You save $69.98
AZ-801 Premium Bundle
- Premium File 326 Questions & Answers
- Last Update: Nov 11, 2026
- Training Course 122 Lectures
- Study Guide 387 Pages
You save $69.98
A new Windows Server will replace a legacy DHCP server serving multiple network scopes.
Which adverse outcome best describes the untreated issue?
Turning on a new server with overlapping scopes before disabling the old one can issue conflicting leases. This is the direct risk of the described condition: A new Windows Server will replace a legacy DHCP server serving multiple network scopes. DHCP continuity relies on valid scopes, reservations, options and directory authorization where required. The corrective approach is to export and import DHCP configuration through a supported migration method and authorize the replacement DHCP service.
Copying content alone can produce an apparent migration that fails at TLS, authentication or process startup. This is a risk associated with Migrate IIS site configuration, such as when an older IIS server runs several applications with custom bindings, certificates and authentication settings. For this case, the main exposure is that turning on a new server with overlapping scopes before disabling the old one can issue conflicting leases.
Attempting an unsupported direct OS upgrade can leave the host unbootable or the application unsupported. This is a risk associated with Choose in-place upgrade versus side-by-side migration, such as when a very old Windows Server installation hosts an application that cannot tolerate an unsupported direct OS upgrade. For this case, the main exposure is that turning on a new server with overlapping scopes before disabling the old one can issue conflicting leases.
Moving only the printer name without driver and port configuration can leave end-user printing unavailable. This is a risk associated with Print server migration, such as when an office has hundreds of printer queues tied to a Windows Server scheduled for decommissioning. For this case, the main exposure is that turning on a new server with overlapping scopes before disabling the old one can issue conflicting leases.
A satellite site has an RODC and needs predictable offline logon for ordinary users without caching privileged credentials.
Which supported approach best meets the stated operational need?
Configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts. This addresses the stated situation: A satellite site has an RODC and needs predictable offline logon for ordinary users without caching privileged credentials. An RODC caches only permitted account credentials, reducing exposure if a physically less-secure branch controller is stolen. Confirm the outcome by checking that approved branch accounts can log on under the intended network conditions, while denied privileged credentials are not cached. If the control is skipped, overbroad password caching on an RODC can expose privileged credentials when the branch server is compromised.
Deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement. This is more relevant to Entra Password Protection for AD DS, such as when a hybrid AD organization finds that users can choose predictable passwords containing the company name. Password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution. The appropriate action here is to configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts.
Evaluate and add eligible privileged accounts to the Protected Users security group after validating their authentication dependencies. This is more relevant to Protected Users account group, such as when tier-zero administrator credentials must not be exposed through legacy NTLM authentication on member machines. Protected Users imposes authentication protections including restrictions on NTLM and credential caching that can affect unsupported legacy workflows. The appropriate action here is to configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts.
Design and enforce supported AD authentication policies and authentication policy silos for the privileged identities and eligible hosts. This is more relevant to Authentication policy silos, such as when tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. Authentication policy silos restrict where qualifying Kerberos-authenticated privileged identities can authenticate, reducing credential exposure. The appropriate action here is to configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts.
Privileged support staff sign in to Windows Server and attackers might attempt to dump reusable domain credentials from memory.
What is the most appropriate next administrative action?
Enable Windows Defender Credential Guard on compatible systems and verify virtualization-based security prerequisites. This addresses the stated situation: Privileged support staff sign in to Windows Server and attackers might attempt to dump reusable domain credentials from memory. Credential Guard isolates qualifying secrets using virtualization-based security so ordinary operating-system processes cannot directly read protected credential material. Confirm the outcome by checking that system information reports Credential Guard running and a supported validation confirms the protected logon scenario remains functional. If the control is skipped, assuming the feature is active without checking hardware and virtualization prerequisites can leave reusable credentials exposed.
Configure Windows LAPS backup, rotation and authorized password retrieval for each managed Windows Server computer. This is more relevant to Windows LAPS local administrator passwords, such as when shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. Windows LAPS manages distinct rotating local administrator credentials and protects their recovery through supported directory permissions. The appropriate action here is to enable Windows Defender Credential Guard on compatible systems and verify virtualization-based security prerequisites.
Pilot Windows Exploit Protection mitigations for the executable, verify compatibility, and deploy the tested policy by management tools. This is more relevant to Exploit Protection mitigation policy, such as when a third-party accounting executable must be hardened against memory-corruption exploits without blocking its approved workflow. Exploit Protection applies process-level mitigations such as DEP and CFG; untested settings can interfere with legacy application behavior. The appropriate action here is to enable Windows Defender Credential Guard on compatible systems and verify virtualization-based security prerequisites.
Deploy a staged Windows Defender Application Control policy that permits approved code and blocks untrusted executables. This is more relevant to Application control allowlist, such as when a file server must run only signed approved administration utilities and vetted service binaries. WDAC enforces code-integrity policy during loading or execution, and audit mode helps discover required applications before enforcement. The appropriate action here is to enable Windows Defender Credential Guard on compatible systems and verify virtualization-based security prerequisites.
A regional datacenter needs the same banned-password policy for on-premises password changes as cloud accounts.
Which technical principle best explains why the correct solution works?
Password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution. This mechanism is relevant because a regional datacenter needs the same banned-password policy for on-premises password changes as cloud accounts. The administrator should deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement. Validate the decision by confirming that a weak branded password change is rejected on an on-premises domain controller while approved passwords are accepted.
An RODC caches only permitted account credentials, reducing exposure if a physically less-secure branch controller is stolen. This explains RODC password replication policy, for example: A branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. The decisive mechanism is that password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution.
Authentication policy silos restrict where qualifying Kerberos-authenticated privileged identities can authenticate, reducing credential exposure. This explains Authentication policy silos, for example: Tier-zero administrator accounts should authenticate only to approved privileged access workstations and domain controllers. The decisive mechanism is that password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution.
Protected Users imposes authentication protections including restrictions on NTLM and credential caching that can affect unsupported legacy workflows. This explains Protected Users account group, for example: Tier-zero administrator credentials must not be exposed through legacy NTLM authentication on member machines. The decisive mechanism is that password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution.
A high-priority VM already replicates to a secondary host but needs a third off-site recovery copy.
Which finding should be recorded as evidence of success?
Both configured relationships report healthy states and a controlled downstream test recovers the intended VM version. This specifically verifies the case: A high-priority VM already replicates to a secondary host but needs a third off-site recovery copy. Hyper-V Replica can support extended replication in compatible topologies; each replication leg has independent health and recovery-point considerations. The matching action is to evaluate supported extended replication to an additional host and monitor Hyper-V Replica health and lag at each hop.
The rehearsal VM starts in an isolated network without affecting production, or the planned failover completes with expected replication state. This would validate Hyper-V Replica test versus planned failover, as in this different situation: A team wants to verify that a Hyper-V Replica VM can boot without disrupting the running production VM. It is not the most direct evidence for the case: A high-priority VM already replicates to a secondary host but needs a third off-site recovery copy. Here, successful verification means that both configured relationships report healthy states and a controlled downstream test recovers the intended VM version.
A test failover VM receives the expected network placement and communicates with approved application dependencies. This would validate Azure Site Recovery network mapping, as in this different situation: A replicated application VM starts during a recovery drill but its virtual network cannot reach dependent services. It is not the most direct evidence for the case: A high-priority VM already replicates to a secondary host but needs a third off-site recovery copy. Here, successful verification means that both configured relationships report healthy states and a controlled downstream test recovers the intended VM version.
Replication state is healthy and a scheduled test failover boots an isolated replica without impacting production. This would validate Hyper-V Replica initial setup, as in this different situation: A standalone Hyper-V host needs asynchronous VM recovery at a second on-premises site. It is not the most direct evidence for the case: A high-priority VM already replicates to a secondary host but needs a third off-site recovery copy. Here, successful verification means that both configured relationships report healthy states and a controlled downstream test recovers the intended VM version.
A directory administrator deleted an organizational unit and wants to recover its objects without rebuilding accounts manually.
What risk should be highlighted in the change assessment?
Recreating users as new objects can break existing ACL links and application associations despite identical display names. This is the direct risk of the described condition: A directory administrator deleted an organizational unit and wants to recover its objects without rebuilding accounts manually. With AD Recycle Bin enabled, qualifying deleted directory objects can be restored with more of their original attributes preserved. The corrective approach is to use AD Recycle Bin recovery for eligible deleted objects and validate their restored directory attributes and memberships.
Treating an AD database corruption event as a routine service restart can extend outage or compromise directory consistency. This is a risk associated with DSRM directory database recovery, such as when a domain controller's AD DS database is damaged and an ordinary service restart cannot bring directory services online. For this case, the main exposure is that recreating users as new objects can break existing ACL links and application associations despite identical display names.
Ignoring DFSR backlogs can cause policy and script inconsistencies even with healthy LDAP directory queries. This is a risk associated with SYSVOL replication troubleshooting, such as when a newly created Group Policy Object reaches one domain controller but not another because SYSVOL contents are missing. For this case, the main exposure is that recreating users as new objects can break existing ACL links and application associations despite identical display names.
Treating stale directory data as a client cache issue can prolong inconsistent access enforcement across sites. This is a risk associated with Active Directory replication topology, such as when a remote domain controller has stale user group membership despite reliable local authentication. For this case, the main exposure is that recreating users as new objects can break existing ACL links and application associations despite identical display names.
A baseline scanner reports divergent service and audit settings after a Windows Server image rollout.
Which test result would best confirm the requirement has been met?
A post-deployment compliance assessment shows target settings in their expected state and records any deliberate exception. This specifically verifies the case: A baseline scanner reports divergent service and audit settings after a Windows Server image rollout. OSConfig applies security baseline settings through supported Windows Server configuration mechanisms rather than merely documenting desired values. The matching action is to apply supported Windows Server OSConfig security baseline controls and verify effective configuration on the targeted servers.
A controlled downloaded-file test produces the expected warning and gpresult shows the intended policy applies. This would validate SmartScreen and Group Policy controls, as in this different situation: Users on an administrative jump host routinely open downloaded files from unknown websites. It is not the most direct evidence for the case: A baseline scanner reports divergent service and audit settings after a Windows Server image rollout. Here, successful verification means that a post-deployment compliance assessment shows target settings in their expected state and records any deliberate exception.
System information reports Credential Guard running and a supported validation confirms the protected logon scenario remains functional. This would validate Credential Guard for reusable secrets, as in this different situation: Privileged support staff sign in to Windows Server and attackers might attempt to dump reusable domain credentials from memory. It is not the most direct evidence for the case: A baseline scanner reports divergent service and audit settings after a Windows Server image rollout. Here, successful verification means that a post-deployment compliance assessment shows target settings in their expected state and records any deliberate exception.
The server rotates its local password, authorized recovery succeeds and an unrelated operator cannot retrieve the secret. This would validate Windows LAPS local administrator passwords, as in this different situation: Shared local administrator passwords across branch servers make lateral movement possible after one host is compromised. It is not the most direct evidence for the case: A baseline scanner reports divergent service and audit settings after a Windows Server image rollout. Here, successful verification means that a post-deployment compliance assessment shows target settings in their expected state and records any deliberate exception.
Administrators need repeatable network configuration across cluster hosts with RDMA-capable interfaces.
Which configuration change best addresses this specific requirement?
Use supported Network ATC intent policies to deploy consistent management, compute and storage network settings. This addresses the stated situation: Administrators need repeatable network configuration across cluster hosts with RDMA-capable interfaces. Network ATC expresses host networking intent and applies consistent configuration across eligible cluster nodes. Confirm the outcome by checking that effective host adapters, RDMA, VLAN and virtual switches match the intended policy on all selected nodes. If the control is skipped, hand-configured inconsistent adapters can interrupt east-west storage traffic and impair cluster resiliency.
Design a supported stretched cluster with storage replication or mirrored storage, suitable site networks and tested failover rules. This is more relevant to Stretch cluster across facilities, such as when an application must fail over between two physically separate datacenters while minimizing data loss. A stretched failover cluster spans fault domains, but application continuity depends on storage consistency, quorum and supported connectivity. The appropriate action here is to use supported Network ATC intent policies to deploy consistent management, compute and storage network settings.
Assign supported S2D site or fault-domain awareness and choose storage resiliency suited to the campus topology. This is more relevant to Storage Spaces Direct campus cluster fault domains, such as when a campus cluster must tolerate a whole-building outage without losing data consistency. Storage Spaces Direct uses fault-domain and resiliency settings to decide data placement and survivability across failures. The appropriate action here is to use supported Network ATC intent policies to deploy consistent management, compute and storage network settings.
Deploy a supported Scale-Out File Server role with appropriate continuously available SMB shares and storage. This is more relevant to Scale-Out File Server workloads, such as when a Hyper-V virtualization farm requires continuously available SMB storage backed by a Windows failover cluster. Scale-Out File Server supports active-access clustered file services for suitable application-data workloads such as Hyper-V and SQL Server. The appropriate action here is to use supported Network ATC intent policies to deploy consistent management, compute and storage network settings.
A three-tier service must recover database, application and web tiers in a dependency-aware order.
Which explanation most directly supports the appropriate decision?
ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions. This mechanism is relevant because a three-tier service must recover database, application and web tiers in a dependency-aware order. The administrator should build and test an Azure Site Recovery recovery plan with dependency-appropriate groups and supported automation or manual steps. Validate the decision by confirming that a controlled drill starts tiers in the intended order and records successful steps and required operator approvals.
ASR replication policy and recovery-point configuration affect the available recovery points and how far data might lag the source. This explains ASR replication policy and recovery points, for example: A recovery auditor requires a measurable RPO and enough recovery history for a Windows application VM. The decisive mechanism is that ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions.
ASR network mappings associate source environments with intended recovery networks; replicated disks alone do not restore application connectivity. This explains Azure Site Recovery network mapping, for example: A replicated application VM starts during a recovery drill but its virtual network cannot reach dependent services. The decisive mechanism is that ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions.
Azure Site Recovery orchestrates supported machine replication and recovery between target sites or regions for business continuity. This explains Azure Site Recovery region replication, for example: A business requires a protected Azure Windows VM to survive loss of its primary Azure region. The decisive mechanism is that ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions.
A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM.
What is the most direct consequence of leaving this problem unresolved?
Restoring an entire VM unnecessarily can overwrite legitimate changes made after the backup point. This is the direct risk of the described condition: A finance operator deleted a small directory from an otherwise healthy backed-up Windows Server VM. Azure Backup file-level recovery allows targeted restoration when the backed-up recovery point includes the needed files. The corrective approach is to use a suitable Azure Backup file recovery workflow from a validated restore point and restore only the required content.
A VM without verified backups can lose recoverable application state when its disks or resource group are damaged. This is a risk associated with Recovery Services vault VM backup, such as when Azure IaaS Windows VMs need daily protected recovery points retained independently of their production resource group. For this case, the main exposure is that restoring an entire VM unnecessarily can overwrite legitimate changes made after the backup point.
Using ad hoc file copies for transactional workloads can leave backups inconsistent or unavailable during recovery. This is a risk associated with Azure Backup Server for workload protection, such as when an on-premises application server requires centrally scheduled backups with off-site Azure retention. For this case, the main exposure is that restoring an entire VM unnecessarily can overwrite legitimate changes made after the backup point.
Restoring encrypted disks without required keys can leave the recovery VM unusable despite healthy backups. This is a risk associated with Azure encrypted VM restore, such as when a protected Azure Windows VM uses disk encryption and must be recovered after storage corruption. For this case, the main exposure is that restoring an entire VM unnecessarily can overwrite legitimate changes made after the backup point.
Cloud users see stale account information after an on-premises AD attribute change despite healthy local replication.
Why is the proposed approach appropriate to this Windows Server problem?
Hybrid directory synchronization propagates eligible on-premises identity changes only when the connector, scope and attribute mapping are healthy. This mechanism is relevant because cloud users see stale account information after an on-premises AD attribute change despite healthy local replication. The administrator should check synchronization scope, connector health, error queues and identity mapping in the supported Microsoft Entra synchronization path. Validate the decision by confirming that a controlled attribute change appears on the cloud identity within the expected sync interval and errors clear.
AD DS replicates directory objects across domain controllers using site topology and scheduled or notification-based replication. This explains Active Directory replication topology, for example: A remote domain controller has stale user group membership despite reliable local authentication. The decisive mechanism is that hybrid directory synchronization propagates eligible on-premises identity changes only when the connector, scope and attribute mapping are healthy.
DSRM provides an offline maintenance environment for directory database recovery when normal AD DS operation is unavailable. This explains DSRM directory database recovery, for example: A domain controller's AD DS database is damaged and an ordinary service restart cannot bring directory services online. The decisive mechanism is that hybrid directory synchronization propagates eligible on-premises identity changes only when the connector, scope and attribute mapping are healthy.
SYSVOL contains file-based Group Policy and scripts, and DFSR failures can create inconsistent policy delivery even when AD object replication works. This explains SYSVOL replication troubleshooting, for example: A newly created Group Policy Object reaches one domain controller but not another because SYSVOL contents are missing. The decisive mechanism is that hybrid directory synchronization propagates eligible on-premises identity changes only when the connector, scope and attribute mapping are healthy.
Please check your mailbox for a message from support@examlabs.com and follow the directions.