AZ-305 Design business continuity solutions Practice Question
A company runs a critical application on Azure virtual machines (VMs) in the West US region. They need a disaster recovery solution that replicates the VMs to East US with a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 2 hours. The application consists of multiple VMs, and the company needs to be able to fail over a single VM without impacting others during an actual disaster. They also want to periodically test the recovery process without affecting the production environment. Which Azure Site Recovery feature should they use to enable non-disruptive testing?
⚠ Common exam trap
Many exam-takers confuse 'Test failover' with 'Planned failover' or 'Recovery Plans,' mistakenly thinking that any failover action must impact production, when in fact Test failover is specifically designed to be isolated and non-disruptive.
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
✓
Test failover
Test failover (Option C) is the correct feature because it allows you to validate your disaster recovery process by creating an isolated copy of your replicated VMs in a separate test network, without impacting the ongoing replication or the production environment. This directly meets the requirement for periodic, non-disruptive testing while maintaining the RPO of 15 minutes and RTO of 2 hours.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Recovery Plans
Why it's wrong here
An Azure Site Recovery Recovery Plan groups multiple VMs into a single failover unit, allowing you to define sequencing, runbooks, and automated action steps for orchestration. However, it is an execution framework for real failover and failback, not a mechanism for isolated validation. Running a recovery plan without a test-failover action would trigger actual failover, potentially disrupting production, so the plan itself cannot provide a non-disruptive drill environment.
- ✗
Planned failover
Why it's wrong here
Planned failover is a migration operation that flushes all pending replication data to the secondary region and then shuts down the source VMs to ensure zero data loss. It assumes you are intentionally accepting downtime and switching production from primary to DR, which is not a validation exercise. Because it impacts the live application and changes the active region, it cannot serve as an isolated test of your disaster recovery readiness.
- ✓
Test failover
Why this is correct
Test failover performs a full validation of replicated VM images by booting them in an isolated virtual network using a selectable recovery point, without disturbing ongoing replication or production traffic. It requires no source VM shutdown and can be run repeatedly for compliance and disaster-recovery drills. This isolated copy allows you to verify application startup and network dependencies exactly as they would behave in a real failover, making it the correct feature for non-disruptive testing.
- ✗
Network mapping
Why it's wrong here
Network mapping is a configuration setting in Azure Site Recovery that links a source virtual network to a target subnet in the DR region, determining the IP addressing and connectivity of failed-over VMs. It does not perform any compute or boot activity, nor does it segregate test workloads from production. As a static prerequisite for failover, it lacks the ability to create an isolated testing environment, so it is not a tool for running disaster-recovery drills.
Go deeper
Related to this question
Learn chapter
Designing Azure Storage Solutions
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
BIA and RPO RTO Design
Business Impact Analysis and the design of Recovery Point Objective and Recovery Time Objective define how much data loss and downtime a business can tolerate after an IT failure, guiding the architecture of backup and disaster recovery systems.
About these practice questions
One of 204 original AZ-305 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.