Question

Difficulty: MediumDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An enterprise logistics company runs a real-time fleet tracking service on Google Cloud. The workload uses a primary Compute Engine Managed Instance Group (MIG) in us-central1 and a secondary MIG in us-east4, with persistent state maintained via Cloud SQL cross-region read replicas. The organization is designing a quarterly Disaster Recovery (DR) validation procedure to verify a Recovery Time Objective (RTO) of 30 minutes and a Recovery Point Objective (RPO) of under 1 minute without disrupting live production traffic. Which TWO procedures must be included in the DR test execution plan to ensure accurate validation? (Select TWO answers.)

  1. Pre-verify that regional compute and database resource quotas in the secondary region (us-east4) are sufficient to sustain full production load prior to executing the failover drill.Answer
  2. Promote a dedicated test cross-region Cloud SQL read replica in us-east4 to a standalone database instance and perform automated consistency checks in an isolated VPC network.Answer
  3. C
    Schedule daily automated Cloud SQL database exports to Cloud Storage and restore them into us-east4 during the failover drill to test baseline database recovery.
  4. D
    Configure Compute Engine autoscaling policies to request regional CPU quota increases dynamically if instance creation fails during failover testing.

Answer

The DR validation plan must include pre-verifying regional resource quotas in the failover target region prior to testing, and promoting a dedicated test cross-region read replica in an isolated network to validate data consistency.
Validating disaster recovery readiness requires verifying target regional quotas in advance to prevent capacity provisioning failures during a test or real outage. Additionally, promoting a dedicated test read replica within an isolated environment validates data consistency and promotion procedures without disrupting the primary database or active replication pipeline.

Step-by-Step Solution

1
Analyze database replication options against the RPO target of under 1 minute.
Daily backup exports yield an RPO of up to 24 hours. Continuous cross-region replication must be validated using an isolated test replica promotion.
Sub-minute RPO requires testing live replication channels rather than periodic file backups.
2
Evaluate regional compute capacity and operational constraints in the failover region.
Quota increases must be pre-approved because request evaluation by Cloud Operations is not instantaneous.
Quota limits enforced during failover testing will cause VM creation failures, breaching the 30-minute RTO.

Key Concept

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