Try 10 focused Microsoft AZ-802 questions on Implement Disaster Recovery, with explanations, then continue with IT Mastery.
Open the matching IT Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.
Try Microsoft AZ-802 on Web View full Microsoft AZ-802 practice page
| Field | Detail |
|---|---|
| Exam route | Microsoft AZ-802 |
| Topic area | Implement Disaster Recovery |
| Blueprint weight | 6.5% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Implement Disaster Recovery for Microsoft AZ-802. Work through the 10 questions first, then review the explanations and return to mixed practice in IT Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 6.5% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original IT Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Implement Disaster Recovery
A company runs a domain-joined Windows Server VM in Azure that hosts an internal line-of-business application. The recovery requirement is to restore the entire VM or its disks to a previous recovery point after corruption. Administrators want the simplest Azure-native design and do not need application-specific or file-only backup. Which design best fits the requirement?
Options:
A. Enable Azure VM backup in a Recovery Services vault
B. Configure Azure Site Recovery replication
C. Install the MARS agent inside the VM
D. Deploy Azure Backup Server for the VM
Best answer: A
Explanation: For VM-level recovery of an Azure IaaS VM, the best fit is Azure VM backup from a Recovery Services vault. This protection uses the Azure VM agent and backup extension to create recovery points for the VM and its managed disks without requiring administrators to manage a separate in-guest backup product. It supports restoring the full VM, individual disks, or files from a recovery point, depending on the restore scenario. The MARS agent is better suited to file, folder, and system-state backup from within a server, while Azure Site Recovery is for disaster recovery replication and failover rather than backup retention and restore points.
Topic: Implement Disaster Recovery
A Windows Server Azure VM named FS01 is protected by Azure Backup in a Recovery Services vault. The backup job from 02:00 is listed as application-consistent. You must recover only D:\Shares\Finance from that recovery point, keep FS01 online, and avoid replacing any VM disks. Which restore method should you use?
Options:
A. Restore the OS and data disks, then swap them into FS01.
B. Initiate an Azure Site Recovery failover for FS01.
C. Use File Recovery and copy the folder with ACLs preserved.
D. Restore the VM to a new Azure VM.
Best answer: C
Explanation: Azure Backup File Recovery is the appropriate restore method when the goal is to recover individual files or folders from an Azure VM backup. It uses the selected recovery point to mount the backed-up volumes through a downloadable script, allowing an administrator to copy only the required content. Because the existing VM and its disks are not replaced, FS01 can remain online. To preserve NTFS permissions and metadata, use a copy method such as robocopy with ACL-preserving options after the recovery volume is mounted. Full VM restore or disk restore is intended for larger recovery scenarios and would not meet the requirement to avoid replacing disks.
Topic: Implement Disaster Recovery
A company protects a three-tier Windows Server application with Azure Site Recovery. The administrator must validate the recovery design this weekend without interrupting production and must confirm that the application starts in the correct order and can use the intended Azure network.
| Evidence | Current state |
|---|---|
| Replication health | Healthy for all VMs |
| Recovery plan | DC group, then SQL group, then Web group |
| Network mapping | Prod-VLAN to DR-VNet/AppSubnet |
| Latest recovery point | App-consistent, 12 minutes old |
Which design is the best fit?
Options:
A. Run a planned failover of each VM to DR-VNet/AppSubnet.
B. Disable network mapping and fail over the recovery plan.
C. Run a test failover of the recovery plan to an isolated test network.
D. Run an unplanned failover of the web VM first.
Best answer: C
Explanation: Azure Site Recovery test failover is the right validation method when production must continue running. The evidence shows replication is healthy, a recent app-consistent recovery point exists, the recovery plan defines the required startup order, and network mapping identifies the intended Azure network. Running the recovery plan as a test failover lets the administrator validate boot order, application behavior, and Azure-side connectivity without committing the production workload to Azure. The test should use an isolated or non-conflicting test network when needed, then be cleaned up after validation. A planned or unplanned failover is for an actual recovery or migration event, not a no-impact validation.
Topic: Implement Disaster Recovery
A company replicates three on-premises Windows Server VMs to Azure by using Azure Site Recovery. The web, app, and database VMs are on separate on-premises VLANs. After an unplanned failover, the VMs must retain tier isolation and immediately use Azure-based DNS and a site-to-site VPN route to reach domain controllers. Which network design is the best fit?
Options:
A. Fail over the VMs first, then manually attach each NIC to a subnet
B. Map each source network to the matching Azure subnet in a prepared VNet
C. Use Microsoft Entra Domain Services instead of ASR network mapping
D. Map all source networks to one recovery subnet and separate tiers later
Best answer: B
Explanation: Azure Site Recovery network mapping defines where protected machines connect after failover. For Azure recovery, the target VNet should already include the required subnets, DNS settings, routing to the VPN gateway or hub network, and NSGs that match the recovery design. Mapping each source network to the corresponding Azure recovery network or subnet lets the web, app, and database VMs come online with the expected isolation and connectivity instead of depending on manual post-failover changes. Per-VM network settings can further refine subnet and IP behavior when needed.
The key design point is to prepare and map recovery networking before a failover event.
Topic: Implement Disaster Recovery
A company runs several on-premises Windows Server hosts that contain Hyper-V VMs and SQL Server databases. Administrators need centralized backup management, application-aware recovery points, short-term retention on local disk, and long-term offsite retention in Azure. Which configuration should you implement?
Options:
A. Enable Azure VM backup for each workload
B. Deploy Azure Backup Server and register it with a Recovery Services vault
C. Install the MARS agent on each protected server
D. Configure Azure Site Recovery replication for the workloads
Best answer: B
Explanation: Microsoft Azure Backup Server is the right fit when supported on-premises workloads need centralized backup management plus both local and Azure-based retention. It can protect workloads such as Hyper-V VMs and SQL Server databases, store short-term recovery points on locally attached disk, and send longer-term recovery points to a Recovery Services vault. This matches the requirement for application-aware backups and centralized administration without requiring the workloads to be Azure VMs. The key distinction is that Azure Backup Server is a backup product for workload recovery points; it is not a per-server file backup agent and not a disaster-recovery replication service.
Topic: Implement Disaster Recovery
A company protects an on-premises three-tier Windows Server application by using Azure Site Recovery. During a regional outage, the domain controller and DNS server must be available before SQL Server starts, SQL Server must be validated before the application servers start, and the web servers must start last. Administrators also need a documented pause for an application owner to confirm database health. Which design best fits these requirements?
Options:
A. Place the Azure VMs in separate availability zones
B. Create an ASR recovery plan with ordered groups and a manual action
C. Restore the servers from Azure Backup in dependency order
D. Use one replication policy with crash-consistent recovery points
Best answer: B
Explanation: Azure Site Recovery recovery plans are designed for controlled failover of multi-VM applications. A recovery plan can group protected machines and run those groups in order, so infrastructure services such as AD DS and DNS can come online before database, application, and web tiers. The plan can also include manual actions to pause execution until an operator validates a dependency, such as SQL Server health, before continuing. This gives administrators an orchestrated runbook for failover rather than a collection of independent VM failovers. Replication policies protect data, but they do not provide application-tier sequencing or approval checkpoints.
Topic: Implement Disaster Recovery
A company runs a line-of-business VM on an on-premises Hyper-V host. The DR requirement is to fail over the VM to another on-premises Hyper-V host in a secondary datacenter, avoid using Azure as the recovery target, tolerate a few minutes of data loss, and validate failover without interrupting production. Which recovery mechanism should you configure?
Options:
A. Configure Hyper-V Replica with test failover
B. Configure Windows Server Backup bare-metal recovery
C. Configure Azure Backup for the VM
D. Configure Azure Site Recovery to Azure
Best answer: A
Explanation: Hyper-V Replica is the right fit when the goal is VM-level disaster recovery between Hyper-V hosts without using Azure as the recovery target. It asynchronously replicates VM changes to a replica server and supports planned, unplanned, and test failover. A test failover creates an isolated test VM so administrators can validate recovery without stopping or redirecting the production VM. Backup mechanisms are designed primarily for restore from recovery points, not rapid failover to a running replica. Azure Site Recovery can orchestrate replication and failover, including to Azure, but using Azure as the target conflicts with the stated requirement.
Topic: Implement Disaster Recovery
A company runs a line-of-business Windows Server VM on an on-premises Hyper-V host. The recovery design must keep a near-current copy at a second on-premises datacenter, allow a non-disruptive recovery validation test, and avoid running the workload in Azure because of data residency requirements. Which recovery mechanism is the best design fit?
Options:
A. Use Azure Backup to restore the VM after an outage
B. Configure Hyper-V Replica to the second datacenter
C. Export the VM nightly and import it during recovery
D. Configure Azure Site Recovery to fail over the VM to Azure
Best answer: B
Explanation: Hyper-V Replica is the best fit when the requirement is VM-level disaster recovery from one Hyper-V host or site to another Hyper-V host or site. It maintains a replica VM, supports planned and unplanned failover, and includes test failover for recovery validation without affecting the running production VM. Azure Site Recovery is appropriate when you need Azure-based orchestration or Azure as the recovery target, but the scenario explicitly avoids running the workload in Azure. Azure Backup is for point-in-time recovery and retention, not near-current site failover.
Topic: Implement Disaster Recovery
Your organization uses Azure Site Recovery to protect Windows Server Azure VMs from East US to West US. The source VMs are in vnet-prod-east on web and app subnets. The DR region already has vnet-dr-west with matching subnets and peering to a hub VNet that hosts domain controllers and shared services. After failover, the VMs must keep their tier separation and reach the DR hub without manual NIC reconfiguration. Which ASR network configuration should you use?
Options:
A. Map vnet-prod-east directly to the DR hub VNet.
B. Assign public IP addresses to the failed-over VM NICs.
C. Map vnet-prod-east to vnet-dr-west and set each VM NIC to its matching DR subnet.
D. Create only VNet peering between vnet-prod-east and vnet-dr-west.
Best answer: C
Explanation: Azure Site Recovery network mapping controls which target virtual network protected Azure VMs attach to after failover. In this scenario, the source production VNet should be mapped to the DR VNet that already contains the matching application subnets. Each protected VM’s network settings should target the appropriate DR subnet so the web and app tiers remain separated. The existing peering from the DR VNet to the hub then provides private connectivity to domain controllers and shared services. Mapping directly to the hub or relying only on peering does not place the failed-over NICs in the correct workload network.
Topic: Implement Disaster Recovery
An administrator configures Azure Site Recovery for an Azure VM named AppVM1 in East US. The recovery requirement is to replicate the VM to West US. The Recovery Services vault and target resource group are in West US. Enable replication fails before initial replication starts.
Replication health: Critical
Error: Cache storage account location does not match the source VM location.
Source VM region: East US
Selected cache account: stasrcachewus, West US
What is the most likely root cause?
Options:
A. The Recovery Services vault is in the target region.
B. The cache storage account is in the target region.
C. The target resource group is empty.
D. The VM uses managed disks.
Best answer: B
Explanation: In Azure-to-Azure Site Recovery, the source VM’s changed data is first written to a cache storage account before being replicated to the target region. That cache account must be in the same region as the source VM. In this case, AppVM1 is in East US, but the selected cache account is in West US, so replication cannot start. The target resource group and recovery resources belong in the target region, but the cache account follows the source region requirement.
The key takeaway is to separate source-side replication components from target-side recovery resources.
Use the Microsoft AZ-802 Practice Test page for the full IT Mastery practice bank, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Try Microsoft AZ-802 on Web View Microsoft AZ-802 Practice Test
Read the Microsoft AZ-802 Cheat Sheet for compact concept review before returning to timed practice.