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

Question 690

At a Windows Hyper-V replication operations unit, administrators find 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 case is being investigated during an annual site outage simulation. Before implementing the proposed change (configure MABS protection group with application-aware backups and suitable local and Azure retention), which observed evidence most strongly substantiates the technical diagnosis?

  1. test run records show stale replica-derived VMs and network interfaces outside the protected production state
  2. replication metadata references one former cluster node and errors occur after a legitimate role move
  3. protection group membership shows only volume-level backup while database consistency checks remain absent
  4. vault protection overview lists no recent recovery point for the server despite agent installation

Explanation

Correct Answer

C:

Protection group membership shows only volume-level backup while database consistency checks remain absent. Workload-aware backup requires protection group inclusion and recoverable application-state checkpoints. At a Windows Hyper-V replication operations unit, administrators find that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its selected recovery policy excludes the database. An application-consistent database restore completes to a recovery environment within retention targets.

Incorrect Answers

A:

Testing run records show stale replica-derived VMs and network interfaces outside the protected production state addresses a separate aspect of the case. At a Windows Hyper-V replication operations unit, administrators find that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its selected recovery policy excludes the database. Protection group membership shows only volume-level backup while database consistency checks remain absent.

B:

“Replication metadata references one former cluster node and errors occur after a legitimate role move” does not explain the observed failure: at a Windows Hyper-V replication operations unit, administrators find that An on-premises SQL workload is added to a machine with Microsoft Azure Backup Server but its selected recovery policy excludes the database. Protection group membership shows only volume-level backup while database consistency checks remain absent.

D:

Workload-aware backup requires protection group inclusion and recoverable application-state checkpoints. At a Windows Hyper-V replication operations unit, administrators find 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 proposed action “Vault protection overview lists no recent recovery point for the server despite agent installation” would not resolve that situation. Protection group membership shows only volume-level backup while database consistency checks remain absent.

Question 691

At a Windows Server monitoring and incident engineering team, administrators find that A domain controller database becomes corrupt and normal boot cannot start directory services, requiring controlled authoritative recovery. The case is being investigated during a production overnight fault investigation. The administrators propose to use Directory Services Restore Mode with validated system state backups and choose the documented authoritative or nonauthoritative restore method. What measurable verification would demonstrate that the original failure has been corrected?

  1. the VM boots from intended disks and data volume mappings remain unchanged after a controlled restart
  2. an approved technician restores the encrypted server without exposing keys and subsequent reboots pass protector validation
  3. simulated audit records remain searchable for required retention while local log bounds and forwarding health stay monitored
  4. restored directory service starts and replication validation confirms the intended authoritative scope without duplicating objects

Explanation

Correct Answer

D:

Restored directory service starts and replication validation confirms the intended authoritative scope without duplicating objects. AD DS disaster recovery requires selecting restore authority and protecting directory database consistency. Boot failure events identify NTDS database inconsistency while network services remain unavailable.

Incorrect Answers

A:

“The VM boots from intended disks and data volume mappings remain unchanged after a controlled restart” does not explain the observed failure: boot failure events identify NTDS database inconsistency while network services remain unavailable. AD DS disaster recovery requires selecting restore authority and protecting directory database consistency. Restored directory service starts and replication validation confirms the intended authoritative scope without duplicating objects.

B:

“An approved technician restores the encrypted server without exposing keys and subsequent reboots pass protector validation” does not explain the observed failure: boot failure events identify NTDS database inconsistency while network services remain unavailable. AD DS disaster recovery requires selecting restore authority and protecting directory database consistency. Restored directory service starts and replication validation confirms the intended authoritative scope without duplicating objects.

C:

“Simulated audit records remain searchable for required retention while local log bounds and forwarding health stay monitored” does not demonstrate what is needed when boot failure events identify NTDS database inconsistency while network services remain unavailable. Restored directory service starts and replication validation confirms the intended authoritative scope without duplicating objects.

Question 692

During a change freeze and rollback planning meeting for a cross-domain infrastructure consolidation project, administrators confirm that An IIS application migrated into Azure App Service starts but fails outbound database access because connection strings and managed identity are not configured. The solution must preserve other approved service dependencies. Before implementing the proposed change (map application settings and database access to approved App Service configuration with secret custody and identity permissions), which observed evidence most strongly substantiates the technical diagnosis?

  1. dfsutil referrals show old target priorities or cached locations for affected clients
  2. dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group
  3. source DNS records and client caches still point to the decommissioned on-premises address
  4. App Service diagnostics show missing environment settings and rejected managed database authentication

Explanation

Correct Answer

D:

App Service diagnostics show missing environment settings and rejected managed database authentication. Connection strings and managed identity are not configured—could otherwise be mistaken for an unrelated infrastructure problem. An IIS application migrated into Azure App Service starts but fails outbound database access because connection strings and managed identity are not configured.

Incorrect Answers

A:

Connection strings and managed identity are not configured—could otherwise be mistaken for an unrelated infrastructure problem. The strongest of the offered choices. The proposed action “Dfsutil referrals show old target priorities or cached locations for affected clients” would not resolve that situation. App Service diagnostics show missing environment settings and rejected managed database authentication.

B:

The proposed step “Dependency view contains one source VM but a packet or process trace reveals remote database sessions outside the group” would leave the problem unresolved: the strongest of the offered choices. App Service diagnostics show missing environment settings and rejected managed database authentication.

C:

“Source DNS records and client caches still point to the decommissioned on-premises address” does not explain the observed failure: the strongest of the offered choices. Connection strings and managed identity are not configured—could otherwise be mistaken for an unrelated infrastructure problem. App Service diagnostics show missing environment settings and rejected managed database authentication.

Question 693

At a Windows Server monitoring and incident engineering team, administrators find that Azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. The case is being investigated during a production overnight fault investigation. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. verify required dependency-map collection configuration and supported VM Insights agents and connectivity
  2. collect and correlate Processor Queue Length with per-process CPU and disk counters under production-like load
  3. diagnose Arc agent service endpoints, proxy settings and role assignment before retrying extension deployment
  4. associate a valid DCR to the appropriate Arc machines with workspace output and selected event channel

Explanation

Correct Answer

D:

Associate a valid DCR to the appropriate Arc machines with workspace output and selected event channel. Agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion; adjacent fixes would not necessarily preserve the intended security or availability boundary. Administrators find that Azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources.

Incorrect Answers

A:

Verifying required dependency-map collection configuration and supported VM Insights agents and connectivity would not resolve the observed failure: administrators find that Azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. Associate a valid DCR to the appropriate Arc machines with workspace output and selected event channel.

B:

Collecting and correlate Processor Queue Length with per-process CPU and disk counters under production-like load is not a direct response to the evidence: administrators find that Azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. Associate a valid DCR to the appropriate Arc machines with workspace output and selected event channel.

C:

Agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion; adjacent fixes would not necessarily preserve the intended security or availability boundary. Administrators find that Azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. The proposed action “Diagnose Arc agent service endpoints, proxy settings and role assignment before retrying extension deployment” would not resolve that situation. Associate a valid DCR to the appropriate Arc machines with workspace output and selected event channel.

Question 694

During a replication and authentication health review for an Active Directory hybrid troubleshooting group, administrators confirm that Administrators accidentally delete a security group and recreate it with the same name, losing the former SID and nested membership information. The solution must preserve other approved service dependencies. The incident trace shows deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references. Which proposed action and matching validation would address the same root cause?

  1. restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity — verify: restored group retains its original SID and membership and access checks regain expected rights
  2. increase appropriately governed event-log capacity and forward selected records to protected centralized storage — verify: simulated audit records remain searchable for required retention while local log bounds and forwarding health stay monitored
  3. inspect sync rules, connector space and export errors, then correct the specific source attribute mapping — verify: restored group retains its original SID and membership and access checks regain expected rights
  4. restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity — verify: a targeted workload fix reduces sustained processor queue and service latency without hiding demand

Explanation

Correct Answer

A:

Restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity. Verify that restored group retains its original SID and membership and access checks regain expected rights. A correct repair plan pairs restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity with a direct test: restored group retains its original SID and membership and access checks regain expected rights. Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references.

Incorrect Answers

B:

Simulated audit records remain searchable for required retention while local log bounds and forwarding health stay monitored. The required validation is different: restored group retains its original SID and membership and access checks regain expected rights. Restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity.

C:

Restored group retains its original SID and membership and access checks regain expected rights. To correct the reported problem, restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity. A correct repair plan pairs restore the deleted AD object from Active Directory Recycle Bin if available rather than create a brand-new identity with a direct test: restored group retains its original SID and membership and access checks regain expected.

D:

A targeted workload fix reduces sustained processor queue and service latency without hiding demand. It would not verify that restored group retains its original SID and membership and access checks regain expected rights. Deleted-object metadata contains the group's old SID, while the recreated group has a different identity and broken ACL references.

Question 695

During a maintenance-window root-cause analysis for an on-premises data center support group, administrators confirm that Azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. The solution must preserve other approved service dependencies. Before implementing the proposed change (associate a valid DCR to the appropriate Arc machines with workspace output and selected event channel), which observed evidence most strongly substantiates the technical diagnosis?

  1. Azure Monitor data collection associations omit the resource even though AMA service runs
  2. disk free-space telemetry crosses an agreed threshold without any administrative alert event
  3. dfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding
  4. boot failure events identify NTDS database inconsistency while network services remain unavailable

Explanation

Correct Answer

A:

Azure Monitor data collection associations omit the resource even though AMA service runs. Agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion. Azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. A simulated matching event appears in the right workspace within the ingestion SLA and irrelevant events stay excluded.

Incorrect Answers

B:

“Disk free-space telemetry crosses an agreed threshold without any administrative alert event” does not explain the observed failure: azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. Agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion. Azure Monitor data collection associations omit the resource even though AMA service runs.

C:

“DfSR diagnostic backlog shows persistent SYSVOL staging divergence despite AD replication succeeding” does not explain the observed failure: azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. Agent installation and rule-to-resource association are distinct requirements for Azure Monitor ingestion. Azure Monitor data collection associations omit the resource even though AMA service runs.

D:

“Boot failure events identify NTDS database inconsistency while network services remain unavailable” does not demonstrate what is needed when azure Monitor Agent is installed on Arc-enabled Windows servers but their event logs never enter Log Analytics because a data collection rule targets the wrong resources. Azure Monitor data collection associations omit the resource even though AMA service runs.

Question 696

At a two-site datacenter high-availability team, administrators find that A geographically stretched cluster repeatedly pauses storage writes when the intersite link exceeds the supported replication latency threshold. The case is being investigated during a planned primary-site outage exercise. The administrators propose to verify supported storage-replica topology, link requirements, witness placement and planned recovery behavior. What measurable verification would demonstrate that the original failure has been corrected?

  1. a production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients
  2. all nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers
  3. failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior
  4. client connection tests succeed through the load balancer before and after role failover

Explanation

Correct Answer

C:

Failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior. Synchronous multi-site failover depends on storage replication latency and independent quorum design. Replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts.

Incorrect Answers

A:

“A production-equivalent load test preserves node heartbeats and storage throughput without isolating approved clients” concerns a different part of the problem. Replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts. Failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior.

B:

Synchronous multi-site failover depends on storage replication latency and independent quorum design. Replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts. The proposed action “All nodes pass the required validation checks and a fault-injection rehearsal does not evict healthy peers” would not resolve that situation. Failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior.

D:

“Client connection tests succeed through the load balancer before and after role failover” does not explain the observed failure: replication metrics show sustained latency and disconnected synchronous replication during site traffic bursts. Synchronous multi-site failover depends on storage replication latency and independent quorum design. Failover rehearsal meets the stated recovery objectives with data consistency and a documented link-loss behavior.

Question 697

During a domain security hardening review for a multi-branch Active Directory services team, administrators confirm that A domain-joined server starts applying a public Windows Defender Firewall profile after DNS and domain-controller reachability change during failover. The solution must preserve other approved service dependencies. What targeted corrective change best addresses this Windows Server or Azure failure while preserving the stated operations constraints?

  1. configure a valid conditional forwarder or Azure DNS Private Resolver path for the private zone
  2. assess supported per-program Exploit Protection settings in audit and a change window before selectively enforcing validated mitigations
  3. repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall
  4. associate the Arc resource to the correct subscription, resource group and policy assignment scopes, then verify evaluation

Explanation

Correct Answer

C:

Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall. Windows firewall profile selection depends on network identification and must not be bypassed by blanket permit rules; adjacent fixes would not necessarily preserve the intended security or availability boundary. A domain-joined server starts applying a public Windows Defender Firewall profile after DNS and domain-controller reachability change during failover.

Incorrect Answers

A:

Configure a valid conditional forwarder or Azure DNS Private Resolver path for the private zone. A domain-joined server starts applying a public Windows Defender Firewall profile after DNS and domain-controller reachability change during failover. Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall.

B:

Assessing supported per-program Exploit Protection settings in audit and a change window before selectively enforcing validated mitigations would not resolve the observed failure: a domain-joined server starts applying a public Windows Defender Firewall profile after DNS and domain-controller reachability change during failover. Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall.

D:

Associate the Arc resource to the correct subscription, resource group and policy assignment scopes, then verify evaluation. Windows firewall profile selection depends on network identification and must not be bypassed by blanket permit rules; adjacent fixes would not necessarily preserve the intended security or availability boundary. A domain-joined server starts applying a public Windows Defender Firewall profile after DNS and domain-controller reachability change during failover. Repair domain network identification dependencies and enforce correctly scoped firewall profile rules without disabling the firewall.

Question 698

During a privileged-access audit for a regulated Windows Server hybrid identity environment, administrators confirm that A newly onboarded branch server is visible in Azure Arc but receives no inherited update or security governance policy. The solution must preserve other approved service dependencies. Before implementing the proposed change (associate the Arc resource to the correct subscription, resource group and policy assignment scopes, then verify evaluation), which observed evidence most strongly substantiates the technical diagnosis?

  1. agent health reports no password-filter enforcement on domain controllers despite cloud policy activation
  2. resource metadata shows successful Arc connection but the baseline assignment excludes the machine's actual resource group
  3. password inspection finds identical unmanaged local administrator credentials on unrelated member servers
  4. nslookup and DNS server query traces show private-zone requests sent toward internet resolvers and return public or negative answers

Explanation

Correct Answer

B:

Resource metadata shows successful Arc connection but the baseline assignment excludes the machine's actual resource group. The solution must preserve other approved service dependencies.

Incorrect Answers

A:

Agent health reports no password-filter enforcement on domain controllers despite cloud policy activation. Resource metadata shows successful Arc connection but the baseline assignment excludes the machine's actual resource group because the solution must preserve other approved service dependencies.

C:

Password inspection finds identical unmanaged local administrator credentials on unrelated member servers. Resource metadata shows successful Arc connection but the baseline assignment excludes the machine's actual resource group.

D:

“Nslookup and DNS server query traces show private-zone requests sent toward internet resolvers and return public or negative answers” does not explain the observed failure: the strongest of the offered choices. Resource metadata shows successful Arc connection but the baseline assignment excludes the machine's actual resource group.

Question 699

At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. The case is being investigated during a staged source-to-target cutover. Which system engineering principle most directly explains why the remedy to inventory and replace incompatible drivers, migrate queues and permissions with supported print tools is appropriate?

  1. cross-forest user moves must reconcile legacy access control identifiers as well as account objects
  2. server migrations should be sequenced by real service dependencies rather than arbitrary VM names
  3. Active Directory functional-level advancement is gated by every participating domain controller and cannot be safely treated as cosmetic
  4. print migration must address server driver architecture, queue metadata and client access

Explanation

Correct Answer

D:

Print migration must address server driver architecture, queue metadata and client access. At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host.

Incorrect Answers

A:

At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. The proposed action “Cross-forest user moves must reconcile legacy access control identifiers as well as account objects” would not resolve that situation. Print migration must address server driver architecture, queue metadata and client access.

B:

The proposed step “Server migrations should be sequenced by real service dependencies rather than arbitrary VM names” would leave the problem unresolved: at a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. Print migration must address server driver architecture, queue metadata and client access.

C:

Active Directory functional-level advancement is gated by every participating domain controller and cannot be safely treated as cosmetic. At a Windows Server modernization migration team, administrators find that Printers are migrated to Windows Server 2025 but legacy kernel-mode drivers prevent queues from opening on the replacement host. Print migration must address server driver architecture, queue metadata and client access.

Question 700

During a quarterly recovery rehearsal for an enterprise Windows Server disaster recovery program, administrators confirm that An Azure-connected Windows Server is configured for daily backup but the relevant Recovery Services vault policy has no active protection association. The solution must preserve other approved service dependencies. The incident trace shows vault protection overview lists no recent recovery point for the server despite agent installation. Which proposed action and matching validation would address the same root cause?

  1. review Azure-to-Azure Site Recovery replication policy, recovery region and cache storage settings — verify: sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region
  2. enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule — verify: test recovery resources are removed while protected replication health and genuine production VM state remain intact
  3. enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule — verify: a backup job completes and a controlled file recovery reads the correct point-in-time data
  4. perform supported planned failover, commit and reverse replication after checking source and target state — verify: a backup job completes and a controlled file recovery reads the correct point-in-time data

Explanation

Correct Answer

C:

Enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule. Verify that a backup job completes and a controlled file recovery reads the correct point-in-time data. In the relevant Windows Server or hybrid-cloud layer, installing backup software does not create recoverable data until vault registration and policy association are effective. Vault protection overview lists no recent recovery point for the server despite agent installation.

Incorrect Answers

A:

Sustained healthy replication meets the recovery-point objective and a test failover reaches the authorized region. The required validation is different: a backup job completes and a controlled file recovery reads the correct point-in-time data. Enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule.

B:

Test recovery resources are removed while protected replication health and genuine production VM state remain intact. It would not verify that a backup job completes and a controlled file recovery reads the correct point-in-time data. Vault protection overview lists no recent recovery point for the server despite agent installation.

D:

A backup job completes and a controlled file recovery reads the correct point-in-time data. To correct the reported problem, enroll the supported protected workload with the vault, recovery services agent or provider path and confirm policy schedule. In the relevant Windows Server or hybrid-cloud layer, installing backup software does not create recoverable data until vault registration and policy association are effective.

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