Microsoft AZ-801 Practice Test 67 - Prepaway
Practice Exams:

Pass Microsoft AZ-801 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

AZ-801 Premium Bundle


  • Premium File 326 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 122 Lectures
  • Study Guide 387 Pages

Microsoft AZ-801 Practice Test 67

Question 660

During an annual site outage simulation for a Windows Hyper-V replication operations unit, administrators confirm that A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. The solution must preserve other approved service dependencies. Before implementing the proposed change (use the Hyper-V Replica Broker clustered client access point instead of a node-specific replication endpoint), which observed evidence most strongly substantiates the technical diagnosis?

  1. event logs show Replica authentication failed due to certificate identity or trust chain mismatch
  2. replication metadata references one former cluster node and errors occur after a legitimate role move
  3. test run records show stale replica-derived VMs and network interfaces outside the protected production state
  4. vault protection overview lists no recent recovery point for the server despite agent installation

Explanation

Correct Answer

B:

Replication metadata references one former cluster node and errors occur after a legitimate role move. A clustered replication endpoint must use a role identity that follows protected workloads across nodes. A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name.

Incorrect Answers

A:

Event logs show Replica authentication failed due to certificate identity or trust chain mismatch. A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. Replication metadata references one former cluster node and errors occur after a legitimate role move.

C:

Testing run records show stale replica-derived VMs and network interfaces outside the protected production state would not resolve the observed failure: a replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. A clustered replication endpoint must use a role identity that follows protected workloads across nodes. Replication metadata references one former cluster node and errors occur after a legitimate role move.

D:

Vault protection overview lists no recent recovery point for the server despite agent installation. A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. Replication metadata references one former cluster node and errors occur after a legitimate role move.

Question 661

At a hybrid VMware and Azure business continuity team, administrators find that An unplanned Hyper-V Replica failover uses an old recovery snapshot without checking which recovery points contain a consistent application state. The case is being investigated during a documented recovery-point review. Before implementing the proposed change (select a supported latest acceptable application-consistent recovery point and document potential data-loss window), which observed evidence most strongly substantiates the technical diagnosis?

  1. replication metadata references one former cluster node and errors occur after a legitimate role move
  2. disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services
  3. replica recovery-point list shows different application-consistency flags and substantial differences in timestamps
  4. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan

Explanation

Correct Answer

C:

Replica recovery-point list shows different application-consistency flags and substantial differences in timestamps. The symptom alone—An unplanned Hyper-V Replica failover uses an old recovery snapshot without checking which recovery points contain a consistent application state—could otherwise be mistaken for an unrelated infrastructure problem. At a hybrid VMware and Azure business continuity team, administrators find that An unplanned Hyper-V Replica failover uses an old recovery snapshot without checking which recovery points contain a consistent application state.

Incorrect Answers

A:

“Replication metadata references one former cluster node and errors occur after a legitimate role move” concerns a different part of the problem. Replica recovery-point list shows different application-consistency flags and substantial differences in timestamps.

B:

The symptom alone—An unplanned Hyper-V Replica failover uses an old recovery snapshot without checking which recovery points contain a consistent application state—could otherwise be mistaken for an unrelated infrastructure problem. The strongest of the offered choices. The proposed action “Disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services” would not resolve that situation. Replica recovery-point list shows different application-consistency flags and substantial differences in timestamps.

D:

“ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan” does not explain the observed failure: the strongest of the offered choices. The symptom alone—An unplanned Hyper-V Replica failover uses an old recovery snapshot without checking which recovery points contain a consistent application state—could otherwise be mistaken for an unrelated infrastructure problem. Replica recovery-point list shows different application-consistency flags and substantial differences in timestamps.

Question 662

During a maintenance-window root-cause analysis for an on-premises data center support group, administrators confirm that Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance. The solution must preserve other approved service dependencies. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security
  2. repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role
  3. correlate per-volume latency and queue counters with underlying SAN or virtual storage load, then reschedule or rebalance I/O
  4. create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions

Explanation

Correct Answer

B:

Repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role. The PDC emulator time source drifted outside Kerberos tolerance, while the available record shows w32tm status and Kerberos logs show the PDC emulator skewed significantly from a trusted source. Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance.

Incorrect Answers

A:

Inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security. Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance. Repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role.

C:

Correlate per-volume latency and queue counters with underlying SAN or virtual storage load, then reschedule or rebalance I/O. Addresses another workflow. Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance. Repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role.

D:

Create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions. The PDC emulator time source drifted outside Kerberos tolerance, while the available record shows w32tm status and Kerberos logs show the PDC emulator skewed significantly from a trusted source. Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance. Repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role.

Question 663

During a signed business continuity acceptance test for an Azure backup and recovery engineering team, administrators confirm that An encrypted Windows VM backup restores its disks but the recovery process lacks the original accessible key material to unlock the guest. The solution must preserve other approved service dependencies. The administrators propose to prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata. What measurable verification would demonstrate that the original failure has been corrected?

  1. isolated test failover attaches a VM to the intended recovery subnet with expected network policies
  2. a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls
  3. Replica connectivity survives cluster role movement while the correct broker virtual name remains reachable
  4. recovered VM boots with the expected disk state and passes application acceptance in an isolated network

Explanation

Correct Answer

B:

A restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls. Encrypted backup is not recoverable without available compatible protectors and keys. Restore activity succeeds at the storage layer but boot logs show disk encryption key retrieval failure.

Incorrect Answers

A:

Isolated test failover attaches a VM to the intended recovery subnet with expected network policies. Restore activity succeeds at the storage layer but boot logs show disk encryption key retrieval failure. A restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls because encrypted backup is not recoverable without available compatible protectors and keys.

C:

Replica connectivity survives cluster role movement while the correct broker virtual name remains reachable. Restore activity succeeds at the storage layer but boot logs show disk encryption key retrieval failure. A restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls.

D:

“Recovered VM boots with the expected disk state and passes application acceptance in an isolated network” does not explain the observed failure: restore activity succeeds at the storage layer but boot logs show disk encryption key retrieval failure. A restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls.

Question 664

At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. The case is being investigated during a staged source-to-target cutover. The administrators propose to inventory and replace incompatible drivers, migrate queues and permissions with supported print tools. What measurable verification would demonstrate that the original failure has been corrected?

  1. migrated web endpoints complete authenticated TLS transactions with least-privilege application-pool credentials
  2. representative target computers process the intended GPO with translated principals and no unauthorized application
  3. representative clients print through authorized new server queues and legacy drivers are no longer required
  4. accounts retain their audited nested group memberships and access tests pass against target services

Explanation

Correct Answer

C:

Representative clients print through authorized new server queues and legacy drivers are no longer required. The proposed intervention, inventory and replace incompatible drivers, migrate queues and permissions with supported print tools, is justified on the engineering principle that print migration must address server driver architecture, queue metadata and client access. At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host.

Incorrect Answers

A:

The proposed intervention, inventory and replace incompatible drivers, migrate queues and permissions with supported print tools, is justified on the engineering principle that print migration must address server driver architecture, queue metadata and client access. At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. The proposed action “Migrated web endpoints complete authenticated TLS transactions with least-privilege application-pool credentials” would not resolve that situation. Representative clients print through authorized new server queues and legacy drivers are no longer required.

B:

The proposed step “Representative target computers process the intended GPO with translated principals and no unauthorized application” would leave the problem unresolved: at a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. Representative clients print through authorized new server queues and legacy drivers are no longer required.

D:

Accounts retain their audited nested group memberships and access tests pass against target services. At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. Representative clients print through authorized new server queues and legacy drivers are no longer required.

Question 665

At a Windows Server 2025 workload fleet with Azure Arc, administrators find that A domain-joined server starts applying a public Windows Defender Firewall profile after DNS and domain-controller reachability change during failover. The case is being investigated during a controlled security baseline change. The incident trace shows Get-NetConnectionProfile shows a public category while secure domain-controller authentication and DNS fail. Which proposed action and matching validation would address the same root cause?

  1. deploy supported Microsoft Entra Password Protection proxy and DC agents with registered forest configuration and staged enforcement — verify: simulated on-premises password changes reject a banned pattern while normal password resets succeed
  2. repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall — verify: the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable
  3. configure a valid conditional forwarder or Azure DNS Private Resolver path for the private zone — verify: the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable
  4. repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall — verify: compliance evidence proves the chosen disk and key control matches the policy and permitted recovery operations succeed

