Examkin

Question

Difficulty: HardDisaster Recovery and Business Continuity Execution

An enterprise IoT telemetry platform processes high-throughput fleet analytics across Google Cloud. The primary workload runs in `us-central1`, while a secondary disaster recovery environment is staged in `us-east4`. The application tier uses Compute Engine Managed Instance Groups (MIGs) served by a Global External Application Load Balancer, and backend services rely on private inter-VPC communication and dedicated hybrid links to on-premises datacenters. During a complete outage in `us-central1`, the incident response team must execute the disaster recovery failover runbook to restore full operational capacity in `us-east4` within a strict RTO. Which of the following execution steps must the operations team perform to successfully execute this regional failover? (Select TWO.)

  1. Verify regional compute resource quotas in `us-east4` and request quota increases in advance if required capacity exceeds current limits prior to scaling up target Managed Instance Groups.Answer
  2. B
    Rely on the existing VPC Network Peering connection between the central hub VPC and `us-central1` to transitively forward failover traffic from `us-east4` to on-premises resources.
  3. Update Cloud DNS routing policies or Load Balancer backend service configurations to direct incoming application traffic exclusively to the healthy MIG backends in `us-east4`.Answer
  4. D
    Provision an emergency Cloud High Availability (HA) VPN connection during failover execution to handle sustained 20 Gbps cross-region database replication streams previously transported over Dedicated Interconnect.

Answer

The correct execution steps are verifying and securing necessary regional vCPU and resource quotas in the failover region (`us-east4`) prior to scaling up backend workloads, and updating ingress traffic routing (via Cloud DNS policies or Load Balancer backend configurations) to direct application traffic to the active failover infrastructure.
Executing a successful regional disaster recovery failover requires both infrastructure readiness and traffic redirection. First, regional compute resource quotas in the failover region must be verified and expanded in advance so that scaling up Managed Instance Groups does not fail due to API quota limits. Second, once failover instances are active, ingress routing mechanisms such as Global Load Balancer backend service definitions or Cloud DNS failover routing policies must be updated to route live application traffic to the failover region.

Step-by-Step Solution

1
Evaluate Regional Resource Quotas
Ensure target compute capacity in `us-east4` can expand to support full operational load without encountering `QUOTA_EXCEEDED` API errors during MIG scale-up.
Google Cloud quotas are enforced regionally. Attempting a rapid failover scale-up without sufficient quota reserved or pre-approved will cause instance creation failures.
2
Perform Ingress Traffic Cutover
Update Load Balancer backend instance groups or Cloud DNS failover routing records to direct all user requests to the operational MIGs in `us-east4`.
Traffic must be explicitly redirected away from the impacted primary region (`us-central1`) to complete operational recovery.

Key Concept

Disaster Recovery Execution and Regional Failover Validation
Rate this question

Topics

Disaster Recovery and Business Continuity Execution

More questions from this topic