Question

Difficulty: MediumDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An international freight logistics enterprise operates its core container dispatch platform on Google Cloud using `europe-west1` as its primary region and `europe-west4` as a secondary disaster recovery (DR) region. Business operations mandate a Recovery Time Objective (RTO) of 30 minutes and a Recovery Point Objective (RPO) of under 5 minutes. During a scheduled DR validation drill, traffic was switched to `europe-west4`, but compute instance creation failed because the target project lacked sufficient N2 CPU regional quotas in `europe-west4`, breaching the RTO. Which procedure should the cloud architect incorporate into the business continuity and DR validation framework to prevent this failure in future drills?

  1. Implement automated pre-drill validation checks that audit secondary region resource quotas and pre-reserve compute capacity prior to executing failover procedures.Answer
  2. B
    Reconfigure the secondary DR environment to use a cold-standby strategy relying on Cloud Storage disk snapshots to avoid keeping active compute quotas reserved.
  3. C
    Deploy a Cloud Interconnect connection between `europe-west1` and `europe-west4` to dynamically transfer compute instance quotas between regions during failover.
  4. D
    Configure operational alerts to automatically initiate a Cloud Quotas increase request when compute instance creation errors occur during the DR drill.

Answer

Implement automated pre-drill validation checks that audit secondary region resource quotas and pre-reserve compute capacity prior to executing failover procedures.
Pre-verifying regional project quotas and establishing compute capacity reservations in the secondary region before executing DR drills ensures that required compute instances can launch immediately without hitting quota limits or capacity constraints, satisfying the 30-minute RTO requirement.

Step-by-Step Solution

1
Analyze the root cause of the DR validation failure
The failover failed because compute resources could not be provisioned due to insufficient regional N2 CPU quota in `europe-west4`.
GCP resource quotas are region-specific and must be requested and verified before spinning up secondary workloads.
2
Evaluate DR requirements against potential resolution procedures
The enterprise mandates an RTO of 30 minutes and RPO under 5 minutes, requiring fast provisioning and guaranteed resource availability.
Reactive quota requests or cold-standby architectures introduce significant recovery delays that exceed the target RTO.
3
Select the correct validation procedure
Automating pre-drill quota validation and enforcing capacity reservations in `europe-west4` guarantees resource allocation during failover tests.
Pre-drill checks ensure all operational prerequisites, including quotas and compute capacity, are met prior to shifting traffic.

Key Concept

Developing Procedures for Business Continuity and Disaster Recovery Validation
Rate this question