Examkin

Question

Difficulty: MediumDisaster Recovery and Business Continuity Execution

A maritime logistics enterprise hosts its vessel tracking platform on Google Cloud with primary infrastructure running in region `europe-west1` and a warm standby disaster recovery site in `europe-west4`. The architecture utilizes Cloud SQL for PostgreSQL with a cross-region read replica in `europe-west4`, while the stateless application tier runs on Managed Instance Groups (MIGs). In the event of a catastrophic regional outage in `europe-west1`, which TWO operational steps must the site reliability engineering team execute to restore full application write capabilities and user traffic routing within the targeted 15-minute Recovery Time Objective (RTO)?

  1. Promote the Cloud SQL cross-region read replica in `europe-west4` to a standalone primary database instance to enable write operations.Answer
  2. Reconfigure the HTTP(S) Load Balancer backend service or Cloud DNS routing policies to direct user traffic to the secondary MIG in `europe-west4`.Answer
  3. C
    Rely on existing VPC Network Peering configurations to transitively route incoming client traffic from `europe-west1` entry points to `europe-west4` compute resources without updating public routing.
  4. D
    Submit a quota increase request for Compute Engine vCPUs in `europe-west4` as the first step of the emergency failover runbook to permit instance scaling.

Answer

During a regional disaster failover, write operations must be restored by promoting the cross-region Cloud SQL read replica in europe-west4 to a standalone instance, and user traffic must be redirected by updating the load balancer backend service or Cloud DNS routing policy to target the secondary region.
Executing a disaster recovery failover for a warm standby architecture requires two primary actions: restoring data persistence write capabilities by promoting the Cloud SQL cross-region read replica to a standalone primary instance, and redirecting client network traffic to the secondary region by updating global load balancer backend services or Cloud DNS records.

Step-by-Step Solution

1
Promote the database replica in the failover region
The Cloud SQL read replica in europe-west4 is converted into a writable standalone database instance.
Cloud SQL cross-region read replicas are read-only until explicitly promoted during a failover procedure.
2
Redirect network traffic to the secondary region
Ingress traffic is steered directly to the running compute instances in europe-west4.
Updating global load balancing backend weights or DNS records points client requests away from the failed primary region.

Key Concept

Cross-Region Disaster Recovery Execution and Failover Mechanics
Rate this question

Topics

Disaster Recovery and Business Continuity Execution

More questions from this topic