Examkin

Soru

Zorluk: OrtaDisaster Recovery and Business Continuity Execution

A digital banking platform hosts its primary transactional processing engine in GCP region `us-central1` with a hot standby disaster recovery (DR) site configured in `us-east4`. The application uses Compute Engine Managed Instance Groups (MIGs) that auto-scale based on incoming traffic demands. During an unannounced disaster recovery simulation where `us-central1` traffic was failed over to `us-east4`, the MIG in `us-east4` failed to scale beyond its baseline count to accommodate peak load, causing service disruption. System logs reveal that compute instance creation requests were rejected due to resource limits. Which action should the Lead Cloud Architect take to ensure reliable execution of the disaster recovery failover plan during a regional outage?

  1. Submit and maintain proactive requests for Compute Engine vCPU and instance quota increases in the target disaster recovery region (`us-east4`) to match peak production capacity demands.Cevap
  2. B
    Migrate the backend database from Cloud SQL to Cloud Spanner so compute vCPU quotas are automatically increased across secondary regions during a failover event.
  3. C
    Replace the existing HA VPN hybrid connectivity with a Dedicated Interconnect to bypass regional Compute Engine quota restrictions during emergency failovers.
  4. D
    Configure transitive routing across peered VPC networks to pool and share Compute Engine vCPU quotas between `us-central1` and `us-east4`.

Cevap

Proactively requesting and securing vCPU and instance quota increases in the target disaster recovery region ensures the hot standby compute infrastructure can scale to handle production traffic during regional failover.
The correct response addresses the root cause of the failover failure. Compute Engine quotas in Google Cloud are region-specific. When executing disaster recovery in a secondary region, autoscale actions will fail if the requested vCPU or instance counts exceed the granted regional quota. Proactively requesting quota increases in the secondary region ensures sufficient headroom for peak production workloads.

Adım Adım Çözüm

1
Analyze failure symptoms from DR exercise logs
Identified that Compute Engine instance creation failed in region `us-east4` due to hitting regional vCPU quota limits.
GCP resource quotas are enforced per region, and default quota levels in a secondary region may not accommodate peak failover scale.
2
Evaluate potential solutions against GCP resource management behavior
Confirmed that quota increases must be explicitly requested and granted per project and per region prior to executing failover events.
Quota allocation is an administrative control plane setting independent of network layout, database engine, or interconnect choice.
3
Formulate preventative DR execution strategy
Request adequate quota headroom in `us-east4` to match `us-central1` peak load requirements.
Pre-provisioning quota prevents deployment bottlenecks during critical regional failovers.

Anahtar Kavram

Disaster Recovery Capacity Planning and Regional Quota Management
Bu soruyu puanla

Konular

Disaster Recovery and Business Continuity Execution

Bu konudan daha fazla soru