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

Question 860

At an Azure Arc and Windows Server fleet operations team, administrators find that Performance Monitor counters are configured interactively but no long-term Data Collector Set exists to capture overnight application stalls. The case is being investigated during a critical-service alert and telemetry test. Before implementing the proposed change (create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions), which observed evidence most strongly substantiates the technical diagnosis?

  1. BitLocker recovery screen identifies a TPM protector validation mismatch after the hardware change
  2. morning investigations find no recorded performance evidence for a fault that occurred after operators closed PerfMon
  3. PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs
  4. WindowsUpdateClient logs show timeouts connecting to a decommissioned intranet update server

Explanation

Correct Answer

B:

Morning investigations find no recorded performance evidence for a fault that occurred after operators closed PerfMon. The indicated corrective path is create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions; acceptance requires the scheduled collection captures a deliberately induced slowdown with timestamps and disk limits enforced.

Incorrect Answers

A:

The indicated corrective path is create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions; acceptance requires the scheduled collection captures a deliberately induced slowdown with timestamps and disk limits enforced. Occurred after operators closed PerfMon. The proposed action “BitLocker recovery screen identifies a TPM protector validation mismatch after the hardware change” would not resolve that situation. Morning investigations find no recorded performance evidence for a fault that occurred after operators closed PerfMon.

C:

“PerfMon shows persistent Avg Disk sec/Transfer and queue growth synchronized with backup jobs” does not explain the observed failure: occurred after operators closed PerfMon. The indicated corrective path is create an appropriate Data Collector Set with saved counters, triggers, rollover and retention permissions. Morning investigations find no recorded performance evidence for a fault that occurred after operators closed PerfMon.

D:

WindowsUpdateClient logs show timeouts connecting to a decommissioned intranet update server. Occurred after operators closed PerfMon. Morning investigations find no recorded performance evidence for a fault that occurred after operators closed PerfMon.

Question 861

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. The administrators propose to restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity. What measurable verification would demonstrate that the original failure has been corrected?

  1. extension transitions to succeeded and the expected monitoring signal appears after service restart
  2. restored group retains its original SID and membership and access checks regain expected rights
  3. the scheduled collection captures a deliberately induced slowdown with timestamps and disk limits enforced
  4. a controlled application TCP connection appears in the VM dependency view without excessive log collection

Explanation

Correct Answer

B:

Restored group retains its original SID and membership and access checks regain expected rights. An unrelated improvement in throughput, monitoring or provisioning cannot replace this causal test. 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:

“Extension transitions to succeeded and the expected monitoring signal appears after service restart” 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. Restored group retains its original SID and membership and access checks regain expected rights.

C:

An unrelated improvement in throughput, monitoring or provisioning cannot replace this causal test. 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 “The scheduled collection captures a deliberately induced slowdown with timestamps and disk limits enforced” would not resolve that situation. Restored group retains its original SID and membership and access checks regain expected rights.

D:

The proposed step “A controlled application TCP connection appears in the VM dependency view without excessive log collection” would leave the problem unresolved: 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. Restored group retains its original SID and membership and access checks regain expected rights.

Question 862

During a controlled security baseline change for a Windows Server 2025 workload fleet with Azure Arc, administrators confirm that Azure Arc enabled on-premises servers are inventoried but lack the intended Microsoft Defender for Servers coverage. The solution must preserve other approved service dependencies. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. reconcile connection security rules and certificate or Kerberos authentication prerequisites on both endpoints
  2. assign corrective actions through Defender for Cloud recommendations with Azure Policy-backed compliance verification
  3. verify virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts
  4. enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding

Explanation

Correct Answer

D:

Enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding. A review is complete only when the targeted Arc server reports correct coverage and its supported security posture findings appear without duplicate enrollment. Azure Arc enabled on-premises servers are inventoried but lack the intended Microsoft Defender for Servers coverage.

Incorrect Answers

A:

Reconciling connection security rules and certificate or Kerberos authentication prerequisites on both endpoints would not resolve the observed failure: azure Arc enabled on-premises servers are inventoried but lack the intended Microsoft Defender for Servers coverage. A review is complete only when the targeted Arc server reports correct coverage and its supported security posture findings appear without duplicate enrollment. Enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding.

B:

