Question 890
After a genuine and committed Azure-to-Azure Site Recovery failover, billing services have run in West US for four days. East US is healthy again. The team has already completed Re-protect from West US back to East US, and reverse replication is Healthy with current data. The owner approves returning production to East US with a controlled cutover. Which operation should follow?
Explanation
Correct Answer
Once reverse replication is healthy and authorized, a controlled planned failover/failback brings up the recovered original-region workload. Verify applications and client networking before traffic cutover, commit as supported and re-establish ongoing secondary-region protection.
Incorrect Answers
Re-protect is already complete in the scenario; it prepares replication direction and does not by itself initiate the operational return to the original production region. The next step is a supported planned recovery cutover.
DNS changes alone cannot create or validate the target-region machines or their application state. Sending users to an old endpoint before failback would risk downtime or stale data even when reverse replication is healthy.
Test failover creates an isolated rehearsal workload and is cleaned up later. It doesn't commit the real primary-region return or restore the intended production replication direction.