Examkin

Soru

Zorluk: OrtaDisaster Recovery and Business Continuity Execution

A smart building automation company processes real-time telemetry from thousands of commercial IoT gateways. The application runs in Google Cloud with primary compute and data resources deployed in region `us-central1`, and a Warm Standby disaster recovery (DR) setup configured in region `us-east4`. The company specifies a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. During an unannounced disaster recovery failover drill of `us-central1`, the operational team promoted the secondary database replica, but the DR secondary Managed Instance Group (MIG) in `us-east4` failed to scale out to accommodate production traffic due to compute capacity errors. Which architectural modification should the Cloud Architect implement to ensure seamless disaster recovery execution?

  1. Proactively request and maintain sufficient Compute Engine regional resource quotas in `us-east4` to match primary production peak requirements.Cevap
  2. B
    Migrate the underlying relational data tier from Cloud SQL to Cloud Spanner to handle automatic scaling of Compute Engine microservices during failover.
  3. C
    Configure the automated DR failover script to submit an API request for an emergency Compute Engine quota increase immediately after a regional outage is detected.
  4. D
    Establish a VPC Network Peering mesh between `us-central1`, `us-east4`, and a transit VPC to transitively route DR traffic to active compute instances in `us-west1`.

Cevap

Proactively request and maintain sufficient Compute Engine regional resource quotas in `us-east4` to match primary production peak requirements.
When executing a disaster recovery failover to a secondary region, compute resource quotas must be requested and maintained in advance. If quotas are not pre-allocated, Compute Engine Managed Instance Groups will fail to scale up, preventing the application from reaching operational capacity within the target Recovery Time Objective (RTO).

Adım Adım Çözüm

1
Analyze the failure mode during the regional failover drill.
Identified that compute instance provisioning failed because the target region lacked adequate vCPU or instance quotas for the scaled workload.
Managed Instance Groups cannot scale beyond the quota limits assigned to the target region.
2
Evaluate disaster recovery capacity planning principles.
Determined that regional quotas must be requested and approved in advance of any operational incident.
Quota increases require evaluation and cannot be guaranteed instantly during an emergency.
3
Select the correct mitigation strategy to meet the 15-minute RTO requirement.
Maintaining pre-approved quotas in the secondary DR region ensures immediate scale-out capability during failover.
Pre-allocated quotas eliminate provisioning blocks and fulfill strict RTO constraints.

Anahtar Kavram

Disaster Recovery Capacity Planning and Regional Quotas
Bu soruyu puanla

Konular

Disaster Recovery and Business Continuity Execution

Bu konudan daha fazla soru