An enterprise financial platform runs its core transaction processing application on Compute Engine Managed Instance Groups (MIGs) with a Cloud SQL for PostgreSQL database in `us-east1`. The organization implements a Warm Standby disaster recovery strategy in `us-west1` to achieve a Recovery Point Objective (RPO) of under 1 minute and a Recovery Time Objective (RTO) of under 15 minutes. During a regional outage drill, the DR execution failover fails because the standby compute tier cannot scale up to match production traffic, and the secondary database tier cannot process incoming write transactions. Which TWO operational steps must be incorporated into the disaster recovery execution runbook to resolve these failures? (Select TWO.)
- Promote the cross-region Cloud SQL read replica in `us-west1` to a standalone primary database instance.Cevap
- Pre-request and maintain sufficient Compute Engine regional resource quotas in `us-west1` prior to failover execution.Cevap
- CReconstruct the database tier in `us-west1` by restoring nightly Cloud Storage export backups during the failover event.
- DEstablish VPC Network Peering between `us-east1` and `us-west1` so the secondary instances can access the primary database across peered VPCs using transitive routing.
Cevap
The disaster recovery execution runbook must include promoting the cross-region Cloud SQL read replica in the target region to a standalone writable primary instance and pre-requesting sufficient Compute Engine regional resource quotas in advance.
Promoting the Cloud SQL read replica in the failover region converts it to a primary database capable of serving read/write traffic, fulfilling low RPO requirements. Pre-requesting compute quotas in the target region ensures that Managed Instance Groups can scale up immediately without hitting API quota bottlenecks, fulfilling the RTO requirement.
Adım Adım Çözüm
Anahtar Kavram
Warm Standby Disaster Recovery Execution for Compute and Database Tiers