Examkin

Question

Difficulty: HardDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A global enterprise operates a high-throughput financial transactions processing platform on Google Cloud with a primary deployment in region us-east4 and a designated disaster recovery (DR) site in us-west1. The database layer utilizes Cloud SQL cross-region read replicas, while microservices run on Google Kubernetes Engine (GKE). The organization is finalizing standard operating procedures for periodic, non-disruptive DR validation drills designed to verify an RTO of 1 hour and an RPO of 5 minutes. Which TWO procedures must the cloud architect include in the DR validation execution plan to ensure accurate validation without disrupting active production operations or causing drill failures? (Select 2 answers.)

  1. Submit regional resource quota increase requests for GKE compute nodes and IP addresses in the secondary region (us-west1) well before executing the validation drill.Answer
  2. Perform validation testing against a isolated clone or point-in-time recovery (PITR) instance derived from the secondary database, preserving continuous cross-region replication from production.Answer
  3. C
    Promote the live Cloud SQL secondary read replica to a standalone primary database instance during the non-disruptive test window, then re-establish replication manually back to us-east4.
  4. D
    Reroute multi-gigabit database synchronization traffic temporarily over standard Cloud VPN tunnels to validate cross-region bandwidth limits under failover conditions.

Answer

The correct procedures are to request regional compute/network quota increases in the secondary region prior to the drill and to perform database validation against a cloned or point-in-time recovery copy rather than promoting the live production cross-region replica.
To execute a non-disruptive disaster recovery drill, organizations must ensure the secondary region has adequate quota to host production workloads by requesting quota increases prior to the test. Additionally, to avoid disrupting production database replication streams, testing must occur on isolated database snapshots or cloned instances rather than promoting the active replica.

Step-by-Step Solution

1
Analyze capacity requirements in the target DR region.
Identified potential quota bottlenecks in GKE compute resources and networking in us-west1 during full workload deployment.
Default quotas in secondary regions may not match primary production scale, leading to provisioning errors during failover testing.
2
Evaluate database validation strategies for non-disruptive testing.
Selected creating a database clone or point-in-time recovery copy in us-west1.
Promoting a live cross-region replica disconnects it from the primary instance, severing continuous data replication and violating production RPO requirements.
3
Verify overall DR validation procedure compliance against RTO and RPO goals.
Confirmed that pre-provisioning quota and isolating test data fulfills both seamless failover verification and production stability.
Allows thorough validation of failover automation while keeping production environment fully operational and protected.

Key Concept

Developing non-disruptive Business Continuity and Disaster Recovery (BCP/DR) validation procedures on Google Cloud requires pre-verifying regional capacity/quotas and maintaining continuous production replication by conducting tests on cloned isolated environments.
Estimated Time:2m 30s
Rate this question

Topics

Developing Procedures for Business Continuity and Disaster Recovery Validation