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

Question 890

During a migration wave readiness review for a corporate datacenter-to-Azure transformation project, administrators confirm that Following a file-server cutover, users still connect through DFS referrals to the retired target even though the new storage server contains the data. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to update namespace target referrals and validate DFS client cache expiration and namespace health is appropriate?

  1. directory object migrations must preserve nested membership and authorization dependencies in a deliberate sequence
  2. distributed file namespaces require explicit referral and target health transition alongside storage migration
  3. infrastructure migration success includes redirecting real clients, not merely starting the destination server
  4. migration planning depends on sufficiently privileged discovery access and truthful inventory coverage

Explanation

Correct Answer

B:

Distributed file namespaces require explicit referral and target health transition alongside storage migration. Following a file-server cutover, users still connect through DFS referrals to the retired target even though the new storage server contains the data.

Incorrect Answers

A:

Directory object migrations must preserve nested membership and authorization dependencies in a deliberate sequence. Following a file-server cutover, users still connect through DFS referrals to the retired target even though the new storage server contains the data. Distributed file namespaces require explicit referral and target health transition alongside storage migration.

C:

“Infrastructure migration success includes redirecting real clients, not merely starting the destination server” does not explain the observed failure: following a file-server cutover, users still connect through DFS referrals to the retired target even though the new storage server contains the data. Distributed file namespaces require explicit referral and target health transition alongside storage migration.

D:

Migration planning depends on sufficiently privileged discovery access and truthful inventory coverage. Addresses another workflow. Following a file-server cutover, users still connect through DFS referrals to the retired target even though the new storage server contains the data. Distributed file namespaces require explicit referral and target health transition alongside storage migration.

Question 891

At an Azure-hosted clustered application service, administrators find that A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance. The case is being investigated during a load-balanced access and cluster-node test. Which system engineering principle most directly explains why the remedy to rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests is appropriate?

  1. cluster supportability depends on consistent validated drivers and software across all participating nodes
  2. S2D pool eligibility depends on consistent supported hardware and clean disk ownership state
  3. workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership
  4. distributed storage rebuild needs usable placement capacity across independent fault domains

Explanation

Correct Answer

A:

Cluster supportability depends on consistent validated drivers and software across all participating nodes. Applying rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests should then yield all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. At an Azure-hosted clustered application service, administrators find that A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance.

Incorrect Answers

B:

“S2D pool eligibility depends on consistent supported hardware and clean disk ownership state” does not explain the observed failure: at an Azure-hosted clustered application service, administrators find that A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance. Applying rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests should then yield all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. Cluster supportability depends on consistent validated drivers and software across all participating nodes.

C:

Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership. At an Azure-hosted clustered application service, administrators find that A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance. Cluster supportability depends on consistent validated drivers and software across all participating nodes.

D:

“Distributed storage rebuild needs usable placement capacity across independent fault domains” does not demonstrate what is needed when at an Azure-hosted clustered application service, administrators find that A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance. Cluster supportability depends on consistent validated drivers and software across all participating nodes.

Question 892

At a multi-branch Active Directory services team, administrators find that A help desk delegation allows a regional support group to reset passwords for tier-zero service accounts in a shared organizational unit. The case is being investigated during a domain security hardening review. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. assess supported per-program Exploit Protection settings in audit and a change window before selectively enforcing validated mitigations
  2. create an audited Windows Defender Application Control policy that allows only approved signed applications and test in audit mode before enforcement
  3. verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts
  4. redesign AD access-control entries and delegation boundaries so staff can manage only eligible standard user objects

Explanation

Correct Answer

D:

Redesign AD access-control entries and delegation boundaries so staff can manage only eligible standard user objects. Active Directory delegation must reflect least privilege at the exact object and container scope. At a multi-branch Active Directory services team, administrators find that A help desk delegation allows a regional support group to reset passwords for tier-zero service accounts in a shared organizational unit.

Incorrect Answers

A:

Assessing supported per-program Exploit Protection settings in audit and a change window before selectively enforcing validated mitigations is not a direct response to the evidence: at a multi-branch Active Directory services team, administrators find that A help desk delegation allows a regional support group to reset passwords for tier-zero service accounts in a shared organizational unit. Redesign AD access-control entries and delegation boundaries so staff can manage only eligible standard user objects.

B:

Active Directory delegation must reflect least privilege at the exact object and container scope. At a multi-branch Active Directory services team, administrators find that A help desk delegation allows a regional support group to reset passwords for tier-zero service accounts in a shared organizational unit. Creating an audited Windows Defender Application Control policy that allows only approved signed applications and test in audit mode before enforcement alone cannot establish that the failure is corrected. Redesign AD access-control entries and delegation boundaries so staff can manage only eligible standard user objects.

C:

Verifying virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts leaves the reported concern untested: at a multi-branch Active Directory services team, administrators find that A help desk delegation allows a regional support group to reset passwords for tier-zero service accounts in a shared organizational unit. Redesign AD access-control entries and delegation boundaries so staff can manage only eligible standard user objects.

Question 893

During a quarterly recovery rehearsal for an enterprise Windows Server disaster recovery program, administrators confirm that An Azure-connected Windows Server is configured for daily backup but the relevant Recovery Services vault policy has no active protection association. The solution must preserve other approved service dependencies. Before implementing the proposed change (enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule), which observed evidence most strongly substantiates the technical diagnosis?

  1. Replica state shows the recovered primary now holds the workload with no reverse replication configured
  2. replication metadata references one former cluster node and errors occur after a legitimate role move
  3. vault protection overview lists no recent recovery point for the server despite agent installation
  4. event logs show Replica authentication failed due to certificate identity or trust chain mismatch

Explanation

Correct Answer

C:

Vault protection overview lists no recent recovery point for the server despite agent installation. The indicated corrective path is enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule; acceptance requires a backup job completes and a controlled file recovery reads the correct point-in-time data. During a quarterly recovery rehearsal for an enterprise Windows Server disaster recovery program, administrators confirm that An Azure-connected Windows Server is configured for daily backup but the relevant Recovery.

Incorrect Answers

A:

Replica state shows the recovered primary now holds the workload with no reverse replication configured. Vault protection overview lists no recent recovery point for the server despite agent installation.

B:

“Replication metadata references one former cluster node and errors occur after a legitimate role move” does not explain the observed failure: the strongest of the offered choices. Vault protection overview lists no recent recovery point for the server despite agent installation.

D:

Event logs show Replica authentication failed due to certificate identity or trust chain mismatch. The indicated corrective path is enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule; acceptance requires a backup job completes and a controlled file recovery reads the correct point-in-time data. Vault protection overview lists no recent recovery point for the server despite agent installation.

Question 894

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. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. configure supported certificate-based Replica authentication, firewall port access and matching server names
  2. review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings
  3. repair supported replication appliance registration, agent health and required Azure connectivity
  4. inspect Azure Backup instant recovery snapshot support and restore an appropriate recovery point to a new VM

Explanation

Correct Answer

D:

Inspect Azure Backup instant recovery snapshot support and restore an appropriate recovery point to a new VM. Recovery points become valuable only when restore procedures are verified against operational recovery targets; adjacent fixes would not necessarily preserve the intended security or availability boundary. 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:

Configuring supported certificate-based Replica authentication, firewall port access and matching server names would not resolve 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; adjacent fixes would not necessarily preserve the intended security or availability boundary. Inspect Azure Backup instant recovery snapshot support and restore an appropriate recovery point to a new VM.

B:

Review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings. A production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points. Inspect Azure Backup instant recovery snapshot support and restore an appropriate recovery point to a new VM.

C:

“Repair supported replication appliance registration, agent health and required Azure connectivity” does not demonstrate what is needed when a production Azure VM is deleted accidentally and operators plan to rebuild the entire workload from installation media despite available recent backup recovery points. Inspect Azure Backup instant recovery snapshot support and restore an appropriate recovery point to a new VM.

Question 895

At a corporate Azure-hosted Windows Server operations unit, administrators find that An on-premises domain accepts commonly guessed seasonal passwords because cloud banned-password protection was enabled only for Entra accounts. The case is being investigated during a monthly compliance verification. Before implementing the proposed change (deploy supported Microsoft Entra Password Protection proxy and DC agents with registered forest configuration and staged enforcement), which observed evidence most strongly substantiates the technical diagnosis?

  1. baseline comparison reports changed security settings after the upgrade while application owners report no approved exception
  2. Windows security telemetry attributes process termination to a specific exploit mitigation after a baseline push
  3. authentication telemetry shows privileged users successfully using NTLM to legacy hosts during administration
  4. agent health reports no password-filter enforcement on domain controllers despite cloud policy activation

Explanation

Correct Answer

D:

Agent health reports no password-filter enforcement on domain controllers despite cloud policy activation. Hybrid password protection requires working on-premises agent paths to extend cloud policy to Active Directory Domain Services. At a corporate Azure-hosted Windows Server operations unit, administrators find that An on-premises domain accepts commonly guessed seasonal passwords because cloud banned-password protection was enabled only for Entra accounts.

Incorrect Answers

A:

Hybrid password protection requires working on-premises agent paths to extend cloud policy to Active Directory Domain Services. At a corporate Azure-hosted Windows Server operations unit, administrators find that An on-premises domain accepts commonly guessed seasonal passwords because cloud banned-password protection was enabled only for Entra accounts. The proposed action “Baseline comparison reports changed security settings after the upgrade while application owners report no approved exception” would not resolve that situation. Agent health reports no password-filter enforcement on domain controllers despite cloud policy activation.

B:

The proposed step “Windows security telemetry attributes process termination to a specific exploit mitigation after a baseline push” would leave the problem unresolved: at a corporate Azure-hosted Windows Server operations unit, administrators find that An on-premises domain accepts commonly guessed seasonal passwords because cloud banned-password protection was enabled only for Entra accounts. Agent health reports no password-filter enforcement on domain controllers despite cloud policy activation.

C:

“Authentication telemetry shows privileged users successfully using NTLM to legacy hosts during administration” does not explain the observed failure: at a corporate Azure-hosted Windows Server operations unit, administrators find that An on-premises domain accepts commonly guessed seasonal passwords because cloud banned-password protection was enabled only for Entra accounts. Hybrid password protection requires working on-premises agent paths to extend cloud policy to Active Directory Domain Services. Agent health reports no password-filter enforcement on domain controllers despite cloud policy activation.

Question 896

During a planned primary-site outage exercise for a two-site datacenter high-availability team, administrators confirm that Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. The solution must preserve other approved service dependencies. The incident trace shows one partially upgraded node shows incompatibility errors with cluster function and resource types. Which proposed action and matching validation would address the same root cause?

  1. follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood — verify: a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients
  2. inspect cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum — verify: node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change
  3. run cluster validation and correct shared storage presentation, access and reservation configuration — verify: controlled failover mounts the correct disk on the new owner while another node cannot write concurrently
  4. follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood — verify: node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change

Explanation

Correct Answer

D:

Follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood. Verify that node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation; the original measurable clue was one partially upgraded node shows incompatibility errors with cluster function and resource types.

Incorrect Answers

A:

A production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients. It would not verify that node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. One partially upgraded node shows incompatibility errors with cluster function and resource types.

B:

Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. To correct the reported problem, follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation.

C:

Controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. The required validation is different: node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. Follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood.

Question 897

At a hybrid VMware and Azure business continuity team, administrators find that An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. The case is being investigated during a documented recovery-point review. Which system engineering principle most directly explains why the remedy to review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings is appropriate?

  1. replica recovery choices trade recoverability, application consistency and potential data loss
  2. replication policies must be measured against recovery requirements rather than relying on a generic protected badge
  3. ASR readiness requires healthy source-side replication agents and target-service connectivity
  4. recovery points become valuable only when restore procedures are verified against operational recovery targets

Explanation

Correct Answer

B:

Replication policies must be measured against recovery requirements rather than relying on a generic protected badge. At a hybrid VMware and Azure business continuity team, administrators find that An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice.

Incorrect Answers

A:

“Replica recovery choices trade recoverability, application consistency and potential data loss” does not explain the observed failure: at a hybrid VMware and Azure business continuity team, administrators find that An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. Replication policies must be measured against recovery requirements rather than relying on a generic protected badge.

C:

“ASR readiness requires healthy source-side replication agents and target-service connectivity” does not explain the observed failure: at a hybrid VMware and Azure business continuity team, administrators find that An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. Replication policies must be measured against recovery requirements rather than relying on a generic protected badge.

D:

“Recovery points become valuable only when restore procedures are verified against operational recovery targets” concerns a different part of the problem. At a hybrid VMware and Azure business continuity team, administrators find that An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. Replication policies must be measured against recovery requirements rather than relying on a generic protected badge.

Question 898

At a Windows Server failover cluster operations group, administrators find that Cluster nodes intermittently lose heartbeats because storage replication and client production traffic saturate a single converged interface. The case is being investigated during a maintenance window with failover validation. The incident trace shows cluster network events correlate heartbeat timeouts with sustained saturated client-facing links. Which proposed action and matching validation would address the same root cause?

  1. configure the supported Azure load balancer front end, health probe and cluster IP resource integration — verify: client connection tests succeed through the load balancer before and after role failover
  2. separate or prioritize cluster heartbeat and storage traffic using supported network roles and QoS — verify: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers
  3. separate or prioritize cluster heartbeat and storage traffic using supported network roles and QoS — verify: a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients
  4. reevaluate dynamic quorum and witness placement, then configure supported cloud witness for balanced recovery behavior — verify: a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients

Explanation

Correct Answer

C:

Separate or prioritize cluster heartbeat and storage traffic using supported network roles and QoS. Verify that a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients. Storage replication and client production traffic saturate a single converged interface; the original measurable clue was cluster network events correlate heartbeat timeouts with sustained saturated client-facing links.

Incorrect Answers

A:

Client connection tests succeed through the load balancer before and after role failover. The required validation is different: a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients. Separate or prioritize cluster heartbeat and storage traffic using supported network roles and QoS.

B:

All nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. It would not verify that a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients. Cluster network events correlate heartbeat timeouts with sustained saturated client-facing links.

D:

A production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients. To correct the reported problem, separate or prioritize cluster heartbeat and storage traffic using supported network roles and QoS. Storage replication and client production traffic saturate a single converged interface; the original measurable clue was cluster network events correlate heartbeat timeouts with sustained saturated client-facing links.

Question 899

During a disaster-tolerant production failover rehearsal for a hybrid infrastructure availability team, administrators confirm that A maintenance operator forcibly shuts down a node without moving a clustered workload and users lose active sessions. The solution must preserve other approved service dependencies. The incident trace shows clustered role history shows unplanned resource restarts during the shutdown rather than orderly owner movement. Which proposed action and matching validation would address the same root cause?

  1. use supported Suspend-ClusterNode drain and live role movement before taking the node offline — verify: the role transitions to another healthy node and users retain required service continuity during drained maintenance
  2. use supported Suspend-ClusterNode drain and live role movement before taking the node offline — verify: controlled failover mounts the correct disk on the new owner while another node cannot write concurrently
  3. validate S2D disk and controller eligibility, clean retired metadata and replace unsupported media before enabling the pool — verify: supported storage devices join a healthy S2D pool and test volumes achieve their requested resiliency
  4. verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior — verify: the role transitions to another healthy node and users retain required service continuity during drained maintenance

Explanation

Correct Answer

A:

Use supported Suspend-ClusterNode drain and live role movement before taking the node offline. Verify that the role transitions to another healthy node and users retain required service continuity during drained maintenance. A maintenance operator forcibly shuts down a node without moving a clustered workload and users lose active sessions; the original measurable clue was clustered role history shows unplanned resource restarts during the shutdown rather than orderly owner movement. During a disaster-tolerant production failover rehearsal for a hybrid infrastructure availability team, administrators confirm that A maintenance operator forcibly shuts down a node without moving a clustered workload and users lose active sessions.

Incorrect Answers

B:

Controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. It would not verify that the role transitions to another healthy node and users retain required service continuity during drained maintenance. Clustered role history shows unplanned resource restarts during the shutdown rather than orderly owner movement.

C:

Supported storage devices join a healthy S2D pool and test volumes achieve their requested resiliency. The required validation is different: the role transitions to another healthy node and users retain required service continuity during drained maintenance. Use supported Suspend-ClusterNode drain and live role movement before taking the node offline.

D:

The role transitions to another healthy node and users retain required service continuity during drained maintenance. To correct the reported problem, use supported Suspend-ClusterNode drain and live role movement before taking the node offline. A maintenance operator forcibly shuts down a node without moving a clustered workload and users lose active sessions; the original measurable clue was clustered role history shows unplanned resource restarts during the shutdown rather than orderly owner movement. During a disaster-tolerant production failover rehearsal for a hybrid infrastructure availability team, administrators confirm that A maintenance operator forcibly shuts down a node without moving a clustered workload and users lose active sessions.

Question 900

At an Active Directory hybrid troubleshooting group, administrators find that An Azure Windows Server VM displays CPU graphs but its VM Insights dependency graph remains empty after onboarding. The case is being investigated during a replication and authentication health review. The incident trace shows perf counters arrive in the workspace while expected process and connection map records remain absent. Which proposed action and matching validation would address the same root cause?

  1. verify required dependency-map collection configuration and supported VM Insights agents and connectivity — verify: SYSVOL content converges and a new GPO script executes consistently from all eligible domain controllers
  2. associate a valid DCR to the appropriate Arc machines with workspace output and selected event channel — verify: a controlled application TCP connection appears in the VM dependency view without excessive log collection
  3. verify required dependency-map collection configuration and supported VM Insights agents and connectivity — verify: a controlled application TCP connection appears in the VM dependency view without excessive log collection
  4. 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

Explanation

Correct Answer

C:

Verify required dependency-map collection configuration and supported VM Insights agents and connectivity. Verify that a controlled application TCP connection appears in the VM dependency view without excessive log collection. Infrastructure performance telemetry and workload dependency mapping use different data streams and onboarding requirements.

Incorrect Answers

A:

SYSVOL content converges and a new GPO script executes consistently from all eligible domain controllers. It would not verify that a controlled application TCP connection appears in the VM dependency view without excessive log collection. A controlled application TCP connection appears in the VM dependency view without excessive log collection.

B:

A controlled application TCP connection appears in the VM dependency view without excessive log collection. To correct the reported problem, verify required dependency-map collection configuration and supported VM Insights agents and connectivity. Infrastructure performance telemetry and workload dependency mapping use different data streams and onboarding requirements.

D:

Test threshold crossing creates a routed alert and server management permissions remain least-privileged. The required validation is different: a controlled application TCP connection appears in the VM dependency view without excessive log collection. Verify required dependency-map collection configuration and supported VM Insights agents and connectivity.

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