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

Question 760

During a controlled security baseline change for a Windows Server 2025 workload fleet with Azure Arc, administrators confirm that Azure Arc enabled on-premises servers are inventoried but lack the intended Microsoft Defender for Servers coverage. The solution must preserve other approved service dependencies. Before implementing the proposed change (enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding), which observed evidence most strongly substantiates the technical diagnosis?

  1. Windows Filtering Platform and IPsec logs show authentication or negotiation failure under the new connection security policy
  2. effective-permission analysis shows the regional group has reset-password rights over privileged account objects
  3. RODC replication policy reports a privileged group in the allowed-cache set and shows cached secrets for branch visitors
  4. Defender for Cloud inventory lists Arc machines without the desired protection plan or assessment telemetry

Explanation

Correct Answer

D:

Defender for Cloud inventory lists Arc machines without the desired protection plan or assessment telemetry. The solution must preserve other approved service dependencies.

Incorrect Answers

A:

Windows Filtering Platform and IPsec logs show authentication or negotiation failure under the new connection security policy. Defender for Cloud inventory lists Arc machines without the desired protection plan or assessment telemetry.

B:

“Effective-permission analysis shows the regional group has reset-password rights over privileged account objects” does not explain the observed failure: the strongest of the offered choices. Defender for Cloud inventory lists Arc machines without the desired protection plan or assessment telemetry.

C:

RODC replication policy reports a privileged group in the allowed-cache set and shows cached secrets for branch visitors. Addresses another workflow. Defender for Cloud inventory lists Arc machines without the desired protection plan or assessment telemetry.

Question 761

At a two-site datacenter high-availability team, administrators find that A geographically stretched cluster repeatedly pauses storage writes when the intersite link exceeds the supported replication latency threshold. The case is being investigated during a planned primary-site outage exercise. The incident trace shows replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts. Which proposed action and matching validation would address the same root cause?

  1. configure supported workgroup cluster local identities, certificates and name resolution consistently on every node — verify: the workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities
  2. 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
  3. repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection — verify: failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior
  4. verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior — verify: failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior

Explanation

Correct Answer

D:

Verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior. Verify that failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior. In the relevant Windows Server or hybrid-cloud layer, synchronous multi-site failover depends on storage replication latency and independent quorum design. Replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts. At a two-site datacenter high-availability team, administrators find that A geographically stretched cluster repeatedly pauses storage writes when the intersite link exceeds the supported replication latency threshold.

Incorrect Answers

A:

The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. The required validation is different: failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior. Verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior.

B:

The role transitions to another healthy node and users retain required service continuity during drained maintenance. It would not verify that failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior. Replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts.

C:

Failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior. To correct the reported problem, verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior. In the relevant Windows Server or hybrid-cloud layer, synchronous multi-site failover depends on storage replication latency and independent quorum design. At a two-site datacenter high-availability team, administrators find that A geographically stretched cluster repeatedly pauses storage writes when the intersite link exceeds the supported replication latency threshold.

Question 762

At an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP. The case is being investigated during a maintenance-window root-cause analysis. 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: extension transitions to succeeded and the expected monitoring signal appears after service restart
  2. correlate per-volume latency and queue counters with underlying SAN or virtual storage load, then reschedule or rebalance I/O — verify: load tests preserve disk latency within the service objective after the corrected storage scheduling plan
  3. inspect sync rules, connector space and export errors, then correct the specific source attribute mapping — verify: extension transitions to succeeded and the expected monitoring signal appears after service restart
  4. inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security — verify: the VM boots from intended disks and data volume mappings remain unchanged after a controlled restart

Explanation

Correct Answer

A:

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. At an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP.

Incorrect Answers

B:

Load tests preserve disk latency within the service objective after the corrected storage scheduling plan. 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.

C:

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. At an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP.

D:

The VM boots from intended disks and data volume mappings remain unchanged after a controlled restart. 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.

Question 763

At a regulated Windows Server hybrid identity environment, administrators find that An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. The case is being investigated during a privileged-access audit. The incident trace shows NTLM operational events attribute legacy authentication to the scanner service account and destination. Which proposed action and matching validation would address the same root cause?

  1. assign corrective actions through Defender for Cloud recommendations with Azure Policy-backed compliance verification — verify: the remediation changes effective configuration and subsequent policy assessments report compliance
  2. enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement — verify: a replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests
  3. enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement — verify: Resultant Set of Policy matches the approved security baseline across representative servers and required administration still works
  4. use supported OSConfig security baseline commands and reconcile documented exceptions through change control — verify: a replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests

Explanation

Correct Answer

B:

Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement. Verify that a replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests. An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller; the original measurable clue was NTLM operational events attribute legacy authentication to the scanner service account and destination.

Incorrect Answers

A:

The remediation changes effective configuration and subsequent policy assessments report compliance. The required validation is different: a replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests. Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement.

C:

Resultant Set of Policy matches the approved security baseline across representative servers and required administration still works. It would not verify that a replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests. NTLM operational events attribute legacy authentication to the scanner service account and destination.

D:

A replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests. To correct the reported problem, enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement. An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller.

Question 764

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. The administrators propose to deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing. What measurable verification would demonstrate that the original failure has been corrected?

  1. a replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests
  2. each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret
  3. Azure Policy evaluation reaches the server and flags or remediates the required baseline without expanding unrelated resource access
  4. approved domain members negotiate protected application traffic while a non-domain probe is denied

Explanation

Correct Answer

B:

Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret. Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet. Password inspection finds identical unmanaged local administrator credentials on unrelated member servers. 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.

Incorrect Answers

A:

“A replay of critical scanner duties succeeds using approved authentication and NTLM restriction logs show rejected legacy tests” does not explain the observed failure: password inspection finds identical unmanaged local administrator credentials on unrelated member servers. Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet. Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret.

C:

“Azure Policy evaluation reaches the server and flags or remediates the required baseline without expanding unrelated resource access” does not explain the observed failure: password inspection finds identical unmanaged local administrator credentials on unrelated member servers. Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret.

D:

Approved domain members negotiate protected application traffic while a non-domain probe is denied. Addresses another workflow. Password inspection finds identical unmanaged local administrator credentials on unrelated member servers. Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret.

Question 765

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. Which system engineering principle most directly explains why the remedy to enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule is appropriate?

  1. disaster recovery replication includes logical network mapping beyond copying operating system disks
  2. a clustered replication endpoint must use a role identity that follows protected workloads across nodes
  3. installing backup software does not create recoverable data until vault registration and policy association are effective
  4. replication policies must be measured against recovery requirements rather than relying on a generic protected badge

Explanation

Correct Answer

C:

Installing backup software does not create recoverable data until vault registration and policy association are effective. An Azure-connected Windows Server is configured for daily backup but the relevant Recovery Services vault policy has no active protection association.

Incorrect Answers

A:

Disaster recovery replication includes logical network mapping beyond copying operating system disks. An Azure-connected Windows Server is configured for daily backup but the relevant Recovery Services vault policy has no active protection association. Installing backup software does not create recoverable data until vault registration and policy association are effective.

B:

A clustered replication endpoint must use a role identity that follows protected workloads across nodes. An Azure-connected Windows Server is configured for daily backup but the relevant Recovery Services vault policy has no active protection association. Installing backup software does not create recoverable data until vault registration and policy association are effective.

D:

Replication policies must be measured against recovery requirements rather than relying on a generic protected badge. An Azure-connected Windows Server is configured for daily backup but the relevant Recovery Services vault policy has no active protection association. Installing backup software does not create recoverable data until vault registration and policy association are effective.

Question 766

At a two-site datacenter high-availability team, administrators find that A new Windows failover cluster cannot create a clustered file-server name because the cluster computer account lacks AD permissions. The case is being investigated during a planned primary-site outage exercise. The incident trace shows Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container. Which proposed action and matching validation would address the same root cause?

  1. repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection — verify: a controlled warning appears at both the affected node and consolidated cluster view before remediation
  2. prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity — verify: controlled failover mounts the correct disk on the new owner while another node cannot write concurrently
  3. rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests — verify: a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights
  4. prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity — verify: a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights

Explanation

Correct Answer

D:

Prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity. Verify that a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. Clustered client identities require valid AD computer objects and controlled delegation for virtual names.

Incorrect Answers

A:

A controlled warning appears at both the affected node and consolidated cluster view before remediation. The required validation is different: a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. Prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity.

B:

Controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. It would not verify that a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. A test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights.

C:

A test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. To correct the reported problem, prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity. Clustered client identities require valid AD computer objects and controlled delegation for virtual names.

Question 767

