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?
- Implement automated pre-drill validation checks that audit secondary region resource quotas and pre-reserve compute capacity prior to executing failover procedures.Cevap
- BReconfigure the secondary DR environment to use a cold-standby strategy relying on Cloud Storage disk snapshots to avoid keeping active compute quotas reserved.
- CDeploy a Cloud Interconnect connection between `europe-west1` and `europe-west4` to dynamically transfer compute instance quotas between regions during failover.
- DConfigure operational alerts to automatically initiate a Cloud Quotas increase request when compute instance creation errors occur during the DR drill.
Cevap
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.
Adım Adım Çözüm
Anahtar Kavram
Developing Procedures for Business Continuity and Disaster Recovery Validation