Examkin

Question

Difficulty: HardDisaster Recovery and Business Continuity Execution

A financial payment gateway company hosts its primary transaction processing system on Compute Engine Managed Instance Groups (MIGs) in `us-east1` and maintains a warm standby disaster recovery environment in `us-central1`. The infrastructure utilizes a dedicated hybrid connection to on-premises data centers and connects to central shared security services in another VPC. During a catastrophic regional facility outage in `us-east1`, the incident response team executes their Disaster Recovery (DR) runbook to restore application processing in `us-central1` within an RTO of 15 minutes. Which TWO operational steps must the cloud engineering team perform to successfully execute the DR failover? (Select TWO.)

  1. Scale up the standby Compute Engine Managed Instance Groups in `us-central1` using pre-requested regional quota increases and capacity reservations.Answer
  2. Update the Cloud DNS routing policy to shift production traffic from the primary `us-east1` load balancer IP to the secondary `us-central1` load balancer IP.Answer
  3. C
    Re-architect and migrate standard regional Cloud SQL transactional databases to Cloud Spanner during the active failover procedure to establish zero-RPO multi-region write capability.
  4. D
    Route emergency traffic from the `us-central1` VPC through an existing VPC Network Peering connection to a central transit VPC to reach the shared services VPC without establishing direct peering.

Answer

The correct operational steps are to scale up the standby Managed Instance Groups in the disaster recovery region using pre-allocated regional quota and capacity reservations, and to update Cloud DNS routing policies to direct production traffic to the load balancer endpoint in the secondary region.
Executing a disaster recovery failover for compute workloads requires rapidly scaling standby instance capacity in the secondary region using pre-configured capacity reservations and regional quota allowances. Once backend compute resources are active, network entry points such as Cloud DNS routing policies must be updated to steer inbound client requests to the secondary regional load balancer.

Step-by-Step Solution

1
Ensure compute resources in the secondary region (`us-central1`) can be provisioned rapidly without hitting regional limit barriers.
The secondary Managed Instance Group successfully scales out instances backed by pre-arranged regional quotas and reservations.
Requesting quota increases during an active regional disaster takes too long and leads to failover execution failure.
2
Update global entry points to direct application traffic to the newly scaled backend infrastructure in `us-central1`.
Cloud DNS updates traffic steering to point to the active load balancer in the secondary region.
Traffic must be explicitly shifted to the secondary region to complete the failover process and restore application availability.

Key Concept

Disaster Recovery Execution and Capacity Management
Rate this question

Topics

Disaster Recovery and Business Continuity Execution

More questions from this topic