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

Question 120

During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that An IIS application migrated into Azure App Service starts but fails outbound database access because connection strings and managed identity are not configured. The solution must preserve other approved service dependencies. The administrators propose to map application settings and database access to approved App Service configuration with secret custody and identity permissions. What measurable verification would demonstrate that the original failure has been corrected?

  1. authenticated application requests reach the database without publishing connection secrets into deployment files
  2. the destination VM starts with consistent checkpoints and all expected virtual disks available
  3. migration grouping includes the database dependency and a test wave preserves end-to-end application transactions
  4. clients renew from only the approved replacement server and receive the exact expected network options

Explanation

Correct Answer

A:

Authenticated application requests reach the database without publishing connection secrets into deployment files. Connection strings and managed identity are not configured; the pre-change evidence is App Service diagnostics show missing environment settings and rejected managed database authentication.

Incorrect Answers

B:

“The destination VM starts with consistent checkpoints and all expected virtual disks available” does not demonstrate what is needed when app Service diagnostics show missing environment settings and rejected managed database authentication. Authenticated application requests reach the database without publishing connection secrets into deployment files.

C:

“Migration grouping includes the database dependency and a test wave preserves end-to-end application transactions” does not explain the observed failure: app Service diagnostics show missing environment settings and rejected managed database authentication. Authenticated application requests reach the database without publishing connection secrets into deployment files.

D:

“Clients renew from only the approved replacement server and receive the exact expected network options” concerns a different part of the problem. App Service diagnostics show missing environment settings and rejected managed database authentication. Authenticated application requests reach the database without publishing connection secrets into deployment files.

Question 121

During a domain security hardening review for a multi-branch Active Directory services team, administrators confirm that A team assumes storage-service encryption alone meets a policy requiring guest-controlled encryption keys for a regulated Windows VM. 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. restore the exact supported Azure Disk Encryption key and secret permissions with a planned restart rehearsal
  2. select a supported at-rest encryption design and document whether guest-level or infrastructure-level control fulfills policy
  3. evaluate effective network security rules and place a narrow higher-priority deny ahead of conflicting permits
  4. configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events

Explanation

Correct Answer

B:

Select a supported at-rest encryption design and document whether guest-level or infrastructure-level control fulfills policy. Storage-service encryption and guest or customer-managed key requirements protect different layers and must be evaluated separately. A team assumes storage-service encryption alone meets a policy requiring guest-controlled encryption keys for a regulated Windows VM. Compliance evidence proves the chosen disk and key control matches the policy and permitted recovery operations succeed.

Incorrect Answers

A:

Restore the exact supported Azure Disk Encryption key and secret permissions with a planned restart rehearsal. A team assumes storage-service encryption alone meets a policy requiring guest-controlled encryption keys for a regulated Windows VM. Select a supported at-rest encryption design and document whether guest-level or infrastructure-level control fulfills policy.

C:

Evaluating effective network security rules and place a narrow higher-priority deny ahead of conflicting permits would not resolve the observed failure: a team assumes storage-service encryption alone meets a policy requiring guest-controlled encryption keys for a regulated Windows VM. Storage-service encryption and guest or customer-managed key requirements protect different layers and must be evaluated separately. Select a supported at-rest encryption design and document whether guest-level or infrastructure-level control fulfills policy.

D:

Configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events. A team assumes storage-service encryption alone meets a policy requiring guest-controlled encryption keys for a regulated Windows VM. Select a supported at-rest encryption design and document whether guest-level or infrastructure-level control fulfills policy.

Question 122

During a staged source-to-target cutover for a Windows Server modernization migration team, administrators confirm that A high-volume file migration repeatedly restarts because copy jobs treat every changing file under active user sessions as a fatal inconsistency. The solution must preserve other approved service dependencies. The administrators propose to stage bulk transfer, schedule a controlled delta synchronization and cut over after validating open-handle closure. What measurable verification would demonstrate that the original failure has been corrected?

  1. migration grouping includes the database dependency and a test wave preserves end-to-end application transactions
  2. authenticated clients connect to the Azure application endpoint and the old location is safely made read-only
  3. source and destination inventories, hashes and permissions reconcile after final read-only cutover
  4. the container starts, passes HTTP and dependency tests, and an image provenance scan succeeds

Explanation

Correct Answer

C:

Source and destination inventories, hashes and permissions reconcile after final read-only cutover. Copy jobs treat every changing file under active user sessions as a fatal inconsistency, which was identified by incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours. A high-volume file migration repeatedly restarts because copy jobs treat every changing file under active user sessions as a fatal inconsistency.

Incorrect Answers

A:

Migration grouping includes the database dependency and a test wave preserves end-to-end application transactions. Addresses another workflow. A high-volume file migration repeatedly restarts because copy jobs treat every changing file under active user sessions as a fatal inconsistency. Source and destination inventories, hashes and permissions reconcile after final read-only cutover.

B:

Authenticated clients connect to the Azure application endpoint and the old location is safely made read-only. Copy jobs treat every changing file under active user sessions as a fatal inconsistency, which was identified by incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours. A high-volume file migration repeatedly restarts because copy jobs treat every changing file under active user sessions as a fatal inconsistency. Source and destination inventories, hashes and permissions reconcile after final read-only cutover.

D:

The container starts, passes HTTP and dependency tests, and an image provenance scan succeeds. A high-volume file migration repeatedly restarts because copy jobs treat every changing file under active user sessions as a fatal inconsistency. Source and destination inventories, hashes and permissions reconcile after final read-only cutover because copy jobs treat every changing file under active user sessions as a fatal inconsistency, which was identified by incremental transfer logs show active source file changes and inconsistent source-to-target hashes during office hours.

Question 123

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. Before implementing the proposed change (review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings), which observed evidence most strongly substantiates the technical diagnosis?

  1. event logs show Replica authentication failed due to certificate identity or trust chain mismatch
  2. protection group membership shows only volume-level backup while database consistency checks remain absent
  3. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan
  4. Replica state shows the recovered primary now holds the workload with no reverse replication configured

Explanation

Correct Answer

C:

ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan. Replication policies must be measured against recovery requirements rather than relying on a generic protected badge. An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. Sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region.

Incorrect Answers

A:

Event logs show Replica authentication failed due to certificate identity or trust chain mismatch. An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan.

B:

“Protection group membership shows only volume-level backup while database consistency checks remain absent” does not explain the observed failure: an Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan.

D:

Replica state shows the recovered primary now holds the workload with no reverse replication configured. Replication policies must be measured against recovery requirements rather than relying on a generic protected badge. An Azure VM is shown as protected but its replication policy violates the agreed recovery-point threshold and target-region choice. ASR policy diagnostics show replication lag and target-region inconsistency with the signed recovery plan.

Question 124

During an annual site outage simulation for a Windows Hyper-V replication operations unit, administrators confirm that A three-tier application fails after disaster failover because web nodes start before its database and domain services are ready. The solution must preserve other approved service dependencies. Before implementing the proposed change (create an Azure Site Recovery recovery plan with ordered groups, scripts and validated dependencies), which observed evidence most strongly substantiates the technical diagnosis?

  1. Replica state shows the recovered primary now holds the workload with no reverse replication configured
  2. disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services
  3. event logs show Replica authentication failed due to certificate identity or trust chain mismatch
  4. replication metadata references one former cluster node and errors occur after a legitimate role move

Explanation

Correct Answer

B:

Disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services. Web nodes start before its database and domain services are ready—could otherwise be mistaken for an unrelated infrastructure problem.

Incorrect Answers

A:

Replica state shows the recovered primary now holds the workload with no reverse replication configured. Disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services because web nodes start before its database and domain services are ready—could otherwise be mistaken for an unrelated infrastructure problem.

C:

Event logs show Replica authentication failed due to certificate identity or trust chain mismatch. Disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services.

D:

“Replication metadata references one former cluster node and errors occur after a legitimate role move” does not explain the observed failure: the strongest of the offered choices. Disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services.

Question 125

During a disaster-tolerant production failover rehearsal for a hybrid infrastructure availability team, administrators confirm that A two-site Windows failover cluster loses quorum after a site outage because all voting nodes reside in one failure domain. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to reevaluate dynamic quorum and witness placement, then configure supported cloud witness for balanced recovery behavior is appropriate?

  1. cluster availability depends on quorum voting design and failure-domain independence, not only node count
  2. Network ATC coordinates repeatable host networking and avoids drift between converged cluster nodes
  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

A:

Cluster availability depends on quorum voting design and failure-domain independence, not only node count. All voting nodes reside in one failure domain. A two-site Windows failover cluster loses quorum after a site outage because all voting nodes reside in one failure domain. A two-site Windows failover cluster loses quorum after a site outage because all voting nodes reside in one failure domain.

Incorrect Answers

B:

Network ATC coordinates repeatable host networking and avoids drift between converged cluster nodes. A two-site Windows failover cluster loses quorum after a site outage because all voting nodes reside in one failure domain. Cluster availability depends on quorum voting design and failure-domain independence, not only node count.

C:

S2D pool eligibility depends on consistent supported hardware and clean disk ownership state. A two-site Windows failover cluster loses quorum after a site outage because all voting nodes reside in one failure domain. Cluster availability depends on quorum voting design and failure-domain independence, not only node count because all voting nodes reside in one failure domain.

D:

“A reachable operating system is not proof of healthy cluster quorum, storage ownership or service state” does not explain the observed failure: a two-site Windows failover cluster loses quorum after a site outage because all voting nodes reside in one failure domain. All voting nodes reside in one failure domain. Cluster availability depends on quorum voting design and failure-domain independence, not only node count.

Question 126

At a corporate datacenter-to-Azure transformation project, administrators find that Operators upgrade a legacy application server in place without validating role support, resulting in an unbootable installed application service. The case is being investigated during a migration wave readiness review. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. choose a supported Windows container base image and host isolation mode compatible with the workload
  2. perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target
  3. use supported GPO migration tables and validate security filtering, WMI filters and link scope
  4. run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing

Explanation

Correct Answer

D:

Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing. An in-place OS upgrade cannot replace product and role compatibility testing. At a corporate datacenter-to-Azure transformation project, administrators find that Operators upgrade a legacy application server in place without validating role support, resulting in an unbootable installed application service.

Incorrect Answers

A:

Choosing a supported Windows container base image and host isolation mode compatible with the workload would not resolve the observed failure: at a corporate datacenter-to-Azure transformation project, administrators find that Operators upgrade a legacy application server in place without validating role support, resulting in an unbootable installed application service. Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing.

B:

Performing supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target is not a direct response to the evidence: at a corporate datacenter-to-Azure transformation project, administrators find that Operators upgrade a legacy application server in place without validating role support, resulting in an unbootable installed application service. Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing.

C:

Use supported GPO migration tables and validate security filtering, WMI filters and link scope. An in-place OS upgrade cannot replace product and role compatibility testing. At a corporate datacenter-to-Azure transformation project, administrators find that Operators upgrade a legacy application server in place without validating role support, resulting in an unbootable installed application service. Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing is the appropriate.

Question 127

During a privileged-access audit for a regulated Windows Server hybrid identity environment, administrators confirm that A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to replace the broad inbound exception with service-scoped source-restricted rules and validate GPO precedence is appropriate?

  1. encrypted VM recovery depends on least-privilege access to the original protected key material
  2. authentication silos restrict where high-value Kerberos identities can authenticate beyond traditional group-based file permissions
  3. application and service identifiers combined with remote-address scopes reduce firewall rule blast radius
  4. security posture improvement requires changing the evaluated resource state rather than dismissing a finding

Explanation

Correct Answer

C:

Application and service identifiers combined with remote-address scopes reduce firewall rule blast radius. A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable.

Incorrect Answers

A:

“Encrypted VM recovery depends on least-privilege access to the original protected key material” does not explain the observed failure: a Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable. Application and service identifiers combined with remote-address scopes reduce firewall rule blast radius.

B:

Authentication silos restrict where high-value Kerberos identities can authenticate beyond traditional group-based file permissions. A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable. Application and service identifiers combined with remote-address scopes reduce firewall rule blast radius.

D:

Security posture improvement requires changing the evaluated resource state rather than dismissing a finding. Addresses another workflow. A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable. Application and service identifiers combined with remote-address scopes reduce firewall rule blast radius.

Question 128

At a corporate datacenter-to-Azure transformation project, administrators find that Operators upgrade a legacy application server in place without validating role support, resulting in an unbootable installed application service. The case is being investigated during a migration wave readiness review. The incident trace shows readiness scan identifies an unsupported application dependency and the attempted upgrade fails post-reboot. Which proposed action and matching validation would address the same root cause?

  1. run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing — verify: clients from multiple sites receive the new healthy namespace target and legacy path access remains intact
  2. execute the validated Azure Migrate cutover and DNS/route transition plan with rollback checkpoints — verify: a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path
  3. run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing — verify: a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path
  4. enable supported dependency analysis and map observed application traffic before grouping migration waves — verify: migration grouping includes the database dependency and a test wave preserves end-to-end application transactions

Explanation

Correct Answer

C:

Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing. Verify that a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. In the relevant Windows Server or hybrid-cloud layer, an in-place OS upgrade cannot replace product and role compatibility testing. Readiness scan identifies an unsupported application dependency and the attempted upgrade fails post-reboot.

Incorrect Answers

A:

Clients from multiple sites receive the new healthy namespace target and legacy path access remains intact. It would not verify that a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. Readiness scan identifies an unsupported application dependency and the attempted upgrade fails post-reboot.

B:

A staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. To correct the reported problem, run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing. In the relevant Windows Server or hybrid-cloud layer, an in-place OS upgrade cannot replace product and role compatibility testing.

D:

Migration grouping includes the database dependency and a test wave preserves end-to-end application transactions. The required validation is different: a staged upgrade in a test clone preserves applications and role state with a recoverable rollback path. Run supported Windows Server upgrade compatibility checks with rollback and application owner signoff before production servicing.

Question 129

During a maintenance-window root-cause analysis for an on-premises data center support group, administrators confirm that An Azure Arc enabled Windows Server accepts inventory heartbeats but cannot install a policy extension because its outbound service path and resource permissions are incomplete. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to diagnose Arc agent service endpoints, proxy settings and role assignment before retrying extension deployment is appropriate?

  1. infrastructure performance telemetry and workload dependency mapping use different data streams and onboarding requirements
  2. hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation
  3. patch failures should be traced to configured update-source policy before deleting system components
  4. agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion

Explanation

Correct Answer

B:

Hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation. An Azure Arc enabled Windows Server accepts inventory heartbeats but cannot install a policy extension because its outbound service path and resource permissions are incomplete.

Incorrect Answers

A:

“Infrastructure performance telemetry and workload dependency mapping use different data streams and onboarding requirements” concerns a different part of the problem. An Azure Arc enabled Windows Server accepts inventory heartbeats but cannot install a policy extension because its outbound service path and resource permissions are incomplete. Hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation.

C:

The proposed step “Patch failures should be traced to configured update-source policy before deleting system components” would leave the problem unresolved: an Azure Arc enabled Windows Server accepts inventory heartbeats but cannot install a policy extension because its outbound service path and resource permissions are incomplete. Hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation.

D:

Agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion. An Azure Arc enabled Windows Server accepts inventory heartbeats but cannot install a policy extension because its outbound service path and resource permissions are incomplete. Hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation.

Question 130

At a corporate Azure-hosted Windows Server operations unit, administrators find that Domain controllers stop providing meaningful identity attack telemetry even though the cloud Defender for Identity portal still lists the environment. The case is being investigated during a monthly compliance verification. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. check sensor version, service health, network connectivity and identity permissions on affected domain controllers
  2. verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts
  3. create an audited Windows Defender Application Control policy that allows only approved signed applications and test in audit mode before enforcement
  4. configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events

Explanation

Correct Answer

A:

Check sensor version, service health, network connectivity and identity permissions on affected domain controllers. Microsoft Defender for Identity detections depend on complete and healthy sensor telemetry from relevant domain controllers. At a corporate Azure-hosted Windows Server operations unit, administrators find that Domain controllers stop providing meaningful identity attack telemetry even though the cloud Defender for Identity portal still lists the environment.

Incorrect Answers

B:

Verifying virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts would not resolve the observed failure: at a corporate Azure-hosted Windows Server operations unit, administrators find that Domain controllers stop providing meaningful identity attack telemetry even though the cloud Defender for Identity portal still lists the environment. Check sensor version, service health, network connectivity and identity permissions on affected domain controllers.

C:

Creating an audited Windows Defender Application Control policy that allows only approved signed applications and test in audit mode before enforcement is not a direct response to the evidence: at a corporate Azure-hosted Windows Server operations unit, administrators find that Domain controllers stop providing meaningful identity attack telemetry even though the cloud Defender for Identity portal still lists the environment. Check sensor version, service health, network connectivity and identity permissions on affected domain controllers.

D:

Microsoft Defender for Identity detections depend on complete and healthy sensor telemetry from relevant domain controllers. At a corporate Azure-hosted Windows Server operations unit, administrators find that Domain controllers stop providing meaningful identity attack telemetry even though the cloud Defender for Identity portal still lists the environment. Configuring appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events alone cannot establish that the failure is corrected. Check sensor version, service health, network connectivity and identity permissions on affected domain controllers.

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