Microsoft AZ-801 Practice Test 66 - 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 66

Question 650

During a production overnight fault investigation for a Windows Server monitoring and incident engineering team, administrators confirm that A Windows Server fails to install monthly updates because a legacy WSUS policy points to a retired internal update endpoint. 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. collect and correlate Processor Queue Length with per-process CPU and disk counters under production-like load
  2. check DFS Replication event state, partner reachability and perform supported nonauthoritative synchronization where appropriate
  3. repair effective Windows Update policy or approved Azure Update Manager orchestration after reviewing update source responsibilities
  4. configure supported Windows Admin Center monitoring connections and alert thresholds with required access

Explanation

Correct Answer

C:

Repair effective Windows Update policy or approved Azure Update Manager orchestration after reviewing update source responsibilities. A legacy WSUS policy points to a retired internal update endpoint. A Windows Server fails to install monthly updates because a legacy WSUS policy points to a retired internal update endpoint.

Incorrect Answers

A:

Collect and correlate Processor Queue Length with per-process CPU and disk counters under production-like load. A legacy WSUS policy points to a retired internal update endpoint. A Windows Server fails to install monthly updates because a legacy WSUS policy points to a retired internal update endpoint. Repair effective Windows Update policy or approved Azure Update Manager orchestration after reviewing update source responsibilities.

B:

Check DFS Replication event state, partner reachability and perform supported nonauthoritative synchronization where appropriate. A Windows Server fails to install monthly updates because a legacy WSUS policy points to a retired internal update endpoint. Repair effective Windows Update policy or approved Azure Update Manager orchestration after reviewing update source responsibilities.

D:

Configuring supported Windows Admin Center monitoring connections and alert thresholds with required access would not resolve the observed failure: a Windows Server fails to install monthly updates because a legacy WSUS policy points to a retired internal update endpoint. A legacy WSUS policy points to a retired internal update endpoint. Repair effective Windows Update policy or approved Azure Update Manager orchestration after reviewing update source responsibilities.

Question 651

At a two-site datacenter high-availability team, administrators find that Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service. The case is being investigated during a planned primary-site outage exercise. The incident trace shows maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes. Which proposed action and matching validation would address the same root cause?

  1. configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks — verify: a full patch rehearsal updates each node with role continuity and documented pause or resume events
  2. configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks — verify: node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change
  3. reapply a validated Network ATC intent and reconcile intended storage and management network role configurations — verify: each node reports compliant network intent and live SMB Direct storage traffic uses approved redundant adapters
  4. configure the supported Azure load balancer front end, health probe and cluster IP resource integration — verify: a full patch rehearsal updates each node with role continuity and documented pause or resume events

Explanation

Correct Answer

A:

Configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks. Verify that a full patch rehearsal updates each node with role continuity and documented pause or resume events. Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service; the original measurable clue was maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes. At a two-site datacenter high-availability team, administrators find that Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service.

Incorrect Answers

B:

Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. It would not verify that a full patch rehearsal updates each node with role continuity and documented pause or resume events. Maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes.

C:

Each node reports compliant network intent and live SMB Direct storage traffic uses approved redundant adapters. The required validation is different: a full patch rehearsal updates each node with role continuity and documented pause or resume events. Configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks.

D:

A full patch rehearsal updates each node with role continuity and documented pause or resume events. To correct the reported problem, configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks. Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service; the original measurable clue was maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes. At a two-site datacenter high-availability team, administrators find that Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service.

Question 652

During a maintenance window with failover validation for a Windows Server failover cluster operations group, administrators confirm that A Windows failover cluster moved to Azure retains an on-premises floating-IP design that Azure load balancing cannot probe or route correctly. 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. configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks
  2. configure the supported Azure load balancer front end, health probe and cluster IP resource integration
  3. repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection
  4. check fault domains and reserve capacity, then complete supported Repair-VirtualDisk or storage jobs

Explanation

Correct Answer

B:

Configure the supported Azure load balancer front end, health probe and cluster IP resource integration. Public cloud load balancers require explicit health-probe aware configuration for clustered virtual IPS. Failover role reports online locally but Azure clients cannot reach the floating service address. Client connection tests succeed through the load balancer before and after role failover.

Incorrect Answers

A:

Configuring Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks would not resolve the observed failure: failover role reports online locally but Azure clients cannot reach the floating service address. Public cloud load balancers require explicit health-probe aware configuration for clustered virtual IPS. Configure the supported Azure load balancer front end, health probe and cluster IP resource integration.

C:

“Repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection” does not explain the observed failure: failover role reports online locally but Azure clients cannot reach the floating service address. Configure the supported Azure load balancer front end, health probe and cluster IP resource integration.

D:

Check fault domains and reserve capacity, then complete supported Repair-VirtualDisk or storage jobs. Addresses another workflow. Failover role reports online locally but Azure clients cannot reach the floating service address. Configure the supported Azure load balancer front end, health probe and cluster IP resource integration.

Question 653

During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that Remote Desktop Services session hosts are moved to a new version but user profiles and broker assignments still direct sessions to the retired farm. The solution must preserve other approved service dependencies. Before implementing the proposed change (migrate session collection, licensing and profile prerequisites using a supported staged approach), which observed evidence most strongly substantiates the technical diagnosis?

  1. inventory report lists files while omitting administrative share settings and NTFS access-control entries
  2. connection broker logs show sessions assigned to retired hosts while profile containers remain mounted there
  3. postmigration group membership contains unresolved old-domain group references for business-critical roles
  4. replication job fails because source is not discovered through the applicable physical or agent-based migration workflow

Explanation

Correct Answer

B:

Connection broker logs show sessions assigned to retired hosts while profile containers remain mounted there. The indicated corrective path is migrate session collection, licensing and profile prerequisites using a supported staged approach; acceptance requires redirected users log into the new collection with retained profile settings and valid licensing.

Incorrect Answers

A:

Inventory report lists files while omitting administrative share settings and NTFS access-control entries. Connection broker logs show sessions assigned to retired hosts while profile containers remain mounted there.

C:

Postmigration group membership contains unresolved old-domain group references for business-critical roles. The strongest of the offered choices. Connection broker logs show sessions assigned to retired hosts while profile containers remain mounted there.

D:

Replication job fails because source is not discovered through the applicable physical or agent-based migration workflow. Connection broker logs show sessions assigned to retired hosts while profile containers remain mounted there.

Question 654

During an annual site outage simulation for a Windows Hyper-V replication operations unit, administrators confirm that A production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to inspect Azure Backup instant recovery snapshot support and restore an appropriate recovery point to a new VM is appropriate?

  1. Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust
  2. ASR readiness requires healthy source-side replication agents and target-service connectivity
  3. recovery points become valuable only when restore procedures are verified against operational recovery targets
  4. failover rehearsal must end with safe environment cleanup and preserved disaster recovery capability

Explanation

Correct Answer

C:

Recovery points become valuable only when restore procedures are verified against operational recovery targets. A production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points. A production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points.

Incorrect Answers

A:

“Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust” concerns a different part of the problem. A production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points. Recovery points become valuable only when restore procedures are verified against operational recovery targets.

B:

A production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points. The proposed action “ASR readiness requires healthy source-side replication agents and target-service connectivity” would not resolve that situation. Recovery points become valuable only when restore procedures are verified against operational recovery targets.

D:

“Failover rehearsal must end with safe environment cleanup and preserved disaster recovery capability” does not explain the observed failure: a production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points. Recovery points become valuable only when restore procedures are verified against operational recovery targets.

Question 655

At a hybrid infrastructure availability team, administrators find that A SQL failover cluster starts a role on the passive node but its disks remain inaccessible because shared storage reservations are misconfigured. The case is being investigated during a disaster-tolerant production failover rehearsal. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. separate or prioritize cluster heartbeat and storage traffic using supported network roles and QoS
  2. inspect cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum
  3. verify continuously available SMB share settings and redundant SMB Multichannel network paths
  4. run cluster validation and correct shared storage presentation, access and reservation configuration

Explanation

Correct Answer

D:

Run cluster validation and correct shared storage presentation, access and reservation configuration. Shared storage reservations are misconfigured. Cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement.

Incorrect Answers

A:

Separating or prioritize cluster heartbeat and storage traffic using supported network roles and QoS addresses a separate aspect of the case. Cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement. Run cluster validation and correct shared storage presentation, access and reservation configuration.

B:

Inspecting cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum would not resolve the observed failure: cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement. Run cluster validation and correct shared storage presentation, access and reservation configuration.

C:

Verifying continuously available SMB share settings and redundant SMB Multichannel network paths is not a direct response to the evidence: cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement. Run cluster validation and correct shared storage presentation, access and reservation configuration.

Question 656

During a privileged-access audit for a regulated Windows Server hybrid identity environment, administrators confirm that Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. 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. deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing
  2. assign corrective actions through Defender for Cloud recommendations with Azure Policy-backed compliance verification
  3. create and escrow replacement BitLocker protectors, verify successful retrieval, then retire old protectors under change control
  4. deploy supported Microsoft Entra Password Protection proxy and DC agents with registered forest configuration and staged enforcement

Explanation

Correct Answer

A:

Deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing. Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet; adjacent fixes would not necessarily preserve the intended security or availability boundary. Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift.

Incorrect Answers

B:

Assign corrective actions through Defender for Cloud recommendations with Azure Policy-backed compliance verification. Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. Deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing.

C:

Create and escrow replacement BitLocker protectors, verify successful retrieval, then retire old protectors under change control. Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. Deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing.

D:

Deploying supported Microsoft Entra Password Protection proxy and DC agents with registered forest configuration and staged enforcement would not resolve the observed failure: local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. Deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing.

Question 657

During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that Remote Desktop Services session hosts are moved to a new version but user profiles and broker assignments still direct sessions to the retired farm. The solution must preserve other approved service dependencies. The incident trace shows connection broker logs show sessions assigned to retired hosts while profile containers remain mounted there. Which proposed action and matching validation would address the same root cause?

  1. repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory — verify: redirected users log into the new collection with retained profile settings and valid licensing
  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. migrate session collection, licensing and profile prerequisites using a supported staged approach — verify: mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes
  4. enable supported dependency analysis and map observed application traffic before grouping migration waves — verify: migration grouping includes the database dependency and a test wave preserves end-to-end application transactions

Explanation

Correct Answer

B:

Migrate session collection, licensing and profile prerequisites using a supported staged approach. Verify that redirected users log into the new collection with retained profile settings and valid licensing. RDS migration preserves broker, licensing, profile and session dependencies beyond individual server imaging.

Incorrect Answers

A:

Redirected users log into the new collection with retained profile settings and valid licensing. To correct the reported problem, migrate session collection, licensing and profile prerequisites using a supported staged approach. RDS migration preserves broker, licensing, profile and session dependencies beyond individual server imaging.

C:

Mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes. It would not verify that redirected users log into the new collection with retained profile settings and valid licensing. Redirected users log into the new collection with retained profile settings and valid licensing.

D:

Migration grouping includes the database dependency and a test wave preserves end-to-end application transactions. The required validation is different: redirected users log into the new collection with retained profile settings and valid licensing. Migrate session collection, licensing and profile prerequisites using a supported staged approach.

Question 658

At a Windows Server 2025 workload fleet with Azure Arc, administrators find that Two domain GPOs apply contradictory user-rights assignment to production Windows Server organizational units. The case is being investigated during a controlled security baseline change. Which system engineering principle most directly explains why the remedy to inspect Group Policy inheritance and result sets, then consolidate security baseline scope with documented precedence is appropriate?

  1. storage-service encryption and guest or customer-managed key requirements protect different layers and must be evaluated separately
  2. domain policy enforcement depends on inheritance, precedence, scope and processing rather than GPO names alone
  3. Microsoft Defender for Identity detections depend on complete and healthy sensor telemetry from relevant domain controllers
  4. privileged identity protections must account for the protocols and credential caching restrictions imposed on protected accounts

Explanation

Correct Answer

B:

Domain policy enforcement depends on inheritance, precedence, scope and processing rather than GPO names alone. At a Windows Server 2025 workload fleet with Azure Arc, administrators find that Two domain GPOs apply contradictory user-rights assignment to production Windows Server organizational units.

Incorrect Answers

A:

“Storage-service encryption and guest or customer-managed key requirements protect different layers and must be evaluated separately” does not explain the observed failure: at a Windows Server 2025 workload fleet with Azure Arc, administrators find that Two domain GPOs apply contradictory user-rights assignment to production Windows Server organizational units. Domain policy enforcement depends on inheritance, precedence, scope and processing rather than GPO names alone.

C:

At a Windows Server 2025 workload fleet with Azure Arc, administrators find that Two domain GPOs apply contradictory user-rights assignment to production Windows Server organizational units. The proposed action “Microsoft Defender for Identity detections depend on complete and healthy sensor telemetry from relevant domain controllers” would not resolve that situation. Domain policy enforcement depends on inheritance, precedence, scope and processing rather than GPO names alone.

D:

The proposed step “Privileged identity protections must account for the protocols and credential caching restrictions imposed on protected accounts” would leave the problem unresolved: at a Windows Server 2025 workload fleet with Azure Arc, administrators find that Two domain GPOs apply contradictory user-rights assignment to production Windows Server organizational units. Domain policy enforcement depends on inheritance, precedence, scope and processing rather than GPO names alone.

Question 659

During a documented recovery-point review for a hybrid VMware and Azure business continuity team, administrators confirm that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its selected recovery policy excludes the database. The solution must preserve other approved service dependencies. The administrators propose to configure MABS protection group with application-aware backups and suitable local and Azure retention. What measurable verification would demonstrate that the original failure has been corrected?

  1. an application-consistent database restore completes to a recovery environment within retention targets
  2. after failover and reverse setup both partners show healthy replication and controlled return is documented
  3. test recovery resources are removed while protected replication health and genuine production VM state remain intact
  4. a backup job completes and a controlled file recovery reads the correct point-in-time data

Explanation

Correct Answer

A:

An application-consistent database restore completes to a recovery environment within retention targets. Workload-aware backup requires protection group inclusion and recoverable application-state checkpoints. Protection group membership shows only volume-level backup while database consistency checks remain absent. An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its selected recovery policy excludes the database.

Incorrect Answers

B:

After failover and reverse setup both partners show healthy replication and controlled return is documented. Protection group membership shows only volume-level backup while database consistency checks remain absent. An application-consistent database restore completes to a recovery environment within retention targets.

C:

Testing recovery resources are removed while protected replication health and genuine production VM state remain intact would not resolve the observed failure: protection group membership shows only volume-level backup while database consistency checks remain absent. An application-consistent database restore completes to a recovery environment within retention targets.

D:

A backup job completes and a controlled file recovery reads the correct point-in-time data. Addresses another workflow. Protection group membership shows only volume-level backup while database consistency checks remain absent. An application-consistent database restore completes to a recovery environment within retention targets.

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.

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