Assign corrective actions through Defender for Cloud recommendations with Azure Policy-backed compliance verification. Azure Arc enabled on-premises servers are inventoried but lack the intended Microsoft Defender for Servers coverage. Enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding.

C:

Verifying virtualization-based security prerequisites and enable Credential Guard on supported Windows Server hosts would not resolve the observed failure: azure Arc enabled on-premises servers are inventoried but lack the intended Microsoft Defender for Servers coverage. Enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding.

Question 863

During a planned primary-site outage exercise for a two-site datacenter high-availability team, administrators confirm that Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. The solution must preserve other approved service dependencies. Which system engineering principle most directly explains why the remedy to follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood is appropriate?

  1. synchronous multi-site failover depends on storage replication latency and independent quorum design
  2. clustered client identities require valid AD computer objects and controlled delegation for virtual names
  3. mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes
  4. S2D pool eligibility depends on consistent supported hardware and clean disk ownership state

Explanation

Correct Answer

C:

Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation.

Incorrect Answers

A:

Synchronous multi-site failover depends on storage replication latency and independent quorum design. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes.

B:

Clustered client identities require valid AD computer objects and controlled delegation for virtual names. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes because the intended choice is about the precise control relationship rather than a general Windows Server best practice.

D:

S2D pool eligibility depends on consistent supported hardware and clean disk ownership state. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Mixed-version cluster transitions must respect supported sequencing and irreversible functional-level changes.

Question 864

At an Azure-hosted clustered application service, administrators find that A failover cluster experiences sporadic node eviction after a NIC driver update performed outside coordinated maintenance. The case is being investigated during a load-balanced access and cluster-node test. The incident trace shows validation reports a version or driver discrepancy on one node immediately after maintenance. Which proposed action and matching validation would address the same root cause?

  1. rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests — verify: the role transitions to another healthy node and users retain required service continuity during drained maintenance
  2. prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity — verify: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers
  3. configure the supported Azure load balancer front end, health probe and cluster IP resource integration — verify: client connection tests succeed through the load balancer before and after role failover
  4. rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests — verify: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers

Explanation

Correct Answer

D:

Rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests. Verify that all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. Cluster supportability depends on consistent validated drivers and software across all participating nodes.

Incorrect Answers

A:

The role transitions to another healthy node and users retain required service continuity during drained maintenance. It would not verify that all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. All nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers.

B:

All nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. To correct the reported problem, rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests. Cluster supportability depends on consistent validated drivers and software across all participating nodes.

C:

Client connection tests succeed through the load balancer before and after role failover. The required validation is different: all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. Rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests.

Question 865

At an enterprise IIS, storage and AD platform upgrade program, administrators find that A migration cutover assigns the destination the old server name before updating DNS and source NIC ownership, causing duplicate network identities. The case is being investigated during a production compatibility validation cycle. The administrators propose to perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification. What measurable verification would demonstrate that the original failure has been corrected?

  1. an isolated test copy boots and passes checks without exposing public services or altering source workloads
  2. approved users can access intended paths and unauthorized users remain denied under both share and NTFS controls
  3. mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes
  4. representative target computers process the intended GPO with translated principals and no unauthorized application

Explanation

Correct Answer

C:

Mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes. Identity and client namespace transitions must be atomic enough to prevent split-brain file service during migration. DNS and network diagnostics show both old and new hosts answering the legacy file-server name.

Incorrect Answers

A:

“An isolated test copy boots and passes checks without exposing public services or altering source workloads” does not demonstrate what is needed when dNS and network diagnostics show both old and new hosts answering the legacy file-server name. Mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes.

B:

“Approved users can access intended paths and unauthorized users remain denied under both share and NTFS controls” does not explain the observed failure: DNS and network diagnostics show both old and new hosts answering the legacy file-server name. Mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes.

D:

Identity and client namespace transitions must be atomic enough to prevent split-brain file service during migration. DNS and network diagnostics show both old and new hosts answering the legacy file-server name. The proposed action “Representative target computers process the intended GPO with translated principals and no unauthorized application” would not resolve that situation. Mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes.

Question 866

During a documented recovery-point review for a hybrid VMware and Azure business continuity team, administrators confirm that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its selected recovery policy excludes the database. The solution must preserve other approved service dependencies. The incident trace shows protection group membership shows only volume-level backup while database consistency checks remain absent. Which proposed action and matching validation would address the same root cause?

  1. configure MABS protection group with application-aware backups and suitable local and Azure retention — verify: an application-consistent database restore completes to a recovery environment within retention targets
  2. perform supported planned failover, commit and reverse replication after checking source and target state — verify: after failover and reverse setup both partners show healthy replication and controlled return is documented
  3. configure target virtual-network and subnet mapping for the protected VM and validate NSG and DNS prerequisites — verify: an application-consistent database restore completes to a recovery environment within retention targets
  4. configure MABS protection group with application-aware backups and suitable local and Azure retention — verify: consistent recovery points resume and measured replication lag returns within the planned recovery-point objective

Explanation

Correct Answer

A:

Configure MABS protection group with application-aware backups and suitable local and Azure retention. Verify that an application-consistent database restore completes to a recovery environment within retention targets. Workload-aware backup requires protection group inclusion and recoverable application-state checkpoints. During a documented recovery-point review for a hybrid VMware and Azure business continuity team, administrators confirm that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its.

Incorrect Answers

B:

After failover and reverse setup both partners show healthy replication and controlled return is documented. The required validation is different: an application-consistent database restore completes to a recovery environment within retention targets. During a documented recovery-point review for a hybrid VMware and Azure business continuity team, administrators confirm that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its. Configure MABS protection group with application-aware backups and suitable local and Azure retention.

C:

An application-consistent database restore completes to a recovery environment within retention targets. To correct the reported problem, configure MABS protection group with application-aware backups and suitable local and Azure retention. Workload-aware backup requires protection group inclusion and recoverable application-state checkpoints. During a documented recovery-point review for a hybrid VMware and Azure business continuity team, administrators confirm that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its selected recovery policy excludes the database.

D:

Consistent recovery points resume and measured replication lag returns within the planned recovery-point objective. It would not verify that an application-consistent database restore completes to a recovery environment within retention targets. An application-consistent database restore completes to a recovery environment within retention targets.

Question 867

During a planned primary-site outage exercise for a two-site datacenter high-availability team, administrators confirm that A Scale-Out File Server offers continuously available shares but client SMB sessions drop when one cluster node restarts. 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. configure the supported Azure load balancer front end, health probe and cluster IP resource integration
  2. verify continuously available SMB share settings and redundant SMB Multichannel network paths
  3. check fault domains and reserve capacity, then complete supported Repair-VirtualDisk or storage jobs
  4. verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior

Explanation

Correct Answer

B:

Verify continuously available SMB share settings and redundant SMB Multichannel network paths. Scale-Out File Server reliability combines continuously available share semantics with redundant network paths. SMB client traces show no alternate connection path when a file-server node enters maintenance.

Incorrect Answers

A:

Configure the supported Azure load balancer front end, health probe and cluster IP resource integration. Scale-Out File Server reliability combines continuously available share semantics with redundant network paths. SMB client traces show no alternate connection path when a file-server node enters maintenance. Verify continuously available SMB share settings and redundant SMB Multichannel network paths.

C:

Check fault domains and reserve capacity, then complete supported Repair-VirtualDisk or storage jobs. SMB client traces show no alternate connection path when a file-server node enters maintenance. Verify continuously available SMB share settings and redundant SMB Multichannel network paths because scale-Out File Server reliability combines continuously available share semantics with redundant network paths.

D:

Verifying supported storage-replica topology, link requirements, witness placement and planned recovery behavior would not resolve the observed failure: sMB client traces show no alternate connection path when a file-server node enters maintenance. Scale-Out File Server reliability combines continuously available share semantics with redundant network paths. Verify continuously available SMB share settings and redundant SMB Multichannel network paths.

Question 868

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. Before implementing the proposed change (replace the broad inbound exception with service-scoped source-restricted rules and validate GPO precedence), which observed evidence most strongly substantiates the technical diagnosis?

  1. authentication telemetry shows privileged users successfully using NTLM to legacy hosts during administration
  2. KDC operational events show a privileged identity obtaining tickets for hosts outside the intended administrative boundary
  3. RODC replication policy reports a privileged group in the allowed-cache set and shows cached secrets for branch visitors
  4. effective firewall policy shows a global inbound permit unrelated to the print service identity

Explanation

Correct Answer

D:

Effective firewall policy shows a global inbound permit unrelated to the print service identity. 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:

“Authentication telemetry shows privileged users successfully using NTLM to legacy hosts during administration” 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. Effective firewall policy shows a global inbound permit unrelated to the print service identity.

B:

KDC operational events show a privileged identity obtaining tickets for hosts outside the intended administrative boundary. Addresses another workflow. A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable. Effective firewall policy shows a global inbound permit unrelated to the print service identity.

C:

RODC replication policy reports a privileged group in the allowed-cache set and shows cached secrets for branch visitors. 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. Effective firewall policy shows a global inbound permit unrelated to the print service identity.

Question 869

At a regulated Windows Server hybrid identity environment, administrators find that Windows Server 2025 application nodes deviate from an agreed security baseline after an in-place servicing operation. The case is being investigated during a privileged-access audit. The administrators propose to use supported OSConfig security baseline commands and reconcile documented exceptions through change control. What measurable verification would demonstrate that the original failure has been corrected?

  1. approved branch users authenticate during the planned disconnection test without any privileged administrator credentials cached
  2. a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table
  3. each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret
  4. subsequent audits show the target baseline and justified exceptions applied without breaking a documented workload

Explanation

Correct Answer

D:

Subsequent audits show the target baseline and justified exceptions applied without breaking a documented workload. An unrelated improvement in throughput, monitoring or provisioning cannot replace this causal test. At a regulated Windows Server hybrid identity environment, administrators find that Windows Server 2025 application nodes deviate from an agreed security baseline after an in-place servicing operation.

Incorrect Answers

A:

“Approved branch users authenticate during the planned disconnection test without any privileged administrator credentials cached” does not explain the observed failure: at a regulated Windows Server hybrid identity environment, administrators find that Windows Server 2025 application nodes deviate from an agreed security baseline after an in-place servicing operation. An unrelated improvement in throughput, monitoring or provisioning cannot replace this causal test. Subsequent audits show the target baseline and justified exceptions applied without breaking a documented workload.

B:

“A safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table” does not demonstrate what is needed when at a regulated Windows Server hybrid identity environment, administrators find that Windows Server 2025 application nodes deviate from an agreed security baseline after an in-place servicing operation. Subsequent audits show the target baseline and justified exceptions applied without breaking a documented workload.

C:

“Each target receives a unique rotated password and only delegated responders can retrieve its escrowed secret” does not explain the observed failure: at a regulated Windows Server hybrid identity environment, administrators find that Windows Server 2025 application nodes deviate from an agreed security baseline after an in-place servicing operation. Subsequent audits show the target baseline and justified exceptions applied without breaking a documented workload.

Question 870

During a signed business continuity acceptance test for an Azure backup and recovery engineering team, administrators confirm that During a planned datacenter maintenance, Hyper-V Replica failover succeeds but administrators forget reverse replication and leave the new primary unprotected. The solution must preserve other approved service dependencies. The administrators propose to perform supported planned failover, commit and reverse replication after checking source and target state. What measurable verification would demonstrate that the original failure has been corrected?

  1. a complete nonproduction recovery-plan test brings up tiers in dependency order with application transactions passing
  2. an application-consistent database restore completes to a recovery environment within retention targets
  3. a restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls
  4. after failover and reverse setup both partners show healthy replication and controlled return is documented

Explanation

Correct Answer

D:

After failover and reverse setup both partners show healthy replication and controlled return is documented. DR failover does not by itself restore ongoing data protection in the new primary direction. Replica state shows the recovered primary now holds the workload with no reverse replication configured.

Incorrect Answers

A:

The proposed step “A complete nonproduction recovery-plan test brings up tiers in dependency order with application transactions passing” would leave the problem unresolved: replica state shows the recovered primary now holds the workload with no reverse replication configured. After failover and reverse setup both partners show healthy replication and controlled return is documented.

B:

“An application-consistent database restore completes to a recovery environment within retention targets” does not explain the observed failure: replica state shows the recovered primary now holds the workload with no reverse replication configured. DR failover does not by itself restore ongoing data protection in the new primary direction. After failover and reverse setup both partners show healthy replication and controlled return is documented.

C:

“A restored isolated VM boots and decrypts its volumes using authorized retained keys without weakening security controls” does not explain the observed failure: replica state shows the recovered primary now holds the workload with no reverse replication configured. DR failover does not by itself restore ongoing data protection in the new primary direction. After failover and reverse setup both partners show healthy replication and controlled return is documented.

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