Examkin

Question

Difficulty: HardDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A global pharmaceutical enterprise operates a mission-critical clinical trial telemetry ingestion platform on Google Cloud. The primary architecture runs in us-east4 with a secondary disaster recovery (DR) environment in us-west1. The system has a strict Recovery Point Objective (RPO) of 1 minute and a Recovery Time Objective (RTO) of 15 minutes. During a scheduled DR validation exercise, engineers simulated a primary region outage by updating Cloud DNS routing policies to direct incoming traffic to us-west1. Although cross-region data replication was up to date, the failover validation failed because auto-scaling Compute Engine Managed Instance Groups in us-west1 hit regional vCPU quota limits, preventing required instances from launching within the target RTO. Which procedure should the Cloud Architect incorporate into the disaster recovery validation framework to ensure RTO compliance during future failover drills?

  1. Implement automated pre-drill validation checks to verify regional quota availability and maintain Reserved Instance Capacity (capacity reservations) in the target DR region.Answer
  2. B
    Configure the automated DR failover script to issue an emergency API request for a regional quota increase from GCP Support upon detecting primary region failure.
  3. C
    Rearchitect the secondary DR environment from a warm-standby setup to a cold-standby backup-and-restore model using Cloud Storage disk snapshots to reduce baseline compute quota footprint.
  4. D
    Replace the dedicated Cloud Interconnect between regional VPCs with High Availability (HA) VPN tunnels configured with Cloud Router to dynamically bypass regional compute quota constraints during failover.

Answer

Implement automated pre-drill validation checks to verify regional quota availability and maintain Reserved Instance Capacity (capacity reservations) in the target DR region.
The correct strategy involves combining pre-drill automated quota validation checks with Compute Engine Capacity Reservations in the DR region. This ensures that the secondary region has both sufficient quota quota allocation and guaranteed compute capacity to spin up resources immediately, satisfying strict RTO requirements.

Step-by-Step Solution

1
Analyze the root cause of the DR validation failure.
The failover failed RTO constraints because Compute Engine instances could not scale up in the secondary region due to regional quota exhaustion.
Quota limits are enforced per region, and high-demand compute resources cannot be provisioned on demand if the project's regional quota is insufficient.
2
Evaluate GCP mechanism to ensure resource availability for strict RTO requirements.
Compute Engine Capacity Reservations allow reserving compute capacity in a specific zone/region so instances can launch immediately when needed.
Reservations guarantee capacity and protect against both quota limits (when combined with adequate quota limits) and stockouts during disaster recovery events.
3
Integrate capacity verification into the DR validation framework.
Establishing continuous pre-drill automated checks ensures quota sufficiency and reservation validity before an actual or simulated disaster drill takes place.
Proactive validation eliminates surprises during live DR failovers.

Key Concept

Disaster Recovery Capacity Planning and Quota Validation
Rate this question

Topics

Developing Procedures for Business Continuity and Disaster Recovery Validation