An online retail platform processes customer orders in the primary region `europe-west1` and maintains a warm standby disaster recovery setup in `europe-west4`. The architecture uses Cloud SQL for PostgreSQL with cross-region asynchronous read replicas and Compute Engine Managed Instance Groups (MIGs) fronted by Cloud Load Balancing and Cloud DNS. Business operational requirements specify a Recovery Point Objective (RPO) of under 1 minute and a Recovery Time Objective (RTO) of under 15 minutes. During a total regional failure of `europe-west1`, which TWO actions must be executed as part of the regional disaster recovery failover runbook? Select 2 response options.
- Promote the cross-region read replica of Cloud SQL in `europe-west4` to a standalone primary database instance.Cevap
- Update Cloud DNS routing policies to direct traffic to the active Cloud Load Balancer endpoint in `europe-west4`.Cevap
- CRestore the Cloud SQL database in `europe-west4` from an automated nightly Cloud Storage snapshot export.
- DRequest an urgent Compute Engine CPU quota increase in `europe-west4` to allow the secondary MIG to scale up during the active incident.
Cevap
Executing disaster recovery for this scenario requires promoting the cross-region Cloud SQL read replica in the failover region and updating Cloud DNS routing policies to direct client traffic to the secondary region's load balancer.
Promoting the cross-region Cloud SQL read replica in `europe-west4` converts it into an independent read-write primary database, preserving near real-time data to satisfy the sub-minute RPO. Concurrently, modifying Cloud DNS routing policies shifts global application traffic to the secondary load balancer endpoint, meeting the sub-15-minute RTO requirement.
Adım Adım Çözüm
Anahtar Kavram
Disaster Recovery Execution and Cross-Region Failover Sequence