Explanation

Correct Answer

B:

Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall. Verify that the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. Windows firewall profile selection depends on network identification and must not be bypassed by blanket permit rules.

Incorrect Answers

A:

Simulated on-premises password changes reject a banned pattern while normal password resets succeed. The required validation is different: the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall.

C:

The correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. To correct the reported problem, repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall. Windows firewall profile selection depends on network identification and must not be bypassed by blanket permit rules.

D:

Compliance evidence proves the chosen disk and key control matches the policy and permitted recovery operations succeed. It would not verify that the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. The correct domain firewall profile applies after connectivity recovery and only intended ports are reachable.

Question 666

At a two-site datacenter high-availability team, administrators find that A new Windows failover cluster cannot create a clustered file-server name because the cluster computer account lacks AD permissions. The case is being investigated during a planned primary-site outage exercise. Before implementing the proposed change (prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity), which observed evidence most strongly substantiates the technical diagnosis?

  1. Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node
  2. Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container
  3. replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts
  4. cluster network events correlate heartbeat timeouts with sustained saturated client-facing links

Explanation

Correct Answer

B:

Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container. The cluster computer account lacks AD permissions—could otherwise be mistaken for an unrelated infrastructure problem. At a two-site datacenter high-availability team, administrators find that A new Windows failover cluster cannot create a clustered file-server name because the cluster computer account lacks AD permissions.

Incorrect Answers

A:

“Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node” does not explain the observed failure: the strongest of the offered choices. The cluster computer account lacks AD permissions—could otherwise be mistaken for an unrelated infrastructure problem. Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container.

C:

“Replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts” does not explain the observed failure: the strongest of the offered choices. Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container.

D:

“Cluster network events correlate heartbeat timeouts with sustained saturated client-facing links” concerns a different part of the problem. Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container.

Question 667

During a staged source-to-target cutover for a Windows Server modernization migration team, administrators confirm that Operators upgrade a legacy application server in place without validating role support, resulting in an unbootable installed application service. The solution must preserve other approved service dependencies. The incident trace shows readiness scan identifies an unsupported application dependency and the attempted upgrade fails post-reboot. Which proposed action and matching validation would address the same root cause?

  1. run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing — verify: representative target computers process the intended GPO with translated principals and no unauthorized application
  2. migrate session collection, licensing and profile prerequisites using a supported staged approach — verify: redirected users log into the new collection with retained profile settings and valid licensing
  3. run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing — verify: a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path
  4. configure supported Azure Files identity-based SMB authentication together with share-level access and directory ACL preservation — verify: a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path

Explanation

Correct Answer

C:

Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing. Verify that a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. An in-place OS upgrade cannot replace product and role compatibility testing.

Incorrect Answers

A:

Representative target computers process the intended GPO with translated principals and no unauthorized application. It would not verify that a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. A staged upgrade in a test clone preserves applications and role state with a recoverable rollback path.

B:

Redirected users log into the new collection with retained profile settings and valid licensing. The required validation is different: a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing.

D:

A staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. To correct the reported problem, run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing. An in-place OS upgrade cannot replace product and role compatibility testing.

Question 668

During a domain security hardening review for a multi-branch Active Directory services team, administrators confirm that A high-value member server retains reusable domain sign-in secrets in memory even after a workstation compromise drill. The solution must preserve other approved service dependencies. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts
  2. replace the broad inbound exception with service-scoped source-restricted rules and validate GPO precedence
  3. reconcile connection security rules and certificate or Kerberos authentication prerequisites on both endpoints
  4. configure a valid conditional forwarder or Azure DNS Private Resolver path for the private zone

Explanation

Correct Answer

A:

Verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts. Isolating eligible credential secrets with virtualization-based security reduces credential theft opportunities on compatible hosts; adjacent fixes would not necessarily preserve the intended security or availability boundary. A high-value member server retains reusable domain sign-in secrets in memory even after a workstation compromise drill.

Incorrect Answers

B:

Replace the broad inbound exception with service-scoped source-restricted rules and validate GPO precedence. Isolating eligible credential secrets with virtualization-based security reduces credential theft opportunities on compatible hosts; adjacent fixes would not necessarily preserve the intended security or availability boundary. A high-value member server retains reusable domain sign-in secrets in memory even after a workstation compromise drill. Verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts.

