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

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.

Question 131

At an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. The case is being investigated during a critical-service alert and telemetry test. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity
  2. verify required dependency-map collection configuration and supported VM Insights agents and connectivity
  3. create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions
  4. restore AD-integrated DNS replication and correct client DNS resolver assignment for the domain namespace

Explanation

Correct Answer

A:

Restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity. A review is complete only when restored group retains its original SID and membership and access checks regain expected rights. At an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information.

Incorrect Answers

B:

Verifying required dependency-map collection configuration and supported VM Insights agents and connectivity would not resolve the observed failure: at an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. A review is complete only when restored group retains its original SID and membership and access checks regain expected rights. Restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity.

C:

Creating an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions addresses a separate aspect of the case. At an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. Restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity.

D:

“Restore AD-integrated DNS replication and correct client DNS resolver assignment for the domain namespace” does not explain the observed failure: at an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. Restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity.

Question 132

During a migration wave readiness review for a corporate datacenter-to-Azure transformation project, administrators confirm that A Hyper-V VM migration fails because its checkpoint disk chain references files on a storage volume not moved with the main VHDX. The solution must preserve other approved service dependencies. Before implementing the proposed change (use supported Hyper-V move/export procedures to transfer the complete VM configuration and referenced differencing disks), which observed evidence most strongly substantiates the technical diagnosis?

  1. VM configuration reports missing parent AVHDX paths after only base disk files were copied
  2. dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group
  3. access checks show new accounts authenticate yet their token lacks identities referenced by old file ACL entries
  4. clients receive inconsistent router options from old and new authorized DHCP servers on the same subnet

Explanation

Correct Answer

A:

VM configuration reports missing parent AVHDX paths after only base disk files were copied. The indicated corrective path is use supported Hyper-V move/export procedures to transfer the complete VM configuration and referenced differencing disks; acceptance requires the destination VM starts with consistent checkpoints and all expected virtual disks available.

Incorrect Answers

B:

Dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group. VM configuration reports missing parent AVHDX paths after only base disk files were copied.

C:

Access checks show new accounts authenticate yet their token lacks identities referenced by old file ACL entries. VM configuration reports missing parent AVHDX paths after only base disk files were copied because the indicated corrective path is use supported Hyper-V move/export procedures to transfer the complete VM configuration and referenced differencing disks; acceptance requires the destination VM starts with consistent checkpoints and all expected virtual disks available.

D:

Clients receive inconsistent router options from old and new authorized DHCP servers on the same subnet. The strongest of the offered choices. VM configuration reports missing parent AVHDX paths after only base disk files were copied.

Question 133

At a multi-branch Active Directory services team, administrators find that Local administrator passwords on several domain-joined servers remain identical and are reused during an emergency support shift. The case is being investigated during a domain security hardening review. The administrators propose to deploy Windows LAPS with correct directory backup permissions, rotation schedule and authorized retrieval auditing. What measurable verification would demonstrate that the original failure has been corrected?

  1. simulated on-premises password changes reject a banned pattern while normal password resets succeed
  2. approved print-management clients work while guest-network SMB probes fail and the scoped rule remains effective
  3. test execution blocks the unauthorized binary while signed approved application binaries and recovery tools remain usable
  4. each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

“Simulated on-premises password changes reject a banned pattern while normal password resets succeed” does not explain the observed failure: password inspection finds identical unmanaged local administrator credentials on unrelated member servers. Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret.

B:

Approved print-management clients work while guest-network SMB probes fail and the scoped rule remains effective. Addresses another workflow. Password inspection finds identical unmanaged local administrator credentials on unrelated member servers. Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret.

C:

Test execution blocks the unauthorized binary while signed approved application binaries and recovery tools remain usable. Per-device local administrator password rotation prevents one recovered secret from granting access across the server fleet. Password inspection finds identical unmanaged local administrator credentials on unrelated member servers. Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret.

Question 134

At a Windows Server modernization migration team, administrators find that A legacy IIS application is packaged into a Windows container using an incompatible base image and the container cannot start on the target host. The case is being investigated during a staged source-to-target cutover. Before implementing the proposed change (choose a supported Windows container base image and host isolation mode compatible with the workload), which observed evidence most strongly substantiates the technical diagnosis?

  1. directory discovery shows a legacy DC version below the intended forest functional-level prerequisites
  2. container creation events show Windows build compatibility errors before any application code runs
  3. appliance logs show successful vCenter enumeration but failed guest discovery credentials for missing machines
  4. DNS and network diagnostics show both old and new hosts answering the legacy file-server name

Explanation

Correct Answer

B:

Container creation events show Windows build compatibility errors before any application code runs. Windows container deployment requires a compatible kernel or isolation relationship between image and host. At a Windows Server modernization migration team, administrators find that A legacy IIS application is packaged into a Windows container using an incompatible base image and the container cannot start on the target host.

Incorrect Answers

A:

“Directory discovery shows a legacy DC version below the intended forest functional-level prerequisites” does not explain the observed failure: at a Windows Server modernization migration team, administrators find that A legacy IIS application is packaged into a Windows container using an incompatible base image and the container cannot start on the target host. Windows container deployment requires a compatible kernel or isolation relationship between image and host. Container creation events show Windows build compatibility errors before any application code runs.

C:

“Appliance logs show successful vCenter enumeration but failed guest discovery credentials for missing machines” does not explain the observed failure: at a Windows Server modernization migration team, administrators find that A legacy IIS application is packaged into a Windows container using an incompatible base image and the container cannot start on the target host. Container creation events show Windows build compatibility errors before any application code runs.

D:

“DNS and network diagnostics show both old and new hosts answering the legacy file-server name” concerns a different part of the problem. At a Windows Server modernization migration team, administrators find that A legacy IIS application is packaged into a Windows container using an incompatible base image and the container cannot start on the target host. Container creation events show Windows build compatibility errors before any application code runs.

Question 135

During a domain security hardening review for a multi-branch Active Directory services team, administrators confirm that A domain-joined server starts applying a public Windows Defender Firewall profile after DNS and domain-controller reachability change during failover. The solution must preserve other approved service dependencies. The incident trace shows Get-NetConnectionProfile shows a public category while secure domain-controller authentication and DNS fail. Which proposed action and matching validation would address the same root cause?

  1. verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts — verify: the supported server reports Credential Guard running and a controlled credential-theft simulation cannot reuse protected secrets
  2. repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall — verify: the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable
  3. deploy supported Microsoft Entra Password Protection proxy and DC agents with registered forest configuration and staged enforcement — verify: the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable
  4. repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall — verify: approved print-management clients work while guest-network SMB probes fail and the scoped rule remains effective

Explanation

Correct Answer

B:

Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall. Verify that the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. A correct repair plan pairs repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall with a direct test: the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. Get-NetConnectionProfile shows a public category while secure domain-controller authentication and DNS fail.

Incorrect Answers

A:

The supported server reports Credential Guard running and a controlled credential-theft simulation cannot reuse protected secrets. The required validation is different: the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall.

C:

The correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. To correct the reported problem, repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall. A correct repair plan pairs repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall with a direct test: the correct domain firewall profile applies after.

D:

Approved print-management clients work while guest-network SMB probes fail and the scoped rule remains effective. It would not verify that the correct domain firewall profile applies after connectivity recovery and only intended ports are reachable. Get-NetConnectionProfile shows a public category while secure domain-controller authentication and DNS fail.

Question 136

At an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. The case is being investigated during a critical-service alert and telemetry test. Which system engineering principle most directly explains why the remedy to restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity is appropriate?

  1. infrastructure performance telemetry and workload dependency mapping use different data streams and onboarding requirements
  2. Windows recovery requires verifying boot-chain and disk mappings rather than blindly reprovisioning the OS
  3. recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce
  4. repeatable performance diagnosis depends on persistent sampling and bounded collection storage

Explanation

Correct Answer

C:

Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce. Applying restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity should then yield restored group retains its original SID and membership and access checks regain expected rights. At an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information.

Incorrect Answers

A:

“Infrastructure performance telemetry and workload dependency mapping use different data streams and onboarding requirements” concerns a different part of the problem. At an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce.

B:

Applying restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity should then yield restored group retains its original SID and membership and access checks regain expected rights. At an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. The proposed action “Windows recovery requires verifying boot-chain and disk mappings rather than blindly reprovisioning the OS” would not resolve that situation. Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce.

D:

“Repeatable performance diagnosis depends on persistent sampling and bounded collection storage” does not explain the observed failure: at an Azure Arc and Windows Server fleet operations team, administrators find that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. Applying restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity should then yield restored group retains its original SID and membership and access checks regain expected rights. Recovering an identity preserves authorization continuity that a same-name replacement object cannot reproduce.

Question 137

During a maintenance window with failover validation for a Windows Server failover cluster operations group, administrators confirm that A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to check fault domains and reserve capacity, then complete supported Repair-VirtualDisk or storage jobs is appropriate?

  1. S2D pool eligibility depends on consistent supported hardware and clean disk ownership state
  2. distributed storage rebuild needs usable placement capacity across independent fault domains
  3. workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership
  4. storage-tier performance depends on correctly categorized physical media and supported cache behavior

Explanation

Correct Answer

B:

Distributed storage rebuild needs usable placement capacity across independent fault domains. A resulting state where the volumes regain healthy resiliency and simulated node loss does not interrupt supported workloads would be the corresponding validation. A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity.

Incorrect Answers

A:

S2D pool eligibility depends on consistent supported hardware and clean disk ownership state. A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. Distributed storage rebuild needs usable placement capacity across independent fault domains.

C:

Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership. Addresses another workflow. A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. Distributed storage rebuild needs usable placement capacity across independent fault domains.

D:

Storage-tier performance depends on correctly categorized physical media and supported cache behavior. A resulting state where the volumes regain healthy resiliency and simulated node loss does not interrupt supported workloads would be the corresponding validation. A Storage Spaces Direct node replacement finishes but virtual disks remain in degraded resiliency because repair jobs lack usable free capacity. Distributed storage rebuild needs usable placement capacity across independent fault domains.

Question 138

At an Azure-hosted clustered application service, administrators find that A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. The case is being investigated during a load-balanced access and cluster-node test. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. validate S2D disk and controller eligibility, clean retired metadata and replace unsupported media before enabling the pool
  2. configure supported workgroup cluster local identities, certificates and name resolution consistently on every node
  3. reevaluate dynamic quorum and witness placement, then configure supported cloud witness for balanced recovery behavior
  4. follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood

Explanation

Correct Answer

B:

Configure supported workgroup cluster local identities, certificates and name resolution consistently on every node. Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership; adjacent fixes would not necessarily preserve the intended security or availability boundary. At an Azure-hosted clustered application service, administrators find that A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration.

Incorrect Answers

A:

Validating S2D disk and controller eligibility, clean retired metadata and replace unsupported media before enabling the pool would not resolve the observed failure: at an Azure-hosted clustered application service, administrators find that A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership; adjacent fixes would not necessarily preserve the intended security or availability boundary. Configure supported workgroup cluster local identities, certificates and name resolution consistently on every node.

C:

“Reevaluate dynamic quorum and witness placement, then configure supported cloud witness for balanced recovery behavior” does not demonstrate what is needed when at an Azure-hosted clustered application service, administrators find that A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. Configure supported workgroup cluster local identities, certificates and name resolution consistently on every node.

D:

Following the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood would not resolve the observed failure: at an Azure-hosted clustered application service, administrators find that A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. Configure supported workgroup cluster local identities, certificates and name resolution consistently on every node.

Question 139

During a documented recovery-point review for a hybrid VMware and Azure business continuity team, administrators confirm that Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to configure supported certificate-based Replica authentication, firewall port access and matching server names is appropriate?

  1. encrypted backup is not recoverable without available compatible protectors and keys
  2. Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust
  3. failover rehearsal must end with safe environment cleanup and preserved disaster recovery capability
  4. disaster recovery replication includes logical network mapping beyond copying operating system disks

Explanation

Correct Answer

B:

Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust. The authentication certificates lack appropriate trust or name identity, produces the distinctive clue event logs show Replica authentication failed due to certificate identity or trust chain mismatch. Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity.

Incorrect Answers

A:

Encrypted backup is not recoverable without available compatible protectors and keys. The authentication certificates lack appropriate trust or name identity, produces the distinctive clue event logs show Replica authentication failed due to certificate identity or trust chain mismatch. Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust.

C:

Failover rehearsal must end with safe environment cleanup and preserved disaster recovery capability. Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust because the authentication certificates lack appropriate trust or name identity, produces the distinctive clue event logs show Replica authentication failed due to certificate identity or trust chain mismatch.

D:

Disaster recovery replication includes logical network mapping beyond copying operating system disks. Two workgroup Hyper-V hosts cannot establish Replica over HTTPS because the authentication certificates lack appropriate trust or name identity. Hyper-V Replica across untrusted domains relies on correctly bound server identity and certificate trust.

Question 140

At an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP. The case is being investigated during a maintenance-window root-cause analysis. Which system engineering principle most directly explains why the remedy to inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security is appropriate?

  1. hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation
  2. Kerberos authentication depends on sufficiently synchronized time throughout the domain trust hierarchy
  3. directory replication recovery must respect deletion lifetime and prevent obsolete objects reentering the forest
  4. VM extension health is an agent and handler execution question independent of RDP connectivity

Explanation

Correct Answer

D:

VM extension health is an agent and handler execution question independent of RDP connectivity. Applying inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security should then yield extension transitions to succeeded and the expected monitoring signal appears after service restart. At an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP.

Incorrect Answers

A:

“Hybrid agent connection does not guarantee authorization and connectivity for each Arc extension operation” does not explain the observed failure: at an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP. VM extension health is an agent and handler execution question independent of RDP connectivity.

B:

“Kerberos authentication depends on sufficiently synchronized time throughout the domain trust hierarchy” concerns a different part of the problem. At an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP. VM extension health is an agent and handler execution question independent of RDP connectivity.

C:

Applying inspect extension handler logs, sequence prerequisites and repair supported agent registration without disabling broader Azure security should then yield extension transitions to succeeded and the expected monitoring signal appears after service restart. At an on-premises data center support group, administrators find that A required Azure Windows monitoring extension remains in provisioning state even though the VM can be reached through RDP. The proposed action “Directory replication recovery must respect deletion lifetime and prevent obsolete objects reentering the forest” would not resolve that situation. VM extension health is an agent and handler execution question independent of RDP connectivity.

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