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?
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.
Why this answer
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.
Exam trap
The trap here is that candidates often 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.
How to eliminate wrong answers
Option A (Planned failover) is wrong because it is used for migrating VMs from a primary to a secondary region with zero data loss, typically during planned maintenance or migration, and it does impact the production environment by shutting down source VMs. Option C (Unplanned failover) is wrong because it is designed for actual disaster scenarios where the primary site is unavailable; it initiates failover without prior synchronization and directly affects production by making the replica VMs the new primary, which would disrupt operations. Option D (Failback) is wrong because it is the process of returning workloads to the primary site after a failover has occurred, and it assumes the production environment has already been impacted by a previous failover event.