An enterprise organization is establishing a standardized disaster recovery (DR) validation procedure for a critical multi-region application on Google Cloud. The architecture uses Cloud SQL cross-region read replicas and Compute Engine managed instance groups (MIGs). In what operational sequence should a cloud architect execute the disaster recovery failover drill from start to finish?
- 1Verify and request necessary Compute Engine quota increases in the target secondary region.
- 2Promote the secondary Cloud SQL read replica to a standalone primary database instance.
- 3Update Cloud DNS routing policies to direct user traffic to the secondary region endpoint.
- 4Execute automated synthetic workload tests to validate application integrity, RPO, and RTO metrics.
Answer
The correct operational sequence is: 1) Verify and request necessary Compute Engine quota increases in the target secondary region, 2) Promote the secondary Cloud SQL read replica to a standalone primary database instance, 3) Update Cloud DNS routing policies to direct user traffic to the secondary region endpoint, and 4) Execute automated synthetic workload tests to validate application integrity, RPO, and RTO metrics.
A sound business continuity validation procedure begins with pre-drill verification of target region compute quotas to guarantee capacity. Once capacity is assured, the secondary database is promoted to primary status so that it can receive writes. Next, network endpoints (Cloud DNS) are switched to route incoming traffic to the secondary region. Finally, synthetic transaction tests run to validate data loss (RPO) and operational restore time (RTO).
Step-by-Step Solution
Key Concept
Disaster Recovery Failover Validation Sequence