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
An organization plans to migrate VMware VMs but lacks inventory data about dependencies and utilization.
Which implementation step should the Windows Server administrator prioritize?
Deploy a supported Azure Migrate discovery appliance and collect sufficient performance and dependency data for assessment. This addresses the stated situation: An organization plans to migrate VMware VMs but lacks inventory data about dependencies and utilization. Azure Migrate discovery and assessment uses inventory and utilization evidence to inform sizing, readiness and cost recommendations. Confirm the outcome by checking that discovered machines appear in the project and produce assessment results based on a representative observation period. If the control is skipped, sizing cloud VMs without workload baselines can cause expensive overprovisioning or insufficient capacity.
Review Azure Migrate readiness, observed performance, software compatibility and cost recommendations before selecting VM sizes. This is more relevant to Azure VM readiness and right-sizing, such as when a legacy application runs on an oversized source VM but the migration team has no throughput or memory baseline. Azure workload sizing depends on actual demand and supported target capabilities rather than simply preserving source hardware dimensions. The appropriate action here is to deploy a supported Azure Migrate discovery appliance and collect sufficient performance and dependency data for assessment.
Use a supported Azure Migrate server migration workflow to replicate, test migrate and execute the cutover. This is more relevant to Azure Migrate VM replication and cutover, such as when a verified on-premises Windows Server VM must be migrated to Azure with a controlled application cutover. Azure Migrate migration coordinates replication and target VM creation; test migration helps validate network and service behavior before committing. The appropriate action here is to deploy a supported Azure Migrate discovery appliance and collect sufficient performance and dependency data for assessment.
Use a supported Azure Migrate physical-server migration or agent-based approach with the correct source prerequisites. This is more relevant to Azure Migrate physical servers, such as when a standalone Windows Server physical machine hosts an application that must run as an Azure virtual machine. Physical server replication to Azure uses compatible migration components and differs from a VM discovery-only inventory. The appropriate action here is to deploy a supported Azure Migrate discovery appliance and collect sufficient performance and dependency data for assessment.
A hybrid failover cluster needs an off-site quorum witness using a controlled Azure storage account.
Why is the proposed approach appropriate to this Windows Server problem?
A Cloud Witness uses an Azure storage blob for cluster quorum arbitration without requiring a full witness server. This mechanism is relevant because a hybrid failover cluster needs an off-site quorum witness using a controlled Azure storage account. The administrator should configure an Azure Cloud Witness using supported storage-account access, connectivity and cluster settings. Validate the decision by confirming that cluster witness health is normal and a simulated site failure preserves the intended quorum behavior.
A stretched failover cluster spans fault domains, but application continuity depends on storage consistency, quorum and supported connectivity. This explains Stretch cluster across facilities, for example: An application must fail over between two physically separate datacenters while minimizing data loss. The decisive mechanism is that a Cloud Witness uses an Azure storage blob for cluster quorum arbitration without requiring a full witness server.
A quorum witness contributes votes or arbitration in supported topologies and reduces split-brain or unavailability risks. This explains Cluster quorum and witness planning, for example: A two-node Windows failover cluster needs to survive the loss of one node without unnecessary loss of quorum. The decisive mechanism is that a Cloud Witness uses an Azure storage blob for cluster quorum arbitration without requiring a full witness server.
Workgroup clusters can operate outside AD DS when their specific authentication, name and workload limitations are addressed. This explains Workgroup cluster identity design, for example: A small isolated application cluster must be built without an Active Directory domain membership dependency. The decisive mechanism is that a Cloud Witness uses an Azure storage blob for cluster quorum arbitration without requiring a full witness server.
A restored Windows VM cannot unlock its encrypted OS volume after key-management permissions changed.
What technical distinction explains the intended control?
Volume unlock depends on matching key protectors and accessible recovery material, which can be separate from the physical disk's health. This mechanism is relevant because a restored Windows VM cannot unlock its encrypted OS volume after key-management permissions changed. The administrator should check the volume's encryption protector state and authorized key recovery path before modifying or deleting stored keys. Validate the decision by confirming that the correct recovery key unlocks the intended volume and authorized use resumes without weakening encryption controls.
Windows startup depends on boot configuration, system partition access and compatible storage drivers; a running hypervisor does not imply a bootable guest. This explains Windows startup recovery, for example: A Windows Server becomes unbootable immediately after a storage-driver change and must be recovered safely. The decisive mechanism is that volume unlock depends on matching key protectors and accessible recovery material, which can be separate from the physical disk's health.
Kerberos authentication and distributed logs depend on reasonably synchronized clocks; inconsistent time can cause ticket validation failures. This explains Windows Time synchronization failures, for example: Kerberos logons fail intermittently because a domain member's clock differs significantly from its domain controller. The decisive mechanism is that volume unlock depends on matching key protectors and accessible recovery material, which can be separate from the physical disk's health.
Arc extension management depends on the connected agent, permitted identities and reachable management services. This explains Arc agent and extension troubleshooting, for example: An Azure Arc-enabled Windows Server reports extension provisioning failure despite healthy local network services. The decisive mechanism is that volume unlock depends on matching key protectors and accessible recovery material, which can be separate from the physical disk's health.
Sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins.
What risk should be highlighted in the change assessment?
Confusing a firewall allow rule with IPsec authentication can permit spoofed or unauthenticated connections. This is the direct risk of the described condition: Sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins. Connection security rules negotiate IPsec authentication and optional protection between hosts; ordinary port allow rules do not authenticate the remote computer. The corrective approach is to deploy and test Windows Defender Firewall connection security rules requiring supported IPsec authentication for the selected endpoints.
Disabling reputation checking or leaving the GPO unlinked can let untrusted downloads execute without the intended user warning. This is a risk associated with SmartScreen and Group Policy controls, such as when users on an administrative jump host routinely open downloaded files from unknown websites. For this case, the main exposure is that confusing a firewall allow rule with IPsec authentication can permit spoofed or unauthenticated connections.
Broadly disabling the host firewall can expose management services even when upstream filtering changes. This is a risk associated with Windows Defender Firewall profile policy, such as when a server accidentally exposes RDP on a public network profile while administrators require limited management access. For this case, the main exposure is that confusing a firewall allow rule with IPsec authentication can permit spoofed or unauthenticated connections.
Relying solely on Windows Firewall while leaving broad NSG exposure increases unintended reachable attack surface. This is a risk associated with Azure NSG filtering for Windows VM, such as when an Azure Windows VM accepts inbound RDP from the public Internet even though access should be limited to a bastion subnet. For this case, the main exposure is that confusing a firewall allow rule with IPsec authentication can permit spoofed or unauthenticated connections.
A physical Windows Server must protect its system volume while supporting disaster recovery after motherboard replacement.
What is the most appropriate next administrative action?
Enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement. This addresses the stated situation: A physical Windows Server must protect its system volume while supporting disaster recovery after motherboard replacement. BitLocker encrypts volumes at rest, while recovery requires access to stored key material if normal TPM unlocking fails. Confirm the outcome by checking that encryption reports protection active and a controlled recovery drill retrieves the correct authorized recovery key. If the control is skipped, encrypting without a retrievable recovery key can make data inaccessible after a TPM or hardware change.
Configure supported disk-encryption key management with least-privilege identities, protected vaults and a recovery validation process. This is more relevant to IaaS VM encryption key governance, such as when a security team needs controlled rotation and access auditing for keys protecting managed Azure VM disks. Encrypted Azure disks depend on their configured key model and access path; changing key grants without dependency analysis can break availability. The appropriate action here is to enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement.
For supported existing deployments, verify Azure Disk Encryption extension status and required key-vault access and recovery procedures. This is more relevant to Azure Disk Encryption implementation, such as when a team maintaining an existing Azure VM deployment uses the Azure Disk Encryption extension and needs to validate key access. Azure Disk Encryption relies on supported in-guest encryption and associated secrets/keys; extension health alone does not guarantee recoverability. The appropriate action here is to enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement.
Enable the appropriate Microsoft Defender for Servers plan and verify deployment of its supported protective components. This is more relevant to Defender for Servers threat protection, such as when azure-hosted Windows Server workloads need endpoint threat alerts and vulnerability assessment beyond configuration-only review. Defender for Servers provides server workload protection features that differ from posture-only inventory and depend on plan and agent configuration. The appropriate action here is to enable BitLocker using supported protectors and escrow the recovery key to an authorized protected location before enforcement.
Sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins.
Which finding should be recorded as evidence of success?
Traffic between approved authenticated hosts succeeds and an untrusted endpoint cannot establish the protected connection. This specifically verifies the case: Sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins. Connection security rules negotiate IPsec authentication and optional protection between hosts; ordinary port allow rules do not authenticate the remote computer. The matching action is to deploy and test Windows Defender Firewall connection security rules requiring supported IPsec authentication for the selected endpoints.
Sensors report healthy status and a supported test signal produces identity-related investigation context in the security portal. This would validate Defender for Identity directory sensors, as in this different situation: Security analysts need to detect suspicious AD reconnaissance and lateral-movement activity around domain controllers. It is not the most direct evidence for the case: Sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins. Here, successful verification means that traffic between approved authenticated hosts succeeds and an untrusted endpoint cannot establish the protected connection.
Connection tests show approved source-to-destination flows succeed and unapproved RDP or database flows are blocked. This would validate Azure NSG filtering for Windows VM, as in this different situation: An Azure Windows VM accepts inbound RDP from the public Internet even though access should be limited to a bastion subnet. It is not the most direct evidence for the case: Sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins. Here, successful verification means that traffic between approved authenticated hosts succeeds and an untrusted endpoint cannot establish the protected connection.
Approved management traffic succeeds from the allowed network while a test from an unauthorized source is denied. This would validate Windows Defender Firewall profile policy, as in this different situation: A server accidentally exposes RDP on a public network profile while administrators require limited management access. It is not the most direct evidence for the case: Sensitive server-to-server traffic on the same corporate subnet must be authenticated independently of application logins. Here, successful verification means that traffic between approved authenticated hosts succeeds and an untrusted endpoint cannot establish the protected connection.
A regional datacenter needs the same banned-password policy for on-premises password changes as cloud accounts.
What is the most directly justified remediation?
Deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement. This addresses the stated situation: A regional datacenter needs the same banned-password policy for on-premises password changes as cloud accounts. Password Protection DC agents evaluate password changes in AD DS against the synchronized banned-password policy; proxy services support policy distribution. Confirm the outcome by checking that a weak branded password change is rejected on an on-premises domain controller while approved passwords are accepted. If the control is skipped, installing only the cloud policy without functional DC agents leaves local AD password changes outside the intended protection.
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 deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement.
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 deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement.
Configure the RODC password replication policy to permit only approved branch identities and explicitly deny sensitive administrative accounts. This is more relevant to RODC password replication policy, such as when a branch office needs a read-only domain controller but must keep high-value administrator passwords out of the branch. An RODC caches only permitted account credentials, reducing exposure if a physically less-secure branch controller is stolen. The appropriate action here is to deploy Microsoft Entra Password Protection proxy and DC agents, configure global and custom banned passwords, and test enforcement.
A business requires a protected Azure Windows VM to survive loss of its primary Azure region.
Why is the proposed approach appropriate to this Windows Server problem?
Azure Site Recovery orchestrates supported machine replication and recovery between target sites or regions for business continuity. This mechanism is relevant because a business requires a protected Azure Windows VM to survive loss of its primary Azure region. The administrator should configure supported Azure Site Recovery replication, recovery target resources and an appropriate replication policy. Validate the decision by confirming that replication health is green, a recovery point exists and a non-disruptive test failover starts the workload in the selected recovery environment.
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 Azure Site Recovery orchestrates supported machine replication and recovery between target sites or regions for business continuity.
ASR recovery plans orchestrate multiple machine failovers in planned sequence, unlike unrelated single-VM recovery actions. This explains ASR recovery plan orchestration, for example: A three-tier service must recover database, application and web tiers in a dependency-aware order. The decisive mechanism is that Azure Site Recovery orchestrates supported machine replication and recovery between target sites or regions for business continuity.
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 Azure Site Recovery orchestrates supported machine replication and recovery between target sites or regions for business continuity.
A security baseline review finds that an old line-of-business application lacks exploit mitigation controls.
What is the most directly justified remediation?
Pilot Windows Exploit Protection mitigations for the executable, verify compatibility, and deploy the tested policy by management tools. This addresses the stated situation: A security baseline review finds that an old line-of-business application lacks exploit mitigation controls. Exploit Protection applies process-level mitigations such as DEP and CFG; untested settings can interfere with legacy application behavior. Confirm the outcome by checking that the protected executable launches and passes its critical business tests while the configured mitigations appear in effective policy. If the control is skipped, applying untested process mitigations can break an essential application while omitting them leaves avoidable exploit exposure.
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 pilot Windows Exploit Protection mitigations for the executable, verify compatibility, and deploy the tested policy by management tools.
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 pilot Windows Exploit Protection mitigations for the executable, verify compatibility, and deploy the tested policy by management tools.
Enable Windows Defender Credential Guard on compatible systems and verify virtualization-based security prerequisites. This is more relevant to Credential Guard for reusable secrets, such as when 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. The appropriate action here is to pilot Windows Exploit Protection mitigations for the executable, verify compatibility, and deploy the tested policy by management tools.
Operations replaced a failed cluster host and need to verify it before moving production resources back.
What observable evidence is most important for successful validation?
The repaired node passes validation, joins the expected cluster and hosts a controlled test resource successfully. This specifically verifies the case: Operations replaced a failed cluster host and need to verify it before moving production resources back. Cluster node recovery requires compatible software, communication and storage paths; simply restoring the machine name is insufficient. The matching action is to repair and validate the node, confirm cluster configuration compatibility and safely rejoin it before failing back services.
Each patched node returns healthy before the next is drained and application resources remain available throughout the sequence. This would validate Cluster-Aware Updating maintenance, as in this different situation: A production Windows failover cluster needs monthly patches without stopping every hosted workload at once. It is not the most direct evidence for the case: Operations replaced a failed cluster host and need to verify it before moving production resources back. Here, successful verification means that the repaired node passes validation, joins the expected cluster and hosts a controlled test resource successfully.
Workloads fail over successfully during each node upgrade and the final cluster functional level matches the new supported version. This would validate Cluster rolling operating-system upgrade, as in this different situation: A supported failover cluster must upgrade Windows Server without one large application outage. It is not the most direct evidence for the case: Operations replaced a failed cluster host and need to verify it before moving production resources back. Here, successful verification means that the repaired node passes validation, joins the expected cluster and hosts a controlled test resource successfully.
The role comes online on the target owner and clients reconnect within the workload's agreed service objective. This would validate Cluster workload and role movement, as in this different situation: A clustered file-server role must be moved away from a node scheduled for hardware maintenance. It is not the most direct evidence for the case: Operations replaced a failed cluster host and need to verify it before moving production resources back. Here, successful verification means that the repaired node passes validation, joins the expected cluster and hosts a controlled test resource successfully.
Operations replaced a failed cluster host and need to verify it before moving production resources back.
Which implementation step should the Windows Server administrator prioritize?
Repair and validate the node, confirm cluster configuration compatibility and safely rejoin it before failing back services. This addresses the stated situation: Operations replaced a failed cluster host and need to verify it before moving production resources back. Cluster node recovery requires compatible software, communication and storage paths; simply restoring the machine name is insufficient. Confirm the outcome by checking that the repaired node passes validation, joins the expected cluster and hosts a controlled test resource successfully. If the control is skipped, moving roles to an unvalidated recovered node can trigger another outage or storage access failure.
Use Failover Cluster Manager or supported PowerShell to drain or move the selected clustered workload to a healthy node. This is more relevant to Cluster workload and role movement, such as when a clustered file-server role must be moved away from a node scheduled for hardware maintenance. Cluster roles have owners and placement constraints; coordinated moves differ from uncontrolled service shutdowns. The appropriate action here is to repair and validate the node, confirm cluster configuration compatibility and safely rejoin it before failing back services.
Follow the supported cluster operating-system rolling-upgrade sequence with workload drains, node upgrades and cluster functional-level updates. This is more relevant to Cluster rolling operating-system upgrade, such as when a supported failover cluster must upgrade Windows Server without one large application outage. Rolling upgrades preserve service during supported mixed-version transitions, but cluster functional-level changes have defined ordering constraints. The appropriate action here is to repair and validate the node, confirm cluster configuration compatibility and safely rejoin it before failing back services.
Configure Cluster-Aware Updating or a supported rolling patch workflow that drains and patches cluster nodes sequentially. This is more relevant to Cluster-Aware Updating maintenance, such as when a production Windows failover cluster needs monthly patches without stopping every hosted workload at once. CAU coordinates node maintenance and workload movement to preserve service availability during supported cluster updates. The appropriate action here is to repair and validate the node, confirm cluster configuration compatibility and safely rejoin it before failing back services.
Please check your mailbox for a message from support@examlabs.com and follow the directions.