C:

Reconcile connection security rules and certificate or Kerberos authentication prerequisites on both endpoints. A high-value member server retains reusable domain sign-in secrets in memory even after a workstation compromise drill. Verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts.

D:

Configure a valid conditional forwarder or Azure DNS Private Resolver path for the private zone. A high-value member server retains reusable domain sign-in secrets in memory even after a workstation compromise drill. Verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts because isolating eligible credential secrets with virtualization-based security reduces credential theft opportunities on compatible hosts; adjacent fixes would not necessarily preserve the intended security or availability boundary.

Question 669

At a hybrid infrastructure availability team, administrators find that A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. The case is being investigated during a disaster-tolerant production failover rehearsal. Which system engineering principle most directly explains why the remedy to check fault domains and reserve capacity, then complete supported Repair-VirtualDisk or storage jobs is appropriate?

  1. workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership
  2. clustered storage requires coordinated ownership and supported shared-disk fencing
  3. cluster availability depends on quorum voting design and failure-domain independence, not only node count
  4. distributed storage rebuild needs usable placement capacity across independent fault domains

Explanation

Correct Answer

D:

Distributed storage rebuild needs usable placement capacity across independent fault domains. Repair jobs lack usable free capacity, produces the distinctive clue Storage Jobs report incomplete slab repair with a shortage of valid fault-domain capacity. At a hybrid infrastructure availability team, administrators find that A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity.

Incorrect Answers

A:

“Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership” does not demonstrate what is needed when at a hybrid infrastructure availability team, administrators find that A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. Distributed storage rebuild needs usable placement capacity across independent fault domains.

B:

“Clustered storage requires coordinated ownership and supported shared-disk fencing” does not explain the observed failure: at a hybrid infrastructure availability team, administrators find that A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. Distributed storage rebuild needs usable placement capacity across independent fault domains.

C:

“Cluster availability depends on quorum voting design and failure-domain independence, not only node count” concerns a different part of the problem. At a hybrid infrastructure availability team, administrators find that A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. Distributed storage rebuild needs usable placement capacity across independent fault domains.

Question 670

At an on-premises data center support group, administrators find that Windows Admin Center shows registered remote servers but operational threshold alerts never fire for a monitored volume approaching capacity. The case is being investigated during a maintenance-window root-cause analysis. The incident trace shows disk free-space telemetry crosses an agreed threshold without any administrative alert event. Which proposed action and matching validation would address the same root cause?

  1. inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security — verify: test threshold crossing creates a routed alert and server management permissions remain least-privileged
  2. configure supported Windows Admin Center monitoring connections and alert thresholds with required access — verify: a targeted workload fix reduces sustained processor queue and service latency without hiding demand
  3. configure supported Windows Admin Center monitoring connections and alert thresholds with required access — verify: test threshold crossing creates a routed alert and server management permissions remain least-privileged
  4. correlate per-volume latency and queue counters with underlying SAN or virtual storage load, then reschedule or rebalance I/O — verify: load tests preserve disk latency within the service objective after the corrected storage scheduling plan

Explanation

Correct Answer

C:

Configure supported Windows Admin Center monitoring connections and alert thresholds with required access. Verify that test threshold crossing creates a routed alert and server management permissions remain least-privileged. Management portal registration is separate from actual actionable monitoring and alert configuration.

Incorrect Answers

A:

Test threshold crossing creates a routed alert and server management permissions remain least-privileged. To correct the reported problem, configure supported Windows Admin Center monitoring connections and alert thresholds with required access. Management portal registration is separate from actual actionable monitoring and alert configuration.

B:

A targeted workload fix reduces sustained processor queue and service latency without hiding demand. It would not verify that test threshold crossing creates a routed alert and server management permissions remain least-privileged. Test threshold crossing creates a routed alert and server management permissions remain least-privileged.

D:

Load tests preserve disk latency within the service objective after the corrected storage scheduling plan. The required validation is different: test threshold crossing creates a routed alert and server management permissions remain least-privileged. Configure supported Windows Admin Center monitoring connections and alert thresholds with required access.

Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests