Examkin

Question

Difficulty: MediumDisaster Recovery and Business Continuity Execution

A global healthcare platform processes diagnostic imaging metadata using Compute Engine Managed Instance Groups (MIGs) in primary region us-central1 and maintains a cross-region read replica of its Cloud SQL PostgreSQL database in us-east4 for disaster recovery. The organization mandates a Recovery Time Objective (RTO) of under 15 minutes and a Recovery Point Objective (RPO) of under 1 minute. During a scheduled disaster recovery drill in us-east4, promoting the database replica succeeds, but application compute instances fail to launch at scale, causing a prolonged outage. Which architectural adjustment should the Cloud Architect implement to ensure reliable execution during a regional failover?

  1. Pre-request sufficient Compute Engine resource quotas in us-east4 and maintain a minimal pre-provisioned warm standby MIG capacity that auto-scales upon failover.Answer
  2. B
    Rely on cold standby MIGs scaled to zero instances in us-east4 that trigger auto-scaling only after Cloud DNS health checks failover.
  3. C
    Replace cross-region database replication with automated hourly Cloud Storage database export snapshots restored to a new Cloud SQL instance upon disaster declaration.
  4. D
    Configure VPC Network Peering between us-central1 and us-east4 to allow application instances in us-east4 to route transitively through us-central1 to reach shared services.

Answer

Pre-request sufficient Compute Engine resource quotas in us-east4 and maintain a minimal pre-provisioned warm standby MIG capacity that auto-scales upon failover.
Pre-allocating regional Compute Engine quotas in the DR region (us-east4) and maintaining a minimal warm standby compute footprint guarantees that capacity is reserved and ready to accept traffic immediately. This meets both the 1-minute RPO (via continuous DB replication) and 15-minute RTO targets.

Step-by-Step Solution

1
Analyze DR requirements and identify cause of failover failure.
The failover failed because compute instances could not scale up quickly enough due to unverified quotas and cold start overhead in the target region.
Meeting an RTO under 15 minutes requires both available infrastructure capacity and sufficient service quota.
2
Evaluate compute scaling and quota provisioning options for the target DR region.
Pre-requesting regional Compute Engine quota and running a minimal warm standby MIG ensures baseline availability and guaranteed resource allocation.
Default quotas in secondary regions may not match primary workloads, causing instance creation failures during sudden failover events.

Key Concept

Disaster Recovery Execution and Regional Quota Planning
Rate this question

Topics

Disaster Recovery and Business Continuity Execution

More questions from this topic