Examkin

Question

Difficulty: MediumDisaster Recovery and Business Continuity Execution

A online gaming studio runs its real-time multiplayer backend in region `us-west1` (primary) and maintains a pilot light disaster recovery (DR) setup in region `us-east1`. During a simulated regional disaster recovery test, the team successfully promotes the cross-region database replica in `us-east1`. However, when the automated scaling scripts attempt to rapidly scale up the Managed Instance Groups (MIGs) in `us-east1` to handle the full production load, instance creation fails due to exceeding regional CPU limits (`QUOTA_EXCEEDED`). Which operational measure should the cloud architect implement to ensure reliable business continuity and failover execution?

  1. Proactively request and maintain sufficient compute resource quotas in the secondary region (`us-east1`) to cover full production capacity prior to initiating any DR failover.Answer
  2. B
    Configure an automated script within the failover pipeline to request an emergency quota increase via the Cloud Quotas API immediately after promoting the database.
  3. C
    Reconfigure the DR strategy to use cold snapshot restoration from Cloud Storage instead of pre-provisioning pilot light resources to bypass quota limits.
  4. D
    Establish VPC Network Peering between `us-west1` and `us-east1` so compute quotas from the primary region transfer transitively to the DR region.

Answer

Proactively request and maintain sufficient compute resource quotas in the secondary region (`us-east1`) to cover full production capacity prior to initiating any DR failover.
Ensuring operational reliability during a Disaster Recovery (DR) failover requires proactive capacity and quota planning. Because GCP quotas are enforced independently per region and project, a warm standby or pilot light architecture will fail to scale during a regional outage if the secondary region's compute quota is insufficient. Securing compute quota limits in advance ensures that scaling scripts can launch required instances immediately without encountering `QUOTA_EXCEEDED` errors.

Step-by-Step Solution

1
Identify the root cause of the DR failover failure.
The failover failed because the target DR region (`us-east1`) did not have adequate compute CPU quota requested in advance to accommodate full production instance scaling.
GCP enforces resource quotas on a per-region, per-project basis independently of active production workloads.
2
Evaluate operational requirements for disaster recovery execution.
To achieve target RTO during a pilot light failover, compute resources must be able to scale up instantly without reaching administrative quota caps.
Quota increases require evaluation and cannot be relied upon in real time during an active regional incident.
3
Select the correct mitigation practice.
Request regional quota increases in advance so that the target DR region's quota limits accommodate peak production capacity.
Pre-approved quota ensures seamless compute expansion during DR execution.

Key Concept

Disaster Recovery Quota Planning and Execution Reliability
Rate this question

Topics

Disaster Recovery and Business Continuity Execution

More questions from this topic