Examkin

Question

Difficulty: HardDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A digital healthcare company processes real-time patient telemetry using an enterprise application hosted in Google Cloud's `us-central1` region. The application relies on Cloud Bigtable for high-throughput sensor ingested data and Compute Engine Managed Instance Groups (MIGs) for stateless processing. The organization's business continuity policy mandates a Disaster Recovery (DR) RPO of 0 and an RTO of under 15 minutes in `us-east4`. The lead cloud architect is establishing automated DR validation procedures to execute non-disruptive quarterly failover drills. Which procedural step must be incorporated into the pre-drill validation protocol to ensure the failover procedure satisfies the RTO requirement without runtime failures?

  1. Programmatically verify and pre-allocate regional resource quotas and capacity reservations in `us-east4` prior to initiating traffic rerouting.Answer
  2. B
    Rely on standard regional default GCP compute quotas and trigger DNS rerouting immediately upon detecting primary region heartbeat failure.
  3. C
    Transition the database architecture to restore daily Cloud Storage cold-standby snapshots in `us-east4` during the validation routine to minimize standing compute overhead.
  4. D
    Route cross-region failover validation database replication over standard Cloud VPN tunnels with default 3 Gbps limits instead of Dedicated Interconnect.

Answer

Programmatically verifying and pre-allocating regional resource quotas and capacity reservations in the target DR region prior to traffic rerouting is essential to ensure failover succeeds within RTO constraints.
Pre-validating regional quotas and securing capacity reservations in the secondary region ensures that when DR failover occurs, the secondary environment can scale up Compute Engine MIGs and provision resources instantly without hitting quota limits or resource shortages, thereby meeting the strict RTO of under 15 minutes.

Step-by-Step Solution

1
Analyze DR constraints and target metrics
Identified strict requirements of RPO = 0 and RTO < 15 minutes for real-time telemetry processing across regions.
Validation procedures must ensure both zero data loss and rapid service restoration.
2
Evaluate pre-failover validation requirements in target GCP region
Recognized that regional quotas (e.g., vCPU limits, in-use IP addresses) in `us-east4` can block MIG scaling if not requested and validated in advance.
Quota acquisition requests are not instant; failing to verify quotas beforehand breaks RTO guarantees.
3
Select the optimal validation procedure
Automated pre-flight quota checks and capacity reservation verifications prior to DNS and traffic switchover.
Ensures targeted secondary infrastructure can immediately absorb production traffic without provisioning errors.

Key Concept

Disaster Recovery Validation and Regional Resource Quota Management
Estimated Time:2m 0s
Rate this question

Topics

Developing Procedures for Business Continuity and Disaster Recovery Validation