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

Question 70

During a disaster-tolerant production failover rehearsal for a hybrid infrastructure availability team, administrators confirm that A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. The solution must preserve other approved service dependencies. Before implementing the proposed change (configure supported workgroup cluster local identities, certificates and name resolution consistently on every node), which observed evidence most strongly substantiates the technical diagnosis?

  1. Storage Jobs report incomplete slab repair with a shortage of valid fault-domain capacity
  2. failover role reports online locally but Azure clients cannot reach the floating service address
  3. cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement
  4. cluster creation logs show name or authentication errors on one peer that is not domain joined

Explanation

Correct Answer

D:

Cluster creation logs show name or authentication errors on one peer that is not domain joined. Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership. A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration.

Incorrect Answers

A:

“Storage Jobs report incomplete slab repair with a shortage of valid fault-domain capacity” does not explain the observed failure: a workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. Cluster creation logs show name or authentication errors on one peer that is not domain joined.

B:

“Failover role reports online locally but Azure clients cannot reach the floating service address” concerns a different part of the problem. A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. Cluster creation logs show name or authentication errors on one peer that is not domain joined.

C:

Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership. A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. The proposed action “Cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement” would not resolve that situation. Cluster creation logs show name or authentication errors on one peer that is not domain joined.

Question 71

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. Before implementing the proposed change (follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood), which observed evidence most strongly substantiates the technical diagnosis?

  1. cluster creation logs show name or authentication errors on one peer that is not domain joined
  2. Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node
  3. FailoverClusters events show the node is paused or partitioned with inaccessible quorum resources
  4. one partially upgraded node shows incompatibility errors with cluster function and resource types

Explanation

Correct Answer

D:

One partially upgraded node shows incompatibility errors with cluster function and resource types. Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change.

Incorrect Answers

A:

“Cluster creation logs show name or authentication errors on one peer that is not domain joined” does not explain the observed failure: operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes. One partially upgraded node shows incompatibility errors with cluster function and resource types.

B:

Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. One partially upgraded node shows incompatibility errors with cluster function and resource types.

C:

“FailoverClusters events show the node is paused or partitioned with inaccessible quorum resources” does not explain the observed failure: operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. One partially upgraded node shows incompatibility errors with cluster function and resource types.

Question 72

During a critical-service alert and telemetry test for an Azure Arc and Windows Server fleet operations team, administrators confirm that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP. The solution must preserve other approved service dependencies. The incident trace shows extension status shows handler error codes and conflicts with a previous extension instance. 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. repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role — verify: extension transitions to succeeded and the expected monitoring signal appears after service restart
  3. restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity — verify: restored group retains its original SID and membership and access checks regain expected rights
  4. inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security — verify: extension transitions to succeeded and the expected monitoring signal appears after service restart

Explanation

Correct Answer

D:

Inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security. Verify that extension transitions to succeeded and the expected monitoring signal appears after service restart. VM extension health is an agent and handler execution question independent of RDP connectivity.

Incorrect Answers

A:

Test threshold crossing creates a routed alert and server management permissions remain least-privileged. It would not verify that extension transitions to succeeded and the expected monitoring signal appears after service restart. Extension transitions to succeeded and the expected monitoring signal appears after service restart.

B:

Extension transitions to succeeded and the expected monitoring signal appears after service restart. To correct the reported problem, inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security. VM extension health is an agent and handler execution question independent of RDP connectivity.

C:

Restored group retains its original SID and membership and access checks regain expected rights. The required validation is different: extension transitions to succeeded and the expected monitoring signal appears after service restart. Inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security.

Question 73

At a corporate datacenter-to-Azure transformation project, administrators find that A high-volume file migration repeatedly restarts because copy jobs treat every changing file under active user sessions as a fatal inconsistency. The case is being investigated during a migration wave readiness review. Before implementing the proposed change (stage bulk transfer, schedule a controlled delta synchronization and cut over after validating open-handle closure), which observed evidence most strongly substantiates the technical diagnosis?

  1. dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group
  2. App Service diagnostics show missing environment settings and rejected managed database authentication
  3. incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours
  4. inventory report lists files while omitting administrative share settings and NTFS access-control entries

Explanation

Correct Answer

C:

Incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours. Copy jobs treat every changing file under active user sessions as a fatal inconsistency—could otherwise be mistaken for an unrelated infrastructure problem.

Incorrect Answers

A:

“Dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group” concerns a different part of the problem. Incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours.

B:

Copy jobs treat every changing file under active user sessions as a fatal inconsistency—could otherwise be mistaken for an unrelated infrastructure problem. The strongest of the offered choices. The proposed action “App Service diagnostics show missing environment settings and rejected managed database authentication” would not resolve that situation. Incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours.

D:

“Inventory report lists files while omitting administrative share settings and NTFS access-control entries” does not explain the observed failure: the strongest of the offered choices. Copy jobs treat every changing file under active user sessions as a fatal inconsistency—could otherwise be mistaken for an unrelated infrastructure problem. Incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours.

Question 74

During a production compatibility validation cycle for an enterprise IIS, storage and AD platform upgrade program, administrators confirm that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. The solution must preserve other approved service dependencies. 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. clients from multiple sites receive the new healthy namespace target and legacy path access remains intact
  2. the destination VM starts with consistent checkpoints and all expected virtual disks available
  3. a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path
  4. representative clients print through authorized new server queues and legacy drivers are no longer required

Explanation

Correct Answer

D:

Representative clients print through authorized new server queues and legacy drivers are no longer required. Print migration must address server driver architecture, queue metadata and client access. Print-management logs show incompatible drivers attached to formerly functioning queues.

Incorrect Answers

A:

Clients from multiple sites receive the new healthy namespace target and legacy path access remains intact. Print-management logs show incompatible drivers attached to formerly functioning queues. Representative clients print through authorized new server queues and legacy drivers are no longer required.

B:

“The destination VM starts with consistent checkpoints and all expected virtual disks available” does not explain the observed failure: print-management logs show incompatible drivers attached to formerly functioning queues. Representative clients print through authorized new server queues and legacy drivers are no longer required.

C:

A staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. Addresses another workflow. Print-management logs show incompatible drivers attached to formerly functioning queues. Representative clients print through authorized new server queues and legacy drivers are no longer required.

Question 75

During a replication and authentication health review for an Active Directory hybrid troubleshooting group, administrators confirm that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. The solution must preserve other approved service dependencies. Before implementing the proposed change (restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity), which observed evidence most strongly substantiates the technical diagnosis?

  1. WindowsUpdateClient logs show timeouts connecting to a decommissioned intranet update server
  2. Arc extension operation logs show permission or endpoint errors while core connected-machine status is healthy
  3. deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references
  4. dfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding

Explanation

Correct Answer

C:

Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references. The indicated corrective path is restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity; acceptance requires restored group retains its original SID and membership and access checks regain expected rights.

Incorrect Answers

A:

WindowsUpdateClient logs show timeouts connecting to a decommissioned intranet update server. Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references because the indicated corrective path is restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity.

B:

Arc extension operation logs show permission or endpoint errors while core connected-machine status is healthy. The strongest of the offered choices. Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references.

D:

“DfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding” does not explain the observed failure: the strongest of the offered choices. Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references.

Question 76

At a multi-branch Active Directory services team, administrators find that Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. The case is being investigated during a domain security hardening review. Which system engineering principle most directly explains why the remedy to deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing is appropriate?

  1. IPsec domain isolation requires compatible peer identity and negotiated connection security settings
  2. connected-server inventory and paid workload protection enrollment are distinct control decisions
  3. reputation-aware browser and application checks are additional screening layers and not replacements for software allowlisting
  4. per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet

Explanation

Correct Answer

D:

Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet. At a multi-branch Active Directory services team, administrators find that Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift.

Incorrect Answers

A:

At a multi-branch Active Directory services team, administrators find that Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. The proposed action “IPsec domain isolation requires compatible peer identity and negotiated connection security settings” would not resolve that situation. Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet.

B:

The proposed step “Connected-server inventory and paid workload protection enrollment are distinct control decisions” would leave the problem unresolved: at a multi-branch Active Directory services team, administrators find that Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet.

C:

“Reputation-aware browser and application checks are additional screening layers and not replacements for software allowlisting” does not explain the observed failure: at a multi-branch Active Directory services team, administrators find that Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet.

Question 77

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. Before implementing the proposed change (inspect Group Policy inheritance and result sets, then consolidate security baseline scope with documented precedence), which observed evidence most strongly substantiates the technical diagnosis?

  1. agent health reports no password-filter enforcement on domain controllers despite cloud policy activation
  2. effective firewall policy shows a global inbound permit unrelated to the print service identity
  3. gpresult and policy event records show unexpected winning settings on the affected servers
  4. an architecture review shows only default platform encryption where customer-controlled key governance is contractually required

Explanation

Correct Answer

C:

Gpresult and policy event records show unexpected winning settings on the affected servers. 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:

“Agent health reports no password-filter enforcement on domain controllers despite cloud policy activation” 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. Gpresult and policy event records show unexpected winning settings on the affected servers.

B:

“Effective firewall policy shows a global inbound permit unrelated to the print service identity” concerns a different part of the problem. 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. Gpresult and policy event records show unexpected winning settings on the affected servers.

D:

The proposed step “An architecture review shows only default platform encryption where customer-controlled key governance is contractually required” 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. Gpresult and policy event records show unexpected winning settings on the affected servers.

Question 78

During a maintenance window with failover validation for a Windows Server failover cluster operations group, administrators confirm that A recovered cluster node cannot rejoin quorum after a storage outage despite its VM responding to ping. The solution must preserve other approved service dependencies. The incident trace shows FailoverClusters events show the node is paused or partitioned with inaccessible quorum resources. 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. follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood — verify: the repaired node rejoins membership, passes validation and safely hosts a planned test role
  3. inspect cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum — verify: the repaired node rejoins membership, passes validation and safely hosts a planned test role
  4. inspect cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum — verify: controlled failover mounts the correct disk on the new owner while another node cannot write concurrently

Explanation

Correct Answer

C:

Inspect cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum. Verify that the repaired node rejoins membership, passes validation and safely hosts a planned test role. A reachable operating system is not proof of healthy cluster quorum, storage ownership or service state.

Incorrect Answers

A:

Client connection tests succeed through the load balancer before and after role failover. The required validation is different: the repaired node rejoins membership, passes validation and safely hosts a planned test role. Inspect cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum.

B:

The repaired node rejoins membership, passes validation and safely hosts a planned test role. To correct the reported problem, inspect cluster service state, node membership, storage paths and witness reachability before forcefully changing quorum. A reachable operating system is not proof of healthy cluster quorum, storage ownership or service state.

D:

Controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. It would not verify that the repaired node rejoins membership, passes validation and safely hosts a planned test role. The repaired node rejoins membership, passes validation and safely hosts a planned test role.

Question 79

During a critical-service alert and telemetry test for an Azure Arc and Windows Server fleet operations team, administrators confirm that A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. The solution must preserve other approved service dependencies. Before implementing the proposed change (inspect sync rules, connector space and export errors, then correct the specific source attribute mapping), which observed evidence most strongly substantiates the technical diagnosis?

  1. WindowsUpdateClient logs show timeouts connecting to a decommissioned intranet update server
  2. Arc extension operation logs show permission or endpoint errors while core connected-machine status is healthy
  3. synchronization service errors show a UPN conflict or unexpected source anchor on the affected account
  4. Azure Monitor data collection associations omit the resource even though AMA service runs

Explanation

Correct Answer

C:

Synchronization service errors show a UPN conflict or unexpected source anchor on the affected account. Hybrid identity troubleshooting must preserve immutable identity mapping and diagnose attribute flow before re-creating accounts. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute.

Incorrect Answers

A:

WindowsUpdateClient logs show timeouts connecting to a decommissioned intranet update server. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. Synchronization service errors show a UPN conflict or unexpected source anchor on the affected account.

B:

Arc extension operation logs show permission or endpoint errors while core connected-machine status is healthy. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. Synchronization service errors show a UPN conflict or unexpected source anchor on the affected account because hybrid identity troubleshooting must preserve immutable identity mapping and diagnose attribute flow before re-creating accounts.

D:

Azure Monitor data collection associations omit the resource even though AMA service runs. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. Synchronization service errors show a UPN conflict or unexpected source anchor on the affected account.

Question 80

At an Azure-hosted clustered application service, administrators find that A converged S2D cluster has RDMA interfaces with manually inconsistent VLAN and QoS settings after a node replacement. The case is being investigated during a load-balanced access and cluster-node test. Before implementing the proposed change (reapply a validated Network ATC intent and reconcile intended storage and management network role configurations), which observed evidence most strongly substantiates the technical diagnosis?

  1. one partially upgraded node shows incompatibility errors with cluster function and resource types
  2. Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node
  3. maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes
  4. Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container

Explanation

Correct Answer

B:

Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node. Network ATC coordinates repeatable host networking and avoids drift between converged cluster nodes. At an Azure-hosted clustered application service, administrators find that A converged S2D cluster has RDMA interfaces with manually inconsistent VLAN and QoS settings after a node replacement.

Incorrect Answers

A:

“One partially upgraded node shows incompatibility errors with cluster function and resource types” concerns a different part of the problem. At an Azure-hosted clustered application service, administrators find that A converged S2D cluster has RDMA interfaces with manually inconsistent VLAN and QoS settings after a node replacement. Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node.

C:

The proposed step “Maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes” would leave the problem unresolved: at an Azure-hosted clustered application service, administrators find that A converged S2D cluster has RDMA interfaces with manually inconsistent VLAN and QoS settings after a node replacement. Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node.

D:

“Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container” does not explain the observed failure: at an Azure-hosted clustered application service, administrators find that A converged S2D cluster has RDMA interfaces with manually inconsistent VLAN and QoS settings after a node replacement. Network ATC coordinates repeatable host networking and avoids drift between converged cluster nodes. Get-NetIntentStatus shows conflicting intent assignments and RDMA validation drops on the new node.

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