Examkin

Question

Difficulty: HardDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An international commercial airline hosts its mission-critical flight scheduling and crew dispatch platform on Google Cloud, operating primarily out of us-central1 with a secondary disaster recovery deployment in us-east4. The system is designed to meet a Recovery Point Objective (RPO) of under 5 minutes and a Recovery Time Objective (RTO) of under 30 minutes. During a scheduled disaster recovery validation drill simulating a total loss of us-central1, database failover completed within RPO target limits and Cloud DNS failover routing was initiated. However, the secondary region failed to meet the target RTO because Compute Engine instance groups in us-east4 could not scale up to handle production traffic due to unrequested regional vCPU quota limits. Which procedure should the Cloud Architect implement to ensure future disaster recovery validation drills and actual failovers successfully meet business continuity objectives?

  1. Implement automated pre-drill verification procedures to audit regional vCPU quota limits and maintain active Compute Engine capacity reservations in the disaster recovery region.Answer
  2. B
    Re-architect the secondary region to use a cold-standby pilot light configuration where compute resources are only requested and provisioned after DNS failover is completed.
  3. C
    Establish High Availability VPN tunnels between us-central1 and us-east4 to redirect failed compute traffic back to primary regional gateway pools during disaster recovery drills.
  4. D
    Migrate the underlying relational database to Cloud Spanner across both regions to automatically expand regional Compute Engine vCPU quotas upon failover.

Answer

Establish automated pre-drill verification procedures that audit regional quotas and maintain Compute Engine capacity reservations in the disaster recovery region.
The correct option establishes pre-drill automated verification of regional vCPU quotas and utilizes Compute Engine capacity reservations in the secondary region. Disaster recovery validation procedures must ensure that target regions not only have correct configuration states, but also sufficient quota limits and reserved compute capacity to handle full production traffic within specified RTO constraints.

Step-by-Step Solution

1
Analyze the root cause of the disaster recovery RTO failure.
Identified that compute instances in the secondary region (us-east4) failed to scale up due to hitting regional Compute Engine vCPU quota limits during failover execution.
GCP resource quotas are enforced at a regional level and must be requested and verified prior to requiring large compute scale-outs.
2
Evaluate validation procedure requirements for business continuity and disaster recovery.
Determined that robust DR validation procedures must verify resource availability, quotas, and baseline infrastructure state in the target region ahead of simulated or real failovers.
Preventive automated pre-checks and compute capacity reservations guarantee that the secondary region has sufficient guaranteed headroom to accommodate workload failover within RTO parameters.
3
Formulate the optimal architectural validation procedure.
Combine pre-drill automated quota auditing with Compute Engine capacity reservations in us-east4.
This guarantees required capacity and quota compliance before traffic diversion occurs.

Key Concept

Disaster Recovery Validation Procedures and Regional Resource Quota Management
Rate this question

Topics

Developing Procedures for Business Continuity and Disaster Recovery Validation