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

Question 60

During a load-balanced access and cluster-node test for an Azure-hosted clustered application service, administrators confirm that Monthly patching reboots both active cluster nodes simultaneously and interrupts a clustered file service. The solution must preserve other approved service dependencies. The administrators propose to configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks. What measurable verification would demonstrate that the original failure has been corrected?

  1. failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior
  2. a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients
  3. a full patch rehearsal updates each node with role continuity and documented pause or resume events
  4. client connection tests succeed through the load balancer before and after role failover

Explanation

Correct Answer

C:

A full patch rehearsal updates each node with role continuity and documented pause or resume events. Cluster-aware maintenance sequences capacity and ownership changes so one planned restart does not become a service outage. Maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes.

Incorrect Answers

A:

Failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior. Maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes. A full patch rehearsal updates each node with role continuity and documented pause or resume events.

B:

“A production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients” does not explain the observed failure: maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes. A full patch rehearsal updates each node with role continuity and documented pause or resume events.

D:

Client connection tests succeed through the load balancer before and after role failover. Cluster-aware maintenance sequences capacity and ownership changes so one planned restart does not become a service outage. Maintenance automation timestamps show concurrent reboot triggers while critical roles still owned by those nodes. A full patch rehearsal updates each node with role continuity and documented pause or resume events.

Question 61

During a critical-service alert and telemetry test for an Azure Arc and Windows Server fleet operations team, administrators confirm that A domain controller reconnected after a long outage produces replication divergence because its directory database contains lingering objects. The solution must preserve other approved service dependencies. The incident trace shows repadmin reports lingering objects or stale partition failures on the isolated domain controller. Which proposed action and matching validation would address the same root cause?

  1. assess replication tombstone lifetime and perform supported lingering-object remediation before restoring normal replication — verify: the domain time hierarchy converges and Kerberos operations succeed without manual clock changes
  2. assess replication tombstone lifetime and perform supported lingering-object remediation before restoring normal replication — verify: directory partitions replicate cleanly and users have consistent AD object state across healthy controllers
  3. diagnose Arc agent service endpoints, proxy settings and role assignment before retrying extension deployment — verify: directory partitions replicate cleanly and users have consistent AD object state across healthy controllers
  4. collect and correlate Processor Queue Length with per-process CPU and disk counters under production-like load — verify: a targeted workload fix reduces sustained processor queue and service latency without hiding demand

Explanation

Correct Answer

B:

Assess replication tombstone lifetime and perform supported lingering-object remediation before restoring normal replication. Verify that directory partitions replicate cleanly and users have consistent AD object state across healthy controllers. Directory replication recovery must respect deletion lifetime and prevent obsolete objects reentering the forest.

Incorrect Answers

A:

The domain time hierarchy converges and Kerberos operations succeed without manual clock changes. It would not verify that directory partitions replicate cleanly and users have consistent AD object state across healthy controllers. Directory partitions replicate cleanly and users have consistent AD object state across healthy controllers.

C:

Directory partitions replicate cleanly and users have consistent AD object state across healthy controllers. To correct the reported problem, assess replication tombstone lifetime and perform supported lingering-object remediation before restoring normal replication. Directory replication recovery must respect deletion lifetime and prevent obsolete objects reentering the forest.

D:

A targeted workload fix reduces sustained processor queue and service latency without hiding demand. The required validation is different: directory partitions replicate cleanly and users have consistent AD object state across healthy controllers. Assess replication tombstone lifetime and perform supported lingering-object remediation before restoring normal replication.

Question 62

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. The administrators propose to configure supported workgroup cluster local identities, certificates and name resolution consistently on every node. What measurable verification would demonstrate that the original failure has been corrected?

  1. controlled failover mounts the correct disk on the new owner while another node cannot write concurrently
  2. a test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights
  3. the workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities
  4. all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers

Explanation

Correct Answer

C:

The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities. Each server has conflicting local identities and no appropriate trust configuration; the pre-change evidence is cluster creation logs show name or authentication errors on one peer that is not domain joined.

Incorrect Answers

A:

Controlled failover mounts the correct disk on the new owner while another node cannot write concurrently. Each server has conflicting local identities and no appropriate trust configuration; the pre-change evidence is cluster creation logs show name or authentication errors on one peer that is not domain joined. Cluster creation logs show name or authentication errors on one peer that is not domain joined. The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities.

B:

A test clustered client access name comes online with proper Kerberos resolution and no excessive domain rights. Cluster creation logs show name or authentication errors on one peer that is not domain joined. The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities.

D:

All nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers. Cluster creation logs show name or authentication errors on one peer that is not domain joined. The workgroup nodes form a supported cluster and quorum/failover tests work using documented administrative identities.

Question 63

At an enterprise IIS, storage and AD platform upgrade program, administrators find that A forest administrator raises the functional level while an unsupported legacy domain controller still exists in a branch. The case is being investigated during a production compatibility validation cycle. Which system engineering principle most directly explains why the remedy to inventory domain controllers, operating systems and replication health before a functional-level change is appropriate?

  1. migration planning depends on sufficiently privileged discovery access and truthful inventory coverage
  2. migration rehearsal requires explicit network isolation and must not change source production availability
  3. identity and client namespace transitions must be atomic enough to prevent split-brain file service during migration
  4. Active Directory functional-level advancement is gated by every participating domain controller and cannot be safely treated as cosmetic

Explanation

Correct Answer

D:

Active Directory functional-level advancement is gated by every participating domain controller and cannot be safely treated as cosmetic. At an enterprise IIS, storage and AD platform upgrade program, administrators find that A forest administrator raises the functional level while an unsupported legacy domain controller still exists in a branch.

Incorrect Answers

A:

“Migration planning depends on sufficiently privileged discovery access and truthful inventory coverage” does not explain the observed failure: at an enterprise IIS, storage and AD platform upgrade program, administrators find that A forest administrator raises the functional level while an unsupported legacy domain controller still exists in a branch. Active Directory functional-level advancement is gated by every participating domain controller and cannot be safely treated as cosmetic.

B:

“Migration rehearsal requires explicit network isolation and must not change source production availability” concerns a different part of the problem. At an enterprise IIS, storage and AD platform upgrade program, administrators find that A forest administrator raises the functional level while an unsupported legacy domain controller still exists in a branch. Active Directory functional-level advancement is gated by every participating domain controller and cannot be safely treated as cosmetic.

C:

At an enterprise IIS, storage and AD platform upgrade program, administrators find that A forest administrator raises the functional level while an unsupported legacy domain controller still exists in a branch. The proposed action “Identity and client namespace transitions must be atomic enough to prevent split-brain file service during migration” would not resolve that situation. Active Directory functional-level advancement is gated by every participating domain controller and cannot be safely treated as cosmetic.

Question 64

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

  1. follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood
  2. repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection
  3. verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior
  4. configure the supported Azure load balancer front end, health probe and cluster IP resource integration

Explanation

Correct Answer

A:

Follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood. A review is complete only when node-by-node upgrade and role failover succeed while the rollback strategy remains valid until final functional-level change. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation.

Incorrect Answers

B:

Repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood.

C:

Verifying supported storage-replica topology, link requirements, witness placement and planned recovery behavior would not resolve the observed failure: operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood.

D:

Configure the supported Azure load balancer front end, health probe and cluster IP resource integration. Addresses another workflow. Operators upgrade all nodes to a new Windows Server release before checking whether clustered roles support mixed-version operation. Follow the supported cluster OS rolling upgrade order and delay functional-level update until rollback limits are understood.

Question 65

During a migration wave readiness review for a corporate datacenter-to-Azure transformation project, administrators confirm that A Windows IIS site is selected for Azure App Service despite dependencies on local COM components and registry-based machine settings. The solution must preserve other approved service dependencies. The incident trace shows assessment discovers native modules and local machine dependencies unsupported by the proposed App Service hosting plan. Which proposed action and matching validation would address the same root cause?

  1. perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target — verify: an isolated test copy boots and passes checks without exposing public services or altering source workloads
  2. stage bulk transfer, schedule a controlled delta synchronization and cut over after validating open-handle closure — verify: source and destination inventories, hashes and permissions reconcile after final read-only cutover
  3. update namespace target referrals and validate DFS client cache expiration and namespace health — verify: chosen hosting platform passes representative web requests and validated dependency substitutions
  4. perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target — verify: chosen hosting platform passes representative web requests and validated dependency substitutions

Explanation

Correct Answer

D:

Perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target. Verify that chosen hosting platform passes representative web requests and validated dependency substitutions. Migrating a web server to a managed platform requires application compatibility assessment, not a direct VM image conversion.

Incorrect Answers

A:

An isolated test copy boots and passes checks without exposing public services or altering source workloads. It would not verify that chosen hosting platform passes representative web requests and validated dependency substitutions. Chosen hosting platform passes representative web requests and validated dependency substitutions.

B:

Source and destination inventories, hashes and permissions reconcile after final read-only cutover. The required validation is different: chosen hosting platform passes representative web requests and validated dependency substitutions. Perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target.

C:

Chosen hosting platform passes representative web requests and validated dependency substitutions. To correct the reported problem, perform supported Azure Migrate web-app assessment to identify incompatible hosting dependencies before choosing a target. Migrating a web server to a managed platform requires application compatibility assessment, not a direct VM image conversion.

Question 66

At a two-site datacenter high-availability team, administrators find that A cluster health dashboard shows green while individual nodes report failed storage jobs that the central dashboard is not collecting. The case is being investigated during a planned primary-site outage exercise. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests
  2. configure Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks
  3. repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection
  4. reevaluate dynamic quorum and witness placement, then configure supported cloud witness for balanced recovery behavior

Explanation

Correct Answer

C:

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. A controlled warning appears at both the affected node and consolidated cluster view before remediation.

Incorrect Answers

A:

“Rerun supported cluster validation, inspect system driver compatibility and reconcile failed network tests” concerns a different part of the problem. 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.

B:

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. Configuring Cluster-Aware Updating to drain and patch one validated node at a time with sequencing checks alone cannot establish that the failure is corrected. Repair Windows Admin Center cluster connectivity and verify node-specific event and performance collection.

D:

“Reevaluate dynamic quorum and witness placement, then configure supported cloud witness for balanced recovery behavior” does not explain 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 67

During a critical-service alert and telemetry test for an Azure Arc and Windows Server fleet operations team, administrators confirm that A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. The solution must preserve other approved service dependencies. The administrators propose to inspect sync rules, connector space and export errors, then correct the specific source attribute mapping. What measurable verification would demonstrate that the original failure has been corrected?

  1. a controlled application TCP connection appears in the VM dependency view without excessive log collection
  2. the account synchronizes with the intended immutable identity and sign-in succeeds without creating a duplicate cloud user
  3. a simulated matching event appears in the right workspace within the ingestion SLA and irrelevant events stay excluded
  4. SYSVOL content converges and a new GPO script executes consistently from all eligible domain controllers

Explanation

Correct Answer

B:

The account synchronizes with the intended immutable identity and sign-in succeeds without creating a duplicate cloud user. Entra Connect sync excludes a required UPN or source-anchor attribute, which was identified by synchronization service errors show a UPN conflict or unexpected source anchor on the affected account. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute.

Incorrect Answers

A:

A controlled application TCP connection appears in the VM dependency view without excessive log collection. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. The account synchronizes with the intended immutable identity and sign-in succeeds without creating a duplicate cloud user.

C:

A simulated matching event appears in the right workspace within the ingestion SLA and irrelevant events stay excluded. Addresses another workflow. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. The account synchronizes with the intended immutable identity and sign-in succeeds without creating a duplicate cloud user.

D:

SYSVOL content converges and a new GPO script executes consistently from all eligible domain controllers. Entra Connect sync excludes a required UPN or source-anchor attribute, which was identified by synchronization service errors show a UPN conflict or unexpected source anchor on the affected account. A hybrid user can authenticate to on-premises AD but cloud sign-in fails because Entra Connect sync excludes a required UPN or source-anchor attribute. The account synchronizes with the intended immutable identity and sign-in succeeds without creating a duplicate cloud user.

Question 68

During a migration wave readiness review for a corporate datacenter-to-Azure transformation project, administrators confirm that A Storage Migration Service job discovers the source file volumes but does not inventory local shares and security descriptors before migration. 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. assign a fenced test virtual network and validate security rules and authentication before test migration
  2. rerun supported storage inventory for files, shares and security before transferring data to the destination
  3. configure the supported physical-server migration and replication appliance path with correct mobility service and credentials
  4. plan cross-forest identity migration with authorized SID history or ACL translation under audited trust controls

Explanation

Correct Answer

B:

Rerun supported storage inventory for files, shares and security before transferring data to the destination. Compare the proposed remedy with the actual symptoms: A Storage Migration Service job discovers the source file volumes but does not inventory local shares and security descriptors before migration.

Incorrect Answers

A:

Assign a fenced test virtual network and validate security rules and authentication before test migration. A Storage Migration Service job discovers the source file volumes but does not inventory local shares and security descriptors before migration. Rerun supported storage inventory for files, shares and security before transferring data to the destination because compare the proposed remedy with the actual symptoms: A Storage Migration Service job discovers the source file volumes but does not inventory local shares and security descriptors before migration.

C:

Configure the supported physical-server migration and replication appliance path with correct mobility service and credentials. A Storage Migration Service job discovers the source file volumes but does not inventory local shares and security descriptors before migration. Rerun supported storage inventory for files, shares and security before transferring data to the destination.

D:

“Plan cross-forest identity migration with authorized SID history or ACL translation under audited trust controls” does not explain the observed failure: a Storage Migration Service job discovers the source file volumes but does not inventory local shares and security descriptors before migration. Rerun supported storage inventory for files, shares and security before transferring data to the destination.

Question 69

At a corporate Azure-hosted Windows Server operations unit, administrators find that Two managed application tiers configured for Windows domain isolation cannot establish secure communication after a new GPO is rolled out. The case is being investigated during a monthly compliance verification. Which system engineering principle most directly explains why the remedy to reconcile connection security rules and certificate or Kerberos authentication prerequisites on both endpoints is appropriate?

  1. IPsec domain isolation requires compatible peer identity and negotiated connection security settings
  2. hybrid password protection requires working on-premises agent paths to extend cloud policy to Active Directory Domain Services
  3. recovery credential rotation must preserve a tested working recovery path throughout the transition
  4. NTLM elimination should be evidence-led because untested protocol removal can interrupt dependent applications

Explanation

Correct Answer

A:

IPsec domain isolation requires compatible peer identity and negotiated connection security settings. At a corporate Azure-hosted Windows Server operations unit, administrators find that Two managed application tiers configured for Windows domain isolation cannot establish secure communication after a new GPO is rolled out.

Incorrect Answers

B:

The proposed step “Hybrid password protection requires working on-premises agent paths to extend cloud policy to Active Directory Domain Services” would leave the problem unresolved: at a corporate Azure-hosted Windows Server operations unit, administrators find that Two managed application tiers configured for Windows domain isolation cannot establish secure communication after a new GPO is rolled out. IPsec domain isolation requires compatible peer identity and negotiated connection security settings.

C:

“Recovery credential rotation must preserve a tested working recovery path throughout the transition” does not explain the observed failure: at a corporate Azure-hosted Windows Server operations unit, administrators find that Two managed application tiers configured for Windows domain isolation cannot establish secure communication after a new GPO is rolled out. IPsec domain isolation requires compatible peer identity and negotiated connection security settings.

D:

“NTLM elimination should be evidence-led because untested protocol removal can interrupt dependent applications” does not explain the observed failure: at a corporate Azure-hosted Windows Server operations unit, administrators find that Two managed application tiers configured for Windows domain isolation cannot establish secure communication after a new GPO is rolled out. IPsec domain isolation requires compatible peer identity and negotiated connection security settings.

Question 70

During a disaster-tolerant production failover rehearsal for a hybrid infrastructure availability team, administrators confirm that A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. The solution must preserve other approved service dependencies. Before implementing the proposed change (configure supported workgroup cluster local identities, certificates and name resolution consistently on every node), which observed evidence most strongly substantiates the technical diagnosis?

  1. Storage Jobs report incomplete slab repair with a shortage of valid fault-domain capacity
  2. failover role reports online locally but Azure clients cannot reach the floating service address
  3. cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement
  4. cluster creation logs show name or authentication errors on one peer that is not domain joined

Explanation

Correct Answer

D:

Cluster creation logs show name or authentication errors on one peer that is not domain joined. Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership. 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:

“Storage Jobs report incomplete slab repair with a shortage of valid fault-domain capacity” does not explain the observed failure: a workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. Cluster creation logs show name or authentication errors on one peer that is not domain joined.

B:

“Failover role reports online locally but Azure clients cannot reach the floating service address” concerns a different part of the problem. A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. Cluster creation logs show name or authentication errors on one peer that is not domain joined.

C:

Workgroup clusters still require consistent identity, certificate and name-resolution prerequisites despite lacking AD domain membership. A workgroup-based Windows failover cluster fails to authenticate nodes because each server has conflicting local identities and no appropriate trust configuration. The proposed action “Cluster validation reports SCSI-3 reservation failures and redirected disk access during role movement” would not resolve that situation. Cluster creation logs show name or authentication errors on one peer that is not domain joined.

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