AZ-305 Design business continuity solutions Practice Question
Which THREE of the following are valid strategies for designing a disaster recovery plan for Azure Virtual Desktop? (Choose three.)
⚠ Common exam trap
Candidates often confuse Azure Front Door (an HTTP/HTTPS load balancer) with Azure Traffic Manager (a DNS-based traffic router that can handle RDP traffic), leading them to incorrectly select Option A instead of Option C.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Azure File Sync to replicate FSLogix profile shares to a secondary region
Option B is correct because Azure File Sync can replicate the SMB file shares that host FSLogix profile containers and Office container VHDX files to a secondary region, giving users access to their profiles during a regional failover. Option C is correct because pre-deploying a secondary host pool in the DR region and using Azure Traffic Manager (or a similar global load balancer) to redirect user connections is a standard AVD multi-region DR pattern that reduces recovery time. Option E is correct because Azure Site Recovery can continuously replicate session host VMs to a secondary region so they can be failed over and brought online as replacement session hosts during a disaster. Option A is not valid because Azure Front Door does not proxy RDP traffic (TCP 3389); it is an HTTP/HTTPS layer-7 service, and AVD clients connect to the gateway/broker, not through Front Door. Option D is not a valid DR strategy because Azure Backup restores data and VMs but does not provide the low-RTO regional failover or the AVD control-plane/broker redirection needed for a disaster recovery plan.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Azure Front Door to route RDP traffic to the secondary region
Why it's wrong here
Azure Front Door operates at Layer 7 and only accepts HTTP/HTTPS traffic, so it cannot forward raw RDP over TCP 3389. RDP requires a network-level forwarder such as Azure Load Balancer or Azure Firewall; Front Door lacks TCP passthrough and port-forwarding capabilities. Thus this is not a valid way to route AVD connections to a secondary region.
- ✓
Use Azure File Sync to replicate FSLogix profile shares to a secondary region
Why this is correct
Azure File Sync replicates the file hierarchy from a primary SMB share to a file share in the secondary region, keeping FSLogix profile containers available to users after failover. Because FSLogix profiles are stored as VHDX files in file shares, sync copies them without needing a backup restore, and the DR region's session hosts simply attach to the synced share. This preserves persistent user state and is a valid DR strategy when combined with compute failover.
- ✓
Pre-deploy a secondary host pool in the DR region and use Azure Traffic Manager to redirect connections
Why this is correct
Pre-deploying a secondary host pool and using Azure Traffic Manager provides DNS-level redirection of AVD client connections to the DR region. Traffic Manager can route users to the secondary region's RD Gateway and broker endpoint based on endpoint availability, and because VMs are already running failover is faster than provisioning on demand. This is valid, but it must be paired with profile synchronization or replication to give users a complete desktop experience.
- ✗
Rely on Azure Backup to restore session hosts in the secondary region
Why it's wrong here
Azure Backup protects session host VMs by creating recovery point snapshots, but restoring those VMs to a secondary region requires substantial time and a Recovery Services vault with cross-region restore configured. Backup and restore is designed for recovery from data loss, not continuous disaster recovery or automatic failover, and the RTO is typically too long for an AVD failover scenario. This makes it an inadequate standalone strategy for replicating session hosts to a secondary region.
- ✓
Replicate session host VMs to a secondary region using Azure Site Recovery
Why this is correct
Azure Site Recovery continuously replicates session host VMs from the primary region to the secondary region, enabling orchestrated failover with RTO measured in minutes. Because AVD session hosts are regular IaaS VMs, ASR can bring them online in the DR region while preserving their OS and installed extensions. This is a valid and supported DR strategy for AVD compute capacity, especially when combined with FSLogix profile replication.
Visual reference
Go deeper
Related to this question
Learn chapter
Azure Service Bus Topology Design
Key term
Azure Site Recovery
Azure Site Recovery is a Microsoft Azure service that keeps your business applications and data running by automatically replicating them to a secondary location and failing over if the primary site goes down.
Key term
Disaster Recovery Design
Disaster Recovery Design is the process of planning and implementing strategies to restore IT systems and data after a catastrophic failure, ensuring business continuity with minimal downtime and data loss.
About these practice questions
Courseiva writes every AZ-305 question from scratch — 795 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-305 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-305 exam.