During a production compatibility validation cycle for an enterprise IIS, storage and AD platform upgrade program, administrators confirm that An application group is assessed as a standalone virtual machine despite upstream database connections crossing several servers. The solution must preserve other approved service dependencies. Before implementing the proposed change (enable supported dependency analysis and map observed application traffic before grouping migration waves), which observed evidence most strongly substantiates the technical diagnosis?

  1. dfsutil referrals show old target priorities or cached locations for affected clients
  2. assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan
  3. dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group
  4. postmigration group membership contains unresolved old-domain group references for business-critical roles

Explanation

Correct Answer

C:

Dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group. The indicated corrective path is enable supported dependency analysis and map observed application traffic before grouping migration waves; acceptance requires migration grouping includes the database dependency and a test wave preserves end-to-end application transactions.

Incorrect Answers

A:

Dfsutil referrals show old target priorities or cached locations for affected clients. Dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group.

B:

“Assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan” does not explain the observed failure: the strongest of the offered choices. Dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group.

D:

Postmigration group membership contains unresolved old-domain group references for business-critical roles. The indicated corrective path is enable supported dependency analysis and map observed application traffic before grouping migration waves; acceptance requires migration grouping includes the database dependency and a test wave preserves end-to-end application transactions. Dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group.

Question 768

At a Windows Server failover cluster operations group, administrators find that Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. The case is being investigated during a maintenance window with failover validation. The administrators propose to follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood. What measurable verification would demonstrate that the original failure has been corrected?

  1. controlled failover mounts the correct disk on the new owner while another node cannot write concurrently
  2. node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change
  3. a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights
  4. the volumes regain healthy resiliency and simulated node loss does not interrupt supported workloads

Explanation

Correct Answer

B:

Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. 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.

Incorrect Answers

A:

“Controlled failover mounts the correct disk on the new owner while another node cannot write concurrently” does not explain the observed failure: 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. Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change.

C:

“A test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights” does not demonstrate what is needed when one partially upgraded node shows incompatibility errors with cluster function and resource types. Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change.

D:

“The volumes regain healthy resiliency and simulated node loss does not interrupt supported workloads” does not explain the observed failure: one partially upgraded node shows incompatibility errors with cluster function and resource types. Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change.

Question 769

During a load-balanced access and cluster-node test for an Azure-hosted clustered application service, administrators confirm that Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks is appropriate?

  1. cluster-aware maintenance sequences capacity and ownership changes so one planned restart does not become a service outage
  2. clustered storage requires coordinated ownership and supported shared-disk fencing
  3. mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes
  4. network resiliency depends on protected cluster communications paths and capacity under failure loads

Explanation

Correct Answer

A:

Cluster-aware maintenance sequences capacity and ownership changes so one planned restart does not become a service outage. Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service.

Incorrect Answers

B:

Clustered storage requires coordinated ownership and supported shared-disk fencing. Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service. Cluster-aware maintenance sequences capacity and ownership changes so one planned restart does not become a service outage.

C:

Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes. Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service. Cluster-aware maintenance sequences capacity and ownership changes so one planned restart does not become a service outage because the intended choice is about the precise control relationship rather than a general Windows Server best practice.

D:

“Network resiliency depends on protected cluster communications paths and capacity under failure loads” does not explain the observed failure: monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service. Cluster-aware maintenance sequences capacity and ownership changes so one planned restart does not become a service outage.

Question 770

During a disaster-tolerant production failover rehearsal for a hybrid infrastructure availability team, administrators confirm that A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance. The solution must preserve other approved service dependencies. The incident trace shows validation reports a version or driver discrepancy on one node immediately after maintenance. Which proposed action and matching validation would address the same root cause?

  1. configure supported workgroup cluster local identities, certificates and name resolution consistently on every node — verify: the workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities
  2. configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks — verify: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers
  3. rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests — verify: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers
  4. rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests — verify: the repaired node rejoins membership, passes validation and safely hosts a planned test role

Explanation

Correct Answer

C:

Rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests. Verify that all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance; the original measurable clue was validation reports a version or driver discrepancy on one node immediately after maintenance.

Incorrect Answers

A:

The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. The required validation is different: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. Rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests.

B:

All nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. To correct the reported problem, rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests. A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance; the original measurable clue was validation reports a version or driver discrepancy on one node immediately after maintenance.

D:

The repaired node rejoins membership, passes validation and safely hosts a planned test role. It would not verify that all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. Validation reports a version or driver discrepancy on one node immediately after maintenance.

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