Courseiva

AZ-305 Design business continuity solutions Practice Question

A company has a disaster recovery plan that requires testing failover of Azure VMs regularly without impacting the production environment. Which feature of Azure Site Recovery should they use?

⚠ Common exam trap

Many candidates confuse 'test failover' with 'planned failover' because both involve controlled processes, but planned failover is intended for actual migration or maintenance and does impact production by shutting down source VMs, whereas test failover is purely for validation with zero production impact.

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 B) is the correct feature for validating disaster recovery readiness without affecting the production environment. Azure Site Recovery's test failover creates an isolated copy of the replicated VMs in a separate virtual network, allowing you to run validation exercises, perform application testing, and verify recovery plans without any impact on the production VMs or ongoing replication. This ensures that the failover process works correctly while maintaining production continuity.

Answer analysis

Option-by-option breakdown

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

  • ✗

    Planned failover

    Why it's wrong here

    Planned failover is an intentional, controlled process typically executed for migration, maintenance, or other scheduled activities where downtime is coordinated. It does not satisfy disaster recovery testing requirements because it operates on the production environment and can affect live workloads, whereas a test must be isolated and non-disruptive. Therefore, it is incorrect for this scenario.

  • ✓

    Test failover

    Why this is correct

    Test failover is the correct choice because it creates an isolated, non-production replica of the protected environment, allowing validation of recovery procedures without impacting live systems. It provides a safe, reversible mechanism to verify that recovery points and recovery time objectives can be met, making it the standard method for disaster recovery testing.

  • ✗

    Unplanned failover

    Why it's wrong here

    Unplanned failover is triggered automatically or manually in response to an actual disaster or critical failure, and it transitions production operations to the replica site. It is a real, high-stakes operation that should not be used for routine testing because it risks data loss, downtime, and unintended production impact. Hence, it is not appropriate for a scheduled DR test.

  • ✗

    Failback

    Why it's wrong here

    Failback is the process of returning workloads to the primary site after a failover has occurred, often requiring replication reversal and synchronization. It is not a testing procedure but a post-disaster recovery step, and using it for testing could cause unnecessary production disruption. Therefore, it is incorrect for validating disaster recovery readiness.

Go deeper

Related to this question

About these practice questions

One of 795 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 →

How Courseiva writes practice questions · Editorial policy

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.