Examkin

Soru

Zorluk: Çok zorDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A global logistics provider hosts a mission-critical fleet routing platform on Google Cloud. The primary architecture runs in us-east4 using Managed Instance Groups (MIGs) and a multi-region Cloud Spanner database instance. The organization requires a strict Disaster Recovery (DR) policy with a Recovery Point Objective (RPO) of near-zero and a Recovery Time Objective (RTO) of less than 15 minutes. During a scheduled regional failover validation exercise, traffic was redirected to the secondary standby region (us-west1). Although database synchronization succeeded, the MIG in us-west1 failed to scale up to handle the sudden burst of failover traffic because the project hit the regional compute CPU quota limit, resulting in extended service downtime and an RTO breach. Which procedure should the Cloud Architect mandate in the BCP/DR validation plan to prevent this issue in future failover drills?

  1. Implement a pre-drill validation checklist that auditing regional compute quota limits against anticipated failover demand and securing Compute Engine capacity reservations in the target DR region prior to executing failover drills.Cevap
  2. B
    Transition the disaster recovery strategy to a cold-standby model utilizing hourly Cloud Storage disk snapshots restored upon incident trigger to eliminate baseline resource quota consumption in us-west1.
  3. C
    Configure Cloud Logging alerting to request automated real-time quota limit increases from Google Cloud Support dynamically at the moment the MIG failover scaling threshold is breached.
  4. D
    Replace Cloud Spanner with a Cloud SQL instance utilizing cross-region read replicas to reduce the regional compute footprint required for database management during failover validation.

Cevap

Implement a pre-drill validation checklist that audits regional compute quota limits against anticipated failover demand and secures Compute Engine capacity reservations in the target DR region prior to executing failover drills.
The correct approach requires proactively verifying regional quotas and using Compute Engine capacity reservations in the target disaster recovery region prior to conducting failover drills. This guarantees that necessary compute capacity exists and is immediately allocable when failover traffic shifts, preventing RTO breaches caused by quota exhaustion.

Adım Adım Çözüm

1
Analyze the root cause of the failure during the DR drill.
The failure occurred because the compute layer in the secondary region encountered regional quota exhaustion when attempting to scale up to accept production load.
GCP resource quotas are enforced per project per region. Even if code and configuration are valid, unmanaged quota limits block resource creation.
2
Evaluate the mandatory business objectives (RPO < 1 min, RTO < 15 min).
Any validation procedure must guarantee instant availability of compute capacity without asynchronous snapshot restoration delay or manual intervention.
Cold standby or on-demand quota escalation cannot meet strict RTO constraints during sudden regional failover.
3
Define the proper BCP and DR validation policy enhancement.
Incorporate explicit pre-validation quota verification and Compute Engine capacity reservations in the secondary region as part of standard DR drill execution procedures.
Capacity reservations guarantee project compute availability up to specified limits, eliminating quota bottlenecks during DR failover.

Anahtar Kavram

Disaster Recovery Capacity Planning and Regional Quota Validation
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation