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

Question 990

During a load-balanced access and cluster-node test for an Azure-hosted clustered application service, administrators confirm that A new Windows failover cluster cannot create a clustered file-server name because the cluster computer account lacks AD permissions. The solution must preserve other approved service dependencies. The incident trace shows Failover Clustering logs show virtual computer object creation denied in the designated Active Directory container. Which proposed action and matching validation would address the same root cause?

  1. prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity — verify: the repaired node rejoins membership, passes validation and safely hosts a planned test role
  2. check fault domains and reserve capacity, then complete supported Repair-VirtualDisk or storage jobs — verify: a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights
  3. prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity — verify: a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights
  4. follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood — verify: node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change

Explanation

Correct Answer

C:

Prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity. Verify that a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. Clustered client identities require valid AD computer objects and controlled delegation for virtual names. During a load-balanced access and cluster-node test for an Azure-hosted clustered application service, administrators confirm that A new Windows failover cluster cannot create a clustered file-server name because the cluster computer account lacks AD permissions.

Incorrect Answers

A:

The repaired node rejoins membership, passes validation and safely hosts a planned test role. It would not verify that a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. A test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights.

B:

A test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. To correct the reported problem, prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity. Clustered client identities require valid AD computer objects and controlled delegation for virtual names. During a load-balanced access and cluster-node test for an Azure-hosted clustered application service, administrators confirm that A new Windows failover cluster cannot create a clustered file-server name because the cluster computer account lacks AD permissions.

D:

Node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. The required validation is different: a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. Prestage the required computer objects or delegate narrowly scoped Create Computer Objects rights to the cluster identity.

Question 991

At a Windows Server 2025 workload fleet with Azure Arc, administrators find that Hybrid Windows Server domain controller security logs never appear in Microsoft Sentinel despite the workspace being active. The case is being investigated during a controlled security baseline change. Before implementing the proposed change (configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events), which observed evidence most strongly substantiates the technical diagnosis?

  1. effective NSG rules show a broad allow with lower numerical priority value winning before the intended deny
  2. agent association and rule diagnostics show the controller is not associated with the required security event collection rule
  3. identity sensor health records show a disconnected sensor and no recent identity events for an active controller
  4. agent health reports no password-filter enforcement on domain controllers despite cloud policy activation

Explanation

Correct Answer

B:

Agent association and rule diagnostics show the controller is not associated with the required security event collection rule. The indicated corrective path is configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events; acceptance requires a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table. At a Windows Server 2025 workload fleet with Azure Arc, administrators find that Hybrid Windows Server domain controller security logs never appear in Microsoft Sentinel despite the workspace being active.

Incorrect Answers

A:

“Effective NSG rules show a broad allow with lower numerical priority value winning before the intended deny” does not demonstrate what is needed when the strongest of the offered choices. Agent association and rule diagnostics show the controller is not associated with the required security event collection rule.

C:

“Identity sensor health records show a disconnected sensor and no recent identity events for an active controller” concerns a different part of the problem. Agent association and rule diagnostics show the controller is not associated with the required security event collection rule.

D:

The indicated corrective path is configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events; acceptance requires a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table. The strongest of the offered choices. The proposed action “Agent health reports no password-filter enforcement on domain controllers despite cloud policy activation” would not resolve that situation. Agent association and rule diagnostics show the controller is not associated with the required security event collection rule.

Question 992

At an enterprise Windows Server disaster recovery program, administrators find that During a planned datacenter maintenance, Hyper-V Replica failover succeeds but administrators forget reverse replication and leave the new primary unprotected. The case is being investigated during a quarterly recovery rehearsal. Before implementing the proposed change (perform supported planned failover, commit and reverse replication after checking source and target state), which observed evidence most strongly substantiates the technical diagnosis?

  1. disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services
  2. Replica state shows the recovered primary now holds the workload with no reverse replication configured
  3. ASR test failover details list a default target network inconsistent with the disaster-recovery application plan
  4. replication health reports a stale configuration server or repeated agent authentication failure

Explanation

Correct Answer

B:

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. Administrators find that During a planned datacenter maintenance, Hyper-V Replica failover succeeds but administrators forget reverse replication and leave the new primary unprotected.

Incorrect Answers

A:

“Disaster-recovery logs show front-end startup preceding successful database connectivity and authentication services” does not explain the observed failure: administrators find that During a planned datacenter maintenance, Hyper-V Replica failover succeeds but administrators forget reverse replication and leave the new primary unprotected. 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.

C:

“ASR test failover details list a default target network inconsistent with the disaster-recovery application plan” does not demonstrate what is needed when administrators find that During a planned datacenter maintenance, Hyper-V Replica failover succeeds but administrators forget reverse replication and leave the new primary unprotected. Replica state shows the recovered primary now holds the workload with no reverse replication configured.

D:

“Replication health reports a stale configuration server or repeated agent authentication failure” does not explain the observed failure: administrators find that During a planned datacenter maintenance, Hyper-V Replica failover succeeds but administrators forget reverse replication and leave the new primary unprotected. Replica state shows the recovered primary now holds the workload with no reverse replication configured.

Question 993

During a load-balanced access and cluster-node test for an Azure-hosted clustered application service, administrators confirm that A cluster health dashboard shows green while individual nodes report failed storage jobs that the central dashboard is not collecting. 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. repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection
  2. configure supported workgroup cluster local identities, certificates and name resolution consistently on every node
  3. use supported Suspend-ClusterNode drain and live role movement before taking the node offline
  4. configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks

Explanation

Correct Answer

A:

Repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection. Centralized administrative tools must corroborate health with node-level telemetry instead of treating an empty dashboard as proof. Node event logs show storage timeouts absent from the central operational view.

Incorrect Answers

B:

Configure supported workgroup cluster local identities, certificates and name resolution consistently on every node. Node event logs show storage timeouts absent from the central operational view. Repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection.

C:

Use supported Suspend-ClusterNode drain and live role movement before taking the node offline. Node event logs show storage timeouts absent from the central operational view. Repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection because centralized administrative tools must corroborate health with node-level telemetry instead of treating an empty dashboard as proof.

D:

Configuring Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks would not resolve the observed failure: node event logs show storage timeouts absent from the central operational view. Centralized administrative tools must corroborate health with node-level telemetry instead of treating an empty dashboard as proof. Repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection.

Question 994

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. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. migrate session collection, licensing and profile prerequisites using a supported staged approach
  2. perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification
  3. repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory
  4. rerun supported storage inventory for files, shares and security before transferring data to the destination

Explanation

Correct Answer

B:

Perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification. Identity and client namespace transitions must be atomic enough to prevent split-brain file service during migration; adjacent fixes would not necessarily preserve the intended security or availability boundary. 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.

Incorrect Answers

A:

“Migrate session collection, licensing and profile prerequisites using a supported staged approach” does not explain the observed failure: 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. Perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification.

C:

Repair appliance access, scope permissions and guest discovery prerequisites, then rerun inventory. Identity and client namespace transitions must be atomic enough to prevent split-brain file service during migration; adjacent fixes would not necessarily preserve the intended security or availability boundary. 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. Perform the supported Storage Migration Service cutover sequence including identity transfer.

D:

The proposed step “Rerun supported storage inventory for files, shares and security before transferring data to the destination” would leave the problem unresolved: 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. Perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification.

Question 995

At a multi-branch Active Directory services team, administrators find that A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable. The case is being investigated during a domain security hardening review. 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. IPsec domain isolation requires compatible peer identity and negotiated connection security settings
  2. application and service identifiers combined with remote-address scopes reduce firewall rule blast radius
  3. exploit mitigations require evidence-based per-application compatibility decisions rather than disabling entire protections globally
  4. governance policies apply through resource scope and assignment inclusion rather than through Azure Arc registration alone

Explanation

Correct Answer

B:

Application and service identifiers combined with remote-address scopes reduce firewall rule blast radius. A firewall exception targets every executable. At a multi-branch Active Directory services team, administrators find that A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable.

Incorrect Answers

A:

“IPsec domain isolation requires compatible peer identity and negotiated connection security settings” does not explain the observed failure: at a multi-branch Active Directory services team, administrators find that A Windows Server print host accepts SMB management requests from unintended guest networks because a firewall exception targets every executable. A firewall exception targets every executable. Application and service identifiers combined with remote-address scopes reduce firewall rule blast radius.

C:

“Exploit mitigations require evidence-based per-application compatibility decisions rather than disabling entire protections globally” does not explain the observed failure: at a multi-branch Active Directory services team, administrators find that 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:

“Governance policies apply through resource scope and assignment inclusion rather than through Azure Arc registration alone” concerns a different part of the problem. At a multi-branch Active Directory services team, administrators find that 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 996

At a Windows Server monitoring and incident engineering team, administrators find that Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance. The case is being investigated during a production overnight fault investigation. The incident trace shows w32tm status and Kerberos logs show the PDC emulator skewed significantly from a trusted source. Which proposed action and matching validation would address the same root cause?

  1. repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role — verify: a targeted workload fix reduces sustained processor queue and service latency without hiding demand
  2. verify required dependency-map collection configuration and supported VM Insights agents and connectivity — verify: a controlled application TCP connection appears in the VM dependency view without excessive log collection
  3. restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity — verify: the domain time hierarchy converges and Kerberos operations succeed without manual clock changes
  4. repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role — verify: the domain time hierarchy converges and Kerberos operations succeed without manual clock changes

Explanation

Correct Answer

D:

Repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role. Verify that the domain time hierarchy converges and Kerberos operations succeed without manual clock changes. Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance; the original measurable clue was w32tm status and Kerberos logs show the PDC emulator skewed significantly from a trusted source.

Incorrect Answers

A:

A targeted workload fix reduces sustained processor queue and service latency without hiding demand. It would not verify that the domain time hierarchy converges and Kerberos operations succeed without manual clock changes. W32tm status and Kerberos logs show the PDC emulator skewed significantly from a trusted source.

B:

A controlled application TCP connection appears in the VM dependency view without excessive log collection. The required validation is different: the domain time hierarchy converges and Kerberos operations succeed without manual clock changes. Repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role.

C:

The domain time hierarchy converges and Kerberos operations succeed without manual clock changes. To correct the reported problem, repair the supported Windows Time hierarchy and reliable upstream time source on the correct domain role. Windows clients fail authentication to a domain controller because the PDC emulator time source drifted outside Kerberos tolerance; the original measurable clue was w32tm status and Kerberos logs show the PDC emulator skewed significantly from a trusted source.

Question 997

During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that A migration cutover assigns the destination the old server name before updating DNS and source NIC ownership, causing duplicate network identities. The solution must preserve other approved service dependencies. The incident trace shows DNS and network diagnostics show both old and new hosts answering the legacy file-server name. Which proposed action and matching validation would address the same root cause?

  1. stage bulk transfer, schedule a controlled delta synchronization and cut over after validating open-handle closure — verify: mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes
  2. use supported GPO migration tables and validate security filtering, WMI filters and link scope — verify: representative target computers process the intended GPO with translated principals and no unauthorized application
  3. perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification — verify: mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes
  4. perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification — verify: destination shares present expected files and effective SMB/NTFS permissions match the validated source inventory

Explanation

Correct Answer

C:

Perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification. Verify that 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.

Incorrect Answers

A:

Mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes. To correct the reported problem, perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification. Identity and client namespace transitions must be atomic enough to prevent split-brain file service during migration.

B:

Representative target computers process the intended GPO with translated principals and no unauthorized application. The required validation is different: mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes. Perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification.

D:

Destination shares present expected files and effective SMB/NTFS permissions match the validated source inventory. It would not verify that mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes. Mapped client shares resolve solely to the new server and the isolated old host cannot accept production writes.

Question 998

At a corporate datacenter-to-Azure transformation project, administrators find that An Azure Migrate test migration creates a VM on a production subnet and unintentionally accepts external traffic before owners validate the migrated system. 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. perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification
  2. enable supported dependency analysis and map observed application traffic before grouping migration waves
  3. assign a fenced test virtual network and validate security rules and authentication before test migration
  4. stage bulk transfer, schedule a controlled delta synchronization and cut over after validating open-handle closure

Explanation

Correct Answer

C:

Assign a fenced test virtual network and validate security rules and authentication before test migration. Migration rehearsal requires explicit network isolation and must not change source production availability. At a corporate datacenter-to-Azure transformation project, administrators find that An Azure Migrate test migration creates a VM on a production subnet and unintentionally accepts external traffic before owners validate the migrated system.

Incorrect Answers

A:

Perform the supported Storage Migration Service cutover sequence including identity transfer, source isolation and DNS verification. At a corporate datacenter-to-Azure transformation project, administrators find that An Azure Migrate test migration creates a VM on a production subnet and unintentionally accepts external traffic before owners validate the migrated system. Assign a fenced test virtual network and validate security rules and authentication before test migration.

B:

Enabling supported dependency analysis and map observed application traffic before grouping migration waves would not resolve the observed failure: at a corporate datacenter-to-Azure transformation project, administrators find that An Azure Migrate test migration creates a VM on a production subnet and unintentionally accepts external traffic before owners validate the migrated system. Assign a fenced test virtual network and validate security rules and authentication before test migration.

D:

Stage bulk transfer, schedule a controlled delta synchronization and cut over after validating open-handle closure. Migration rehearsal requires explicit network isolation and must not change source production availability. At a corporate datacenter-to-Azure transformation project, administrators find that An Azure Migrate test migration creates a VM on a production subnet and unintentionally accepts external traffic before owners validate the migrated system. Assign a fenced test virtual network and validate security rules and authentication before test migration.

Question 999

At a Windows Server 2025 workload fleet with Azure Arc, administrators find that Hybrid Windows Server domain controller security logs never appear in Microsoft Sentinel despite the workspace being active. The case is being investigated during a controlled security baseline change. The incident trace shows agent association and rule diagnostics show the controller is not associated with the required security event collection rule. Which proposed action and matching validation would address the same root cause?

  1. configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events — verify: a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table
  2. configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events — verify: a tested protected recovery workflow uses the new escrowed protector and old material is invalidated afterwards
  3. enable the appropriate Defender for Servers plan for the relevant subscriptions or connected machines and verify onboarding — verify: a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table
  4. inspect Group Policy inheritance and result sets, then consolidate security baseline scope with documented precedence — verify: Resultant Set of Policy matches the approved security baseline across representative servers and required administration still works

Explanation

Correct Answer

A:

Configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events. Verify that a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table. Security analytics coverage depends on rule association, data pipeline health and permitted events rather than workspace creation alone.

Incorrect Answers

B:

A tested protected recovery workflow uses the new escrowed protector and old material is invalidated afterwards. It would not verify that a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table. A safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table.

C:

A safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table. To correct the reported problem, configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events. Security analytics coverage depends on rule association, data pipeline health and permitted events rather than workspace creation alone.

D:

Resultant Set of Policy matches the approved security baseline across representative servers and required administration still works. The required validation is different: a safe test sign-in generates the intended Windows security event in the selected Sentinel Log Analytics table. Configure appropriate Azure Monitor Agent and supported data collection rules with destination workspace and required events.

Question 1000

At an on-premises data center support group, administrators find that Domain members intermittently fail Kerberos logon because a branch resolver lacks the domain controller SRV records used for discovery. The case is being investigated during a maintenance-window root-cause analysis. Which system engineering principle most directly explains why the remedy to restore AD-integrated DNS replication and correct client DNS resolver assignment for the domain namespace is appropriate?

  1. storage performance faults require measuring end-to-end I/O wait and workload contention rather than only resource utilization totals
  2. incident evidence preservation requires capacity planning and centralized retention, not only event generation
  3. Kerberos authentication depends on sufficiently synchronized time throughout the domain trust hierarchy
  4. Active Directory service discovery depends on healthy directory DNS records and properly scoped resolver selection

Explanation

Correct Answer

D:

Active Directory service discovery depends on healthy directory DNS records and properly scoped resolver selection. A branch resolver lacks the domain controller SRV records used for discovery, produces the distinctive clue dcdiag and nslookup _ldap. At an on-premises data center support group, administrators find that Domain members intermittently fail Kerberos logon because a branch resolver lacks the domain controller SRV records used for discovery.

Incorrect Answers

A:

A branch resolver lacks the domain controller SRV records used for discovery, produces the distinctive clue dcdiag and nslookup _ldap. At an on-premises data center support group, administrators find that Domain members intermittently fail Kerberos logon because a branch resolver lacks the domain controller SRV records used for discovery. The proposed action “Storage performance faults require measuring end-to-end I/O wait and workload contention rather than only resource utilization totals” would not resolve that situation. Active Directory service discovery depends on healthy directory DNS records and properly scoped resolver selection.

B:

The proposed step “Incident evidence preservation requires capacity planning and centralized retention, not only event generation” would leave the problem unresolved: at an on-premises data center support group, administrators find that Domain members intermittently fail Kerberos logon because a branch resolver lacks the domain controller SRV records used for discovery. Active Directory service discovery depends on healthy directory DNS records and properly scoped resolver selection.

C:

“Kerberos authentication depends on sufficiently synchronized time throughout the domain trust hierarchy” does not explain the observed failure: at an on-premises data center support group, administrators find that Domain members intermittently fail Kerberos logon because a branch resolver lacks the domain controller SRV records used for discovery. A branch resolver lacks the domain controller SRV records used for discovery, produces the distinctive clue dcdiag and nslookup _ldap. Active Directory service discovery depends on healthy directory DNS records and properly scoped resolver selection.

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