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

Question 620

During a load-balanced access and cluster-node test for an Azure-hosted clustered application service, administrators confirm that A geographically stretched cluster repeatedly pauses storage writes when the intersite link exceeds the supported replication latency threshold. The solution must preserve other approved service dependencies. 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. 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
  2. run cluster validation and correct shared storage presentation, access and reservation configuration — verify: failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior
  3. verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior — verify: a rolling node restart preserves an SMB application file handle through an alternate supported channel
  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.

Incorrect Answers

A:

A test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. 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:

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.

C:

A rolling node restart preserves an SMB application file handle through an alternate supported channel. 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.

Question 621

At an Azure Arc and Windows Server fleet operations team, administrators find that An Azure Windows virtual machine fails to start after a storage change because boot configuration points to the wrong system volume. The case is being investigated during a critical-service alert and telemetry test. The administrators propose to use supported Azure VM boot diagnostics and offline recovery tools to repair BCD against the correct volume. What measurable verification would demonstrate that the original failure has been corrected?

  1. load tests preserve disk latency within the service objective after the corrected storage scheduling plan
  2. the VM boots from intended disks and data volume mappings remain unchanged after a controlled restart
  3. affected clients discover the correct domain controllers and authenticated logon succeeds after DNS repair
  4. approved updates install within maintenance windows and health reporting confirms reboot requirements

Explanation

Correct Answer

B:

The VM boots from intended disks and data volume mappings remain unchanged after a controlled restart. Boot configuration points to the wrong system volume; the pre-change evidence is Azure boot screenshot and recovery environment identify a missing boot target even though disks are attached.

Incorrect Answers

A:

Load tests preserve disk latency within the service objective after the corrected storage scheduling plan. Azure boot screenshot and recovery environment identify a missing boot target even though disks are attached. The VM boots from intended disks and data volume mappings remain unchanged after a controlled restart because boot configuration points to the wrong system volume; the pre-change evidence is Azure boot screenshot and recovery environment identify a missing boot target even though disks are attached.

C:

Affected clients discover the correct domain controllers and authenticated logon succeeds after DNS repair. Azure boot screenshot and recovery environment identify a missing boot target even though disks are attached. The VM boots from intended disks and data volume mappings remain unchanged after a controlled restart.

D:

“Approved updates install within maintenance windows and health reporting confirms reboot requirements” does not explain the observed failure: azure boot screenshot and recovery environment identify a missing boot target even though disks are attached. The VM boots from intended disks and data volume mappings remain unchanged after a controlled restart.

Question 622

During a maintenance window with failover validation for a Windows Server failover cluster operations group, administrators confirm that A Windows failover cluster moved to Azure retains an on-premises floating-IP design that Azure load balancing cannot probe or route correctly. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to configure the supported Azure load balancer front end, health probe and cluster IP resource integration is appropriate?

  1. planned failover requires active resource ownership transfer ahead of host shutdown
  2. mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes
  3. public cloud load balancers require explicit health-probe aware configuration for clustered virtual IPs
  4. storage-tier performance depends on correctly categorized physical media and supported cache behavior

Explanation

Correct Answer

C:

Public cloud load balancers require explicit health-probe aware configuration for clustered virtual IPS. For the described incident, failover role reports online locally but Azure clients cannot reach the floating service address is the distinguishing observation; configure the supported Azure load balancer front end, health probe and cluster IP resource integration is the proposed repair. A Windows failover cluster moved to Azure retains an on-premises floating-IP design that Azure load balancing cannot probe or route correctly.

Incorrect Answers

A:

Planned failover requires active resource ownership transfer ahead of host shutdown. For the described incident, failover role reports online locally but Azure clients cannot reach the floating service address is the distinguishing observation; configure the supported Azure load balancer front end, health probe and cluster IP resource integration is the proposed repair. A Windows failover cluster moved to Azure retains an on-premises floating-IP design that Azure load balancing cannot probe or route correctly. Public cloud load balancers require explicit health-probe aware configuration for clustered virtual IPS.

B:

Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes. A Windows failover cluster moved to Azure retains an on-premises floating-IP design that Azure load balancing cannot probe or route correctly. Public cloud load balancers require explicit health-probe aware configuration for clustered virtual IPS.

D:

Storage-tier performance depends on correctly categorized physical media and supported cache behavior. A Windows failover cluster moved to Azure retains an on-premises floating-IP design that Azure load balancing cannot probe or route correctly. Public cloud load balancers require explicit health-probe aware configuration for clustered virtual IPS.

Question 623

At a corporate datacenter-to-Azure transformation project, administrators find that A Windows DHCP server replacement imports production leases while the old server continues responding as an authorized DHCP endpoint. The case is being investigated during a migration wave readiness review. The incident trace shows clients receive inconsistent router options from old and new authorized DHCP servers on the same subnet. Which proposed action and matching validation would address the same root cause?

  1. use supported Hyper-V move/export procedures to transfer the complete VM configuration and referenced differencing disks — verify: the destination VM starts with consistent checkpoints and all expected virtual disks available
  2. export scopes, leases and options, configure the new server, then deauthorize and isolate the old server at cutover — verify: a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path
  3. migrate session collection, licensing and profile prerequisites using a supported staged approach — verify: clients renew from only the approved replacement server and receive the exact expected network options
  4. export scopes, leases and options, configure the new server, then deauthorize and isolate the old server at cutover — verify: clients renew from only the approved replacement server and receive the exact expected network options

Explanation

Correct Answer

D:

Export scopes, leases and options, configure the new server, then deauthorize and isolate the old server at cutover. Verify that clients renew from only the approved replacement server and receive the exact expected network options. A Windows DHCP server replacement imports production leases while the old server continues responding as an authorized DHCP endpoint; the original measurable clue was clients receive inconsistent router options from old and new authorized DHCP servers on the same subnet. At a corporate datacenter-to-Azure transformation project, administrators find that A Windows DHCP server replacement imports production leases while the old server continues responding as an authorized DHCP endpoint.

Incorrect Answers

A:

The destination VM starts with consistent checkpoints and all expected virtual disks available. The required validation is different: clients renew from only the approved replacement server and receive the exact expected network options. Export scopes, leases and options, configure the new server, then deauthorize and isolate the old server at cutover.

B:

A staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. It would not verify that clients renew from only the approved replacement server and receive the exact expected network options. Clients receive inconsistent router options from old and new authorized DHCP servers on the same subnet.

C:

Clients renew from only the approved replacement server and receive the exact expected network options. To correct the reported problem, export scopes, leases and options, configure the new server, then deauthorize and isolate the old server at cutover. A Windows DHCP server replacement imports production leases while the old server continues responding as an authorized DHCP endpoint. At a corporate datacenter-to-Azure transformation project, administrators find that A Windows DHCP server replacement imports production leases while the old server continues responding as an authorized DHCP endpoint.

Question 624

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 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. prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity — verify: node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change
  2. 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
  3. 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
  4. reapply a validated Network ATC intent and reconcile intended storage and management network role configurations — verify: each node reports compliant network intent and live SMB Direct storage traffic uses approved redundant adapters

Explanation

Correct Answer

B:

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. Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes.

Incorrect Answers

A:

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. Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes.

C:

The repaired node rejoins membership, passes validation and safely hosts a planned test role. It would not verify that node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change.

D:

Each node reports compliant network intent and live SMB Direct storage traffic uses approved redundant adapters. 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 625

At an Azure backup and recovery engineering team, administrators find that A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. The case is being investigated during a signed business continuity acceptance test. Which system engineering principle most directly explains why the remedy to use the Hyper-V Replica Broker clustered client access point instead of a node-specific replication endpoint is appropriate?

  1. recovery points become valuable only when restore procedures are verified against operational recovery targets
  2. recovery orchestration must represent service dependencies rather than merely powering on VM replicas
  3. DR failover does not by itself restore ongoing data protection in the new primary direction
  4. a clustered replication endpoint must use a role identity that follows protected workloads across nodes

Explanation

Correct Answer

D:

A clustered replication endpoint must use a role identity that follows protected workloads across nodes. The target points to one host name, produces the distinctive clue replication metadata references one former cluster node and errors occur after a legitimate role move. At an Azure backup and recovery engineering team, administrators find that A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name.

Incorrect Answers

A:

Recovery points become valuable only when restore procedures are verified against operational recovery targets. At an Azure backup and recovery engineering team, administrators find that A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. A clustered replication endpoint must use a role identity that follows protected workloads across nodes.

B:

Recovery orchestration must represent service dependencies rather than merely powering on VM replicas. At an Azure backup and recovery engineering team, administrators find that A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. A clustered replication endpoint must use a role identity that follows protected workloads across nodes because the target points to one host name, produces the distinctive clue replication metadata references one former cluster node and errors occur after a legitimate role move.

C:

“DR failover does not by itself restore ongoing data protection in the new primary direction” does not explain the observed failure: at an Azure backup and recovery engineering team, administrators find that A replicated Hyper-V VM hosted in a failover cluster stops replicating after moving to another cluster node because the target points to one host name. The target points to one host name, produces the distinctive clue replication metadata references one former cluster node and errors occur after a legitimate role move. A clustered replication endpoint must use a role identity that follows protected workloads across nodes.

Question 626

At a cross-domain infrastructure consolidation project, administrators find that A Windows IIS site is selected for Azure App Service despite dependencies on local COM components and registry-based machine settings. The case is being investigated during a change freeze and rollback planning meeting. Before implementing the proposed change (perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target), which observed evidence most strongly substantiates the technical diagnosis?

  1. DNS and network diagnostics show both old and new hosts answering the legacy file-server name
  2. assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan
  3. incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours
  4. replication job fails because source is not discovered through the applicable physical or agent-based migration workflow

Explanation

Correct Answer

B:

Assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan. The indicated corrective path is perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target; acceptance requires chosen hosting platform passes representative web requests and validated dependency substitutions.

Incorrect Answers

A:

“DNS and network diagnostics show both old and new hosts answering the legacy file-server name” concerns a different part of the problem. Assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan.

C:

The proposed step “Incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours” would leave the problem unresolved: the strongest of the offered choices. Assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan.

D:

“Replication job fails because source is not discovered through the applicable physical or agent-based migration workflow” does not explain the observed failure: the strongest of the offered choices. The indicated corrective path is perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target. Assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan.

Question 627

At an Azure Arc and Windows Server fleet operations team, administrators find that Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. The case is being investigated during a critical-service alert and telemetry test. Before implementing the proposed change (correlate per-volume latency and queue counters with underlying SAN or virtual storage load, then reschedule or rebalance I/O), which observed evidence most strongly substantiates the technical diagnosis?

  1. Azure Monitor data collection associations omit the resource even though AMA service runs
  2. deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references
  3. Arc extension operation logs show permission or endpoint errors while core connected-machine status is healthy
  4. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs

Explanation

Correct Answer

D:

PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs. Storage performance faults require measuring end-to-end I/O wait and workload contention rather than only resource utilization totals. At an Azure Arc and Windows Server fleet operations team, administrators find that Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy.

Incorrect Answers

A:

“Azure Monitor data collection associations omit the resource even though AMA service runs” does not demonstrate what is needed when at an Azure Arc and Windows Server fleet operations team, administrators find that Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs.

B:

“Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references” does not explain the observed failure: at an Azure Arc and Windows Server fleet operations team, administrators find that Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs.

C:

“Arc extension operation logs show permission or endpoint errors while core connected-machine status is healthy” concerns a different part of the problem. At an Azure Arc and Windows Server fleet operations team, administrators find that Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs.

Question 628

During a monthly compliance verification for a corporate Azure-hosted Windows Server operations unit, administrators confirm that A Windows Server VM in Azure remains publicly reachable on an administrative port despite a deny rule lower in its NSG table. The solution must preserve other approved service dependencies. Before implementing the proposed change (evaluate effective network security rules and place a narrow higher-priority deny ahead of conflicting permits), which observed evidence most strongly substantiates the technical diagnosis?

  1. an architecture review shows only default platform encryption where customer-controlled key governance is contractually required
  2. effective NSG rules show a broad allow with lower numerical priority value winning before the intended deny
  3. RODC replication policy reports a privileged group in the allowed-cache set and shows cached secrets for branch visitors
  4. recovery protector audit shows encryption enabled but no escrowed recovery key exists for the volume

Explanation

Correct Answer

B:

Effective NSG rules show a broad allow with lower numerical priority value winning before the intended deny. The indicated corrective path is evaluate effective network security rules and place a narrow higher-priority deny ahead of conflicting permits; acceptance requires internet probes to the administrative port fail while approved management source addresses retain access.

Incorrect Answers

A:

An architecture review shows only default platform encryption where customer-controlled key governance is contractually required. Effective NSG rules show a broad allow with lower numerical priority value winning before the intended deny because the indicated corrective path is evaluate effective network security rules and place a narrow higher-priority deny ahead of conflicting permits; acceptance requires internet probes to the administrative port fail while approved management source addresses retain access.

C:

RODC replication policy reports a privileged group in the allowed-cache set and shows cached secrets for branch visitors. Effective NSG rules show a broad allow with lower numerical priority value winning before the intended deny.

D:

“Recovery protector audit shows encryption enabled but no escrowed recovery key exists for the volume” does not explain the observed failure: the strongest of the offered choices. Effective NSG rules show a broad allow with lower numerical priority value winning before the intended deny.

Question 629

During a maintenance window with failover validation for a Windows Server failover cluster operations group, administrators confirm that A SQL failover cluster starts a role on the passive node but its disks remain inaccessible because shared storage reservations are misconfigured. The solution must preserve other approved service dependencies. The incident trace shows cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement. Which proposed action and matching validation would address the same root cause?

  1. 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
  2. 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
  3. run cluster validation and correct shared storage presentation, access and reservation configuration — verify: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers
  4. separate or prioritize cluster heartbeat and storage traffic using supported network roles and QoS — verify: controlled failover mounts the correct disk on the new owner while another node cannot write concurrently

Explanation

Correct Answer

A:

Run cluster validation and correct shared storage presentation, access and reservation configuration. Verify that controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. Shared storage reservations are misconfigured; the original measurable clue was cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement.

Incorrect Answers

B:

The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. The required validation is different: controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. Run cluster validation and correct shared storage presentation, access and reservation configuration.

C:

All nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. It would not verify that controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. Cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement.

D:

Controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. To correct the reported problem, run cluster validation and correct shared storage presentation, access and reservation configuration. Shared storage reservations are misconfigured; the original measurable clue was cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement.

Question 630

During a replication and authentication health review for an Active Directory hybrid troubleshooting group, administrators confirm that Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. The solution must preserve other approved service dependencies. Before implementing the proposed change (correlate per-volume latency and queue counters with underlying SAN or virtual storage load, then reschedule or rebalance I/O), which observed evidence most strongly substantiates the technical diagnosis?

  1. deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references
  2. extension status shows handler error codes and conflicts with a previous extension instance
  3. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs
  4. dcdiag and nslookup _ldap._tcp records show missing or stale SRV answers in one branch

Explanation

Correct Answer

C:

PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs. Storage performance faults require measuring end-to-end I/O wait and workload contention rather than only resource utilization totals. Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. Load tests preserve disk latency within the service objective after the corrected storage scheduling plan.

Incorrect Answers

A:

“Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references” does not explain the observed failure: windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs.

B:

Extension status shows handler error codes and conflicts with a previous extension instance. Addresses another workflow. Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs.

D:

Dcdiag and nslookup _ldap._tcp records show missing or stale SRV answers in one branch. Windows Server file operations time out during backup windows because the backing storage queue saturates while CPU and RAM remain healthy. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs.

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