A pharmaceutical research firm hosts its core analytics pipeline in Google Cloud with a primary deployment in region `us-central1`. The workload consists of a stateless application running on Compute Engine Managed Instance Groups (MIGs) and an operational database on Cloud SQL for PostgreSQL. The firm is configuring a warm standby disaster recovery plan targeting region `us-east4` to achieve an RPO of under 5 minutes and an RTO of under 15 minutes, while keeping idle steady-state costs low. Which of the following execution steps must be included in the emergency failover runbook? (Select TWO answers.)
- Promote the cross-region Cloud SQL for PostgreSQL read replica located in `us-east4` to become a standalone primary database instance.Cevap
- Resize the pre-configured warm standby Compute Engine MIG in `us-east4` from its baseline capacity up to full production capacity.Cevap
- CSubmit an emergency request to Google Cloud Support for a Compute Engine CPU quota increase in `us-east4` at the moment failover is initiated.
- DMigrate the primary Cloud SQL instance data into a single-region Cloud Spanner database in `us-east4` during the failover window.
Cevap
The correct execution steps are promoting the cross-region Cloud SQL read replica in the DR region to a standalone primary database and scaling up the warm standby Compute Engine Managed Instance Group in the DR region to production capacity.
Executing a warm standby DR failover for relational workloads requires promoting the cross-region read replica to a writable primary database and expanding the compute instance group capacity in the DR region. These actions ensure data accessibility with minimal RPO and restore service capacity rapidly within the target RTO.
Adım Adım Çözüm
Anahtar Kavram
Warm Standby Disaster Recovery Execution for Compute Engine and Cloud SQL