An enterprise application hosted in a primary Google Cloud region experiences a total regional failure. The cloud operations team must execute the Disaster Recovery (DR) failover runbook to switch service to a warm standby environment in a secondary region. What is the correct chronological sequence of operational steps to safely complete this failover?
- 1Promote the cross-region database replica in the secondary region to a standalone primary database.
- 2Scale up compute resources in the secondary region from standby capacity to full production capacity.
- 3Update Cloud DNS record sets to point incoming application traffic to the secondary region's HTTP(S) Load Balancer.
- 4Perform validation testing and monitor application metrics to confirm operational stability in the secondary region.
Answer
The correct operational order is: first promote the secondary database replica to primary, second scale up secondary compute capacity, third update Cloud DNS to redirect traffic, and fourth verify application performance and system health.
Executing a disaster recovery failover requires establishing data write availability first, provisioning sufficient compute capacity second, rerouting external traffic third, and finally verifying post-cutover system health.
Step-by-Step Solution
Key Concept
Disaster Recovery Failover Execution Workflow