Examkin

Soru

Zorluk: OrtaDisaster Recovery and Business Continuity Execution

An aerospace satellite operations company hosts its ground telemetry monitoring system on Google Cloud. The primary workload runs in region `europe-west1`, utilizing Compute Engine Managed Instance Groups (MIGs) for application servers and Cloud SQL for PostgreSQL for critical mission metadata. To comply with regulatory requirements, the system requires a Disaster Recovery (DR) warm standby in `europe-west4` capable of achieving a Recovery Point Objective (RPO) of near-zero and a Recovery Time Objective (RTO) under 15 minutes. A regional catastrophe causes a complete failure of `europe-west1`. Which set of disaster recovery execution steps should the cloud architect specify in the failover runbook?

  1. Promote the cross-region Cloud SQL read replica in `europe-west4` to a standalone primary instance, reconfigure the `europe-west4` MIG application instances to target the promoted database, and update Cloud DNS routing policies to direct traffic to `europe-west4`.Cevap
  2. B
    Restore the latest automated Cloud SQL export file from a Cloud Storage multi-region bucket into a newly created Cloud SQL instance in `europe-west4`, then update Cloud DNS records.
  3. C
    Spin up new Compute Engine MIG instances in `europe-west4` during failover execution without requesting pre-allocated regional CPU quota, relying on automatic GCP project quota expansion during regional outage events.
  4. D
    Route traffic from application servers in `europe-west4` through a transitive VPC Peering connection via a central hub VPC to access the database proxy in `europe-west1` until the primary region recovers.

Cevap

Promote the cross-region Cloud SQL read replica in `europe-west4` to a standalone primary instance, reconfigure the `europe-west4` MIG application instances to target the promoted database, and update Cloud DNS routing policies to direct traffic to `europe-west4`.
Promoting a cross-region Cloud SQL read replica to a standalone primary database is the standard GCP disaster recovery pattern for relational workloads requiring near-zero RPO and fast RTO. Because data is asynchronously replicated continuously across regions, promoting the replica provides immediate read-write capability. Updating application configurations and DNS routing completes the regional failover sequence within the required time window.

Adım Adım Çözüm

1
Promote the standby database replica in the DR region
The Cloud SQL cross-region read replica in `europe-west4` becomes a read-write primary instance with minimal data latency loss.
Cross-region read replicas continuously replicate write-ahead logs from the primary region, providing near-zero RPO.
2
Reconfigure application connection endpoints
Application workloads in `europe-west4` point directly to the local promoted Cloud SQL instance.
Applications must reference the newly promoted read-write database endpoint to resume operational capability.
3
Switch global network traffic via Cloud DNS
Ingress traffic is rerouted from `europe-west1` to `europe-west4`.
Updating Cloud DNS routing policies directs external telemetry streams to the functional DR region.

Anahtar Kavram

Disaster Recovery execution using Cloud SQL cross-region read replica promotion
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Disaster Recovery and Business Continuity Execution

Bu konudan daha fazla soru