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

Question 360

During a production overnight fault investigation for a Windows Server monitoring and incident engineering team, administrators confirm that A Windows Server enters BitLocker recovery after a motherboard replacement changes the TPM state and no operator has validated the recovery sequence. The solution must preserve other approved service dependencies. The administrators propose to recover using authorized escrowed keys, reseal compatible protectors and document controlled hardware change handling. What measurable verification would demonstrate that the original failure has been corrected?

  1. simulated audit records remain searchable for required retention while local log bounds and forwarding health stay monitored
  2. the VM boots from intended disks and data volume mappings remain unchanged after a controlled restart
  3. an approved technician restores the encrypted server without exposing keys and subsequent reboots pass protector validation
  4. the account synchronizes with the intended immutable identity and sign-in succeeds without creating a duplicate cloud user

Explanation

Correct Answer

C:

An approved technician restores the encrypted server without exposing keys and subsequent reboots pass protector validation. An unrelated improvement in throughput, monitoring or provisioning cannot replace this causal test. A Windows Server enters BitLocker recovery after a motherboard replacement changes the TPM state and no operator has validated the recovery sequence.

Incorrect Answers

A:

Simulated audit records remain searchable for required retention while local log bounds and forwarding health stay monitored. Addresses another workflow. A Windows Server enters BitLocker recovery after a motherboard replacement changes the TPM state and no operator has validated the recovery sequence. An approved technician restores the encrypted server without exposing keys and subsequent reboots pass protector validation.

B:

The VM boots from intended disks and data volume mappings remain unchanged after a controlled restart. An unrelated improvement in throughput, monitoring or provisioning cannot replace this causal test. A Windows Server enters BitLocker recovery after a motherboard replacement changes the TPM state and no operator has validated the recovery sequence. An approved technician restores the encrypted server without exposing keys and subsequent reboots pass protector validation.

D:

The account synchronizes with the intended immutable identity and sign-in succeeds without creating a duplicate cloud user. A Windows Server enters BitLocker recovery after a motherboard replacement changes the TPM state and no operator has validated the recovery sequence. An approved technician restores the encrypted server without exposing keys and subsequent reboots pass protector validation because an unrelated improvement in throughput, monitoring or provisioning cannot replace this causal test.

Question 361

At a two-site datacenter high-availability team, administrators find that Write-heavy cluster storage latency spikes after new drives are inserted because cache and capacity devices are incorrectly classified. The case is being investigated during a planned primary-site outage exercise. Which system engineering principle most directly explains why the remedy to validate supported drive usage, storage tier configuration and cache-device selection without risking existing data is appropriate?

  1. clustered client identities require valid AD computer objects and controlled delegation for virtual names
  2. storage-tier performance depends on correctly categorized physical media and supported cache behavior
  3. S2D pool eligibility depends on consistent supported hardware and clean disk ownership state
  4. a reachable operating system is not proof of healthy cluster quorum, storage ownership or service state

Explanation

Correct Answer

B:

Storage-tier performance depends on correctly categorized physical media and supported cache behavior. At a two-site datacenter high-availability team, administrators find that Write-heavy cluster storage latency spikes after new drives are inserted because cache and capacity devices are incorrectly classified.

Incorrect Answers

A:

“Clustered client identities require valid AD computer objects and controlled delegation for virtual names” does not demonstrate what is needed when at a two-site datacenter high-availability team, administrators find that Write-heavy cluster storage latency spikes after new drives are inserted because cache and capacity devices are incorrectly classified. Storage-tier performance depends on correctly categorized physical media and supported cache behavior.

C:

“S2D pool eligibility depends on consistent supported hardware and clean disk ownership state” concerns a different part of the problem. At a two-site datacenter high-availability team, administrators find that Write-heavy cluster storage latency spikes after new drives are inserted because cache and capacity devices are incorrectly classified. Storage-tier performance depends on correctly categorized physical media and supported cache behavior.

D:

At a two-site datacenter high-availability team, administrators find that Write-heavy cluster storage latency spikes after new drives are inserted because cache and capacity devices are incorrectly classified. The proposed action “A reachable operating system is not proof of healthy cluster quorum, storage ownership or service state” would not resolve that situation. Storage-tier performance depends on correctly categorized physical media and supported cache behavior.

Question 362

At an enterprise Windows Server disaster recovery program, administrators find that Engineers run Azure Site Recovery test failovers but leave temporary virtual machines consuming reserved IP addresses and cloud quotas. The case is being investigated during a quarterly recovery rehearsal. The incident trace shows test run records show stale replica-derived VMs and network interfaces outside the protected production state. Which proposed action and matching validation would address the same root cause?

  1. apply controlled ASR test failover cleanup and verify resource tracking without deleting production protection — verify: encrypted Hyper-V Replica traffic succeeds and a planned test replica VM starts with the expected recovery state
  2. repair supported replication appliance registration, agent health and required Azure connectivity — verify: consistent recovery points resume and measured replication lag returns within the planned recovery-point objective
  3. apply controlled ASR test failover cleanup and verify resource tracking without deleting production protection — verify: test recovery resources are removed while protected replication health and genuine production VM state remain intact
  4. perform supported planned failover, commit and reverse replication after checking source and target state — verify: test recovery resources are removed while protected replication health and genuine production VM state remain intact

Explanation

Correct Answer

C:

Apply controlled ASR test failover cleanup and verify resource tracking without deleting production protection. Verify that test recovery resources are removed while protected replication health and genuine production VM state remain intact. Failover rehearsal must end with safe environment cleanup and preserved disaster recovery capability.

Incorrect Answers

A:

Encrypted Hyper-V Replica traffic succeeds and a planned test replica VM starts with the expected recovery state. It would not verify that test recovery resources are removed while protected replication health and genuine production VM state remain intact. Test recovery resources are removed while protected replication health and genuine production VM state remain intact.

B:

Consistent recovery points resume and measured replication lag returns within the planned recovery-point objective. The required validation is different: test recovery resources are removed while protected replication health and genuine production VM state remain intact. Apply controlled ASR test failover cleanup and verify resource tracking without deleting production protection.

D:

Test recovery resources are removed while protected replication health and genuine production VM state remain intact. To correct the reported problem, apply controlled ASR test failover cleanup and verify resource tracking without deleting production protection. Failover rehearsal must end with safe environment cleanup and preserved disaster recovery capability.

Question 363

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. The incident trace shows cluster creation logs show name or authentication errors on one peer that is not domain joined. Which proposed action and matching validation would address the same root cause?

  1. validate supported drive usage, storage tier configuration and cache-device selection without risking existing data — verify: synthetic storage workload returns to the accepted latency range with healthy tier assignments and redundancy
  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. configure supported workgroup cluster local identities, certificates and name resolution consistently on every node — verify: node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change
  4. verify continuously available SMB share settings and redundant SMB Multichannel network paths — verify: the workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities

Explanation

Correct Answer

B:

Configure supported workgroup cluster local identities, certificates and name resolution consistently on every node. Verify that the workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. Each server has conflicting local identities and no appropriate trust configuration; the original measurable clue was cluster creation logs show name or authentication errors on one peer that is not domain joined.

Incorrect Answers

A:

Synthetic storage workload returns to the accepted latency range with healthy tier assignments and redundancy. The required validation is different: the workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. Configure supported workgroup cluster local identities, certificates and name resolution consistently on every node.

C:

Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. It would not verify that the workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. Cluster creation logs show name or authentication errors on one peer that is not domain joined.

D:

The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. To correct the reported problem, configure supported workgroup cluster local identities, certificates and name resolution consistently on every node. Each server has conflicting local identities and no appropriate trust configuration; the original measurable clue was cluster creation logs show name or authentication errors on one peer that is not domain joined.

Question 364

At a Windows Server modernization migration team, administrators find that An IIS workload migrates to a newer Windows Server but uses an application pool identity without access to a required certificate private key. The case is being investigated during a staged source-to-target cutover. Which system engineering principle most directly explains why the remedy to export IIS configuration and required dependencies, then grant only the new approved pool identity its necessary certificate rights is appropriate?

  1. source platform type determines supported migration and replication method
  2. IIS migrations must preserve dependent identities and key access, not just site bindings and application files
  3. migrating a web server to a managed platform requires application compatibility assessment, not a direct VM image conversion
  4. cross-forest user moves must reconcile legacy access control identifiers as well as account objects

Explanation

Correct Answer

B:

IIS migrations must preserve dependent identities and key access, not just site bindings and application files. At a Windows Server modernization migration team, administrators find that An IIS workload migrates to a newer Windows Server but uses an application pool identity without access to a required certificate private key.

Incorrect Answers

A:

“Source platform type determines supported migration and replication method” does not explain the observed failure: at a Windows Server modernization migration team, administrators find that An IIS workload migrates to a newer Windows Server but uses an application pool identity without access to a required certificate private key. IIS migrations must preserve dependent identities and key access, not just site bindings and application files.

C:

At a Windows Server modernization migration team, administrators find that An IIS workload migrates to a newer Windows Server but uses an application pool identity without access to a required certificate private key. Migrating a web server to a managed platform requires application compatibility assessment, not a direct VM image conversion alone cannot establish that the failure is corrected. IIS migrations must preserve dependent identities and key access, not just site bindings and application files.

D:

The proposed step “Cross-forest user moves must reconcile legacy access control identifiers as well as account objects” would leave the problem unresolved: at a Windows Server modernization migration team, administrators find that An IIS workload migrates to a newer Windows Server but uses an application pool identity without access to a required certificate private key. IIS migrations must preserve dependent identities and key access, not just site bindings and application files.

Question 365

At a hybrid VMware and Azure business continuity team, administrators find that Azure Site Recovery test failover starts a VM in the target region on the wrong subnet and breaks application access controls. The case is being investigated during a documented recovery-point review. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. create an Azure Site Recovery recovery plan with ordered groups, scripts and validated dependencies
  2. configure target virtual-network and subnet mapping for the protected VM and validate NSG and DNS prerequisites
  3. review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings
  4. configure supported certificate-based Replica authentication, firewall port access and matching server names

Explanation

Correct Answer

B:

Configure target virtual-network and subnet mapping for the protected VM and validate NSG and DNS prerequisites. A review is complete only when isolated test failover attaches a VM to the intended recovery subnet with expected network policies. At a hybrid VMware and Azure business continuity team, administrators find that Azure Site Recovery test failover starts a VM in the target region on the wrong subnet and breaks application access controls.

Incorrect Answers

A:

Creating an Azure Site Recovery recovery plan with ordered groups, scripts and validated dependencies would not resolve the observed failure: at a hybrid VMware and Azure business continuity team, administrators find that Azure Site Recovery test failover starts a VM in the target region on the wrong subnet and breaks application access controls. A review is complete only when isolated test failover attaches a VM to the intended recovery subnet with expected network policies. Configure target virtual-network and subnet mapping for the protected VM and validate NSG and DNS prerequisites.

C:

Reviewing Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings would not resolve the observed failure: at a hybrid VMware and Azure business continuity team, administrators find that Azure Site Recovery test failover starts a VM in the target region on the wrong subnet and breaks application access controls. Configure target virtual-network and subnet mapping for the protected VM and validate NSG and DNS prerequisites.

D:

Configure supported certificate-based Replica authentication, firewall port access and matching server names. Addresses another workflow. At a hybrid VMware and Azure business continuity team, administrators find that Azure Site Recovery test failover starts a VM in the target region on the wrong subnet and breaks application access controls. Configure target virtual-network and subnet mapping for the protected VM and validate NSG and DNS prerequisites.

Question 366

At an enterprise Windows Server disaster recovery program, administrators find that An encrypted Windows VM backup restores its disks but the recovery process lacks the original accessible key material to unlock the guest. The case is being investigated during a quarterly recovery rehearsal. The incident trace shows restore activity succeeds at the storage layer but boot logs show disk encryption key retrieval failure. Which proposed action and matching validation would address the same root cause?

  1. prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata — verify: a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls
  2. repair supported replication appliance registration, agent health and required Azure connectivity — verify: consistent recovery points resume and measured replication lag returns within the planned recovery-point objective
  3. prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata — verify: after failover and reverse setup both partners show healthy replication and controlled return is documented
  4. review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings — verify: a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls

Explanation

Correct Answer

A:

Prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata. Verify that a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls. A correct repair plan pairs prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata with a direct test: a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls. Restore activity succeeds at the storage layer but boot logs show disk encryption key retrieval failure.

Incorrect Answers

B:

Consistent recovery points resume and measured replication lag returns within the planned recovery-point objective. The required validation is different: a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls. Prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata.

C:

After failover and reverse setup both partners show healthy replication and controlled return is documented. It would not verify that a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls. Restore activity succeeds at the storage layer but boot logs show disk encryption key retrieval failure.

D:

A restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls. To correct the reported problem, prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata. A correct repair plan pairs prepare supported encrypted-VM restore prerequisites including Key Vault permissions and retained encryption metadata with a direct test: a restored isolated VM boots and decrypts its volumes using authorized retained keys.

Question 367

During a monthly compliance verification for a corporate Azure-hosted Windows Server operations unit, administrators confirm that An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. The solution must preserve other approved service dependencies. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. create and enforce a validated AD authentication policy silo binding privileged accounts and permitted authentication services
  2. enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding
  3. enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement
  4. configure a valid conditional forwarder or Azure DNS Private Resolver path for the private zone

Explanation

Correct Answer

C:

Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement. NTLM elimination should be evidence-led because untested protocol removal can interrupt dependent applications; adjacent fixes would not necessarily preserve the intended security or availability boundary. An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller.

Incorrect Answers

A:

Create and enforce a validated AD authentication policy silo binding privileged accounts and permitted authentication services. Addresses another workflow. An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement.

B:

Enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding. NTLM elimination should be evidence-led because untested protocol removal can interrupt dependent applications; adjacent fixes would not necessarily preserve the intended security or availability boundary. An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement.

D:

Configure a valid conditional forwarder or Azure DNS Private Resolver path for the private zone. An organization wants to disable NTLM immediately although a business-critical scanner still negotiates NTLM with a domain controller. Enable targeted NTLM audit policies, identify remaining dependencies, migrate them to supported authentication and phase enforcement because nTLM elimination should be evidence-led because untested protocol removal can interrupt dependent applications; adjacent fixes would not necessarily preserve the intended security or availability boundary.

Question 368

During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that An Azure Migrate assessment finds only half of the intended VMware servers because discovery credentials cannot read guest operating system details. The solution must preserve other approved service dependencies. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target
  2. run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing
  3. repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory
  4. map application settings and database access to approved App Service configuration with secret custody and identity permissions

Explanation

Correct Answer

C:

Repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory. Discovery credentials cannot read guest operating system details. Appliance logs show successful vCenter enumeration but failed guest discovery credentials for missing machines.

Incorrect Answers

A:

Perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target. Appliance logs show successful vCenter enumeration but failed guest discovery credentials for missing machines. Repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory.

B:

Running supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing would not resolve the observed failure: appliance logs show successful vCenter enumeration but failed guest discovery credentials for missing machines. Repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory.

D:

Map application settings and database access to approved App Service configuration with secret custody and identity permissions. Discovery credentials cannot read guest operating system details. Appliance logs show successful vCenter enumeration but failed guest discovery credentials for missing machines. Repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory.

Question 369

During a quarterly recovery rehearsal for an enterprise Windows Server disaster recovery program, administrators confirm that An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. The solution must preserve other approved service dependencies. The administrators propose to review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings. What measurable verification would demonstrate that the original failure has been corrected?

  1. an application-consistent database restore completes to a recovery environment within retention targets
  2. sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region
  3. recovered VM boots with the expected disk state and passes application acceptance in an isolated network
  4. a complete nonproduction recovery-plan test brings up tiers in dependency order with application transactions passing

Explanation

Correct Answer

B:

Sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region. Replication policies must be measured against recovery requirements rather than relying on a generic protected badge. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan.

Incorrect Answers

A:

An application-consistent database restore completes to a recovery environment within retention targets. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan. Sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region because replication policies must be measured against recovery requirements rather than relying on a generic protected badge.

C:

Recovered VM boots with the expected disk state and passes application acceptance in an isolated network. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan. Sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region.

D:

“A complete nonproduction recovery-plan test brings up tiers in dependency order with application transactions passing” does not explain the observed failure: aSR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan. Sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region.

Question 370

At an Active Directory hybrid troubleshooting group, administrators find that Group Policy scripts differ between domain controllers because DFSR SYSVOL replication stalled after an unplanned shutdown. The case is being investigated during a replication and authentication health review. Before implementing the proposed change (check DFS Replication event state, partner reachability and perform supported nonauthoritative synchronization where appropriate), which observed evidence most strongly substantiates the technical diagnosis?

  1. dfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding
  2. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs
  3. BitLocker recovery screen identifies a TPM protector validation mismatch after the hardware change
  4. event log properties show oldest records younger than the required retention window during a busy sign-in day

Explanation

Correct Answer

A:

DfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding. SYSVOL file replication is a separate health dependency from Active Directory database replication. At an Active Directory hybrid troubleshooting group, administrators find that Group Policy scripts differ between domain controllers because DFSR SYSVOL replication stalled after an unplanned shutdown.

Incorrect Answers

B:

The proposed step “PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs” would leave the problem unresolved: at an Active Directory hybrid troubleshooting group, administrators find that Group Policy scripts differ between domain controllers because DFSR SYSVOL replication stalled after an unplanned shutdown. DfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding.

C:

“BitLocker recovery screen identifies a TPM protector validation mismatch after the hardware change” does not explain the observed failure: at an Active Directory hybrid troubleshooting group, administrators find that Group Policy scripts differ between domain controllers because DFSR SYSVOL replication stalled after an unplanned shutdown. SYSVOL file replication is a separate health dependency from Active Directory database replication. DfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding.

D:

“Event log properties show oldest records younger than the required retention window during a busy sign-in day” does not explain the observed failure: at an Active Directory hybrid troubleshooting group, administrators find that Group Policy scripts differ between domain controllers because DFSR SYSVOL replication stalled after an unplanned shutdown. SYSVOL file replication is a separate health dependency from Active Directory database replication. DfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding.

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