AZ-305 Design infrastructure solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure Backup

  Why it's wrong here

  Azure Backup delivers snapshots and point-in-time recovery of Azure VMs and workloads to a Recovery Services vault, allowing you to restore data from a previous state after corruption or accidental deletion. However, it does not provide continuous asynchronous replication to a secondary region, nor does it orchestrate a DNS cutover or failover of VM compute — meaning there is no automatic failover to a standby location. For that reason, Backup is effectively the 'safety net' for data, not the DR failover mechanism.

• ✓

  Azure Site Recovery test failover capability

  Why this is correct

  Azure Site Recovery's test failover capability lets you perform a real failover of replicated VMs into an isolated Network Security Group-backed test network, without affecting the production environment or the ongoing replication stream. This exercise validates the orchestration of your recovery plan, as well as the boot order, IP addressing, DNS resolution, and connectivity of your recovered workloads — essentially a no-cost dress rehearsal of DR. It directly satisfies the need to prove that a DR solution actually works before a real outage occurs.

• ✓

  Azure Site Recovery

  Why this is correct

  Azure Site Recovery itself is a comprehensive DR orchestration service that continuously replicates Azure VMs or on-premises Hyper-V/VMware VMs to a primary or secondary Azure region, maintaining a configurable RPO in the range of as low as 30 seconds. It automates failover and failback with a structured recovery plan that sequences VMs in the correct order and supports actions such as scripts, runbooks, and notifications. With ASR, you achieve a genuinely automated disaster recovery that meets the RTO/RPO requirements of a critical application, and the test-failover capability is a built-in verification feature of it.

• ✓

  Azure Traffic Manager

  Why this is correct

  Azure Traffic Manager operates at the DNS layer to route end-user traffic to an application endpoint deployed in the primary or secondary region, using priority routing to failover automatically when a health probe fails. This is the traffic-routing half of a DR strategy: after ASR has failed over the VM across regions, Traffic Manager must be updated or health probes must detect the down primary and send users to the secondary IP. It does not replicate data, but it is essential for redirecting user traffic with a controlled DNS-based failover in multi-region architectures.

• ✗

  Azure Front Door

  Why it's wrong here

  Azure Front Door is a global reverse proxy that routes HTTP(S) traffic and provides CDN capabilities, web application firewall (WAF) protection, SSL termination, and path-based routing, rather than cheap DNS-based geoproximity routing like Traffic Manager. While Front Door could technically serve as a global load balancer in a DR design, it adds significant complexity and cost, and it is redundant if you've already implemented Traffic Manager for geo-routing of a DR scenario. It is certainly not a requirement or replacement for Site Recovery; it's an optional entry point, and using both for the same DR route is over-engineered.

Go deeper

Related to this question