Question

Difficulty: MediumDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An enterprise digital publishing platform hosts its core services in us-central1 and maintains a secondary disaster recovery environment in us-east4 on Google Cloud. The infrastructure utilizes Compute Engine Managed Instance Groups (MIGs), Cloud SQL cross-region read replicas, and Cloud Storage. During an upcoming business continuity validation drill, the architecture team must test regional failover procedures while ensuring continuous replication remains undisturbed and preventing resource allocation failures. Which TWO validation procedures should the team include in their disaster recovery test plan? (Select TWO.)

  1. Automate pre-drill verification to ensure compute, network, and storage quotas in us-east4 are sufficient to support the full production load prior to executing failover procedures.Answer
  2. Promote an isolated clone of the secondary Cloud SQL database replica to run validation queries and synthetic transaction tests without breaking the active cross-region replication stream.Answer
  3. C
    Rely on Compute Engine regional autoscaling policies in us-east4 to dynamically request additional CPU and IP quota limits during the simulated failover drill.
  4. D
    Reconfigure the primary database replication mechanism to cold standby backups during the drill window to guarantee zero recovery point objectives.

Answer

The correct validation procedures are to verify regional resource quotas in the disaster recovery region prior to drill execution, and to test failover readiness using isolated database clones to preserve active replication streams.
Effective DR validation procedures must verify both infrastructure quota availability and data integrity without jeopardizing production operations. Pre-verifying regional resource quotas ensures that the DR target region can accommodate full production traffic during a failover event. Using a cloned database replica provides a isolated environment to execute validation tests without interrupting continuous cross-region replication or mutating production state.

Step-by-Step Solution

1
Audit pre-drill resource headroom and regional quotas in the secondary region.
Confirms that Compute Engine MIGs and network resources can scale to full operational load during failover.
GCP quota increases require advance request and approval; failure to check quotas before a drill leads to provisioning failures.
2
Create isolated database snapshot clones for synthetic drill testing.
Enables end-to-end failover validation while keeping the primary-to-secondary database replication stream intact.
Directly modifying or promoting active replicas disrupts ongoing replication and risks production data integrity.

Key Concept

Developing Procedures for Business Continuity and Disaster Recovery Validation
Rate this question