An enterprise operations team is establishing a disaster recovery (DR) validation procedure for a mission-critical service on Google Cloud. Which TWO procedures should be included in the validation plan to ensure successful DR testing without causing production downtime or data corruption?
- Pre-verify and request necessary Google Cloud compute and storage resource quotas in the target DR region prior to executing the failover drill.Answer
- BUse a cold-standby restore strategy from daily backups for real-time transactional databases requiring near-zero Recovery Point Objective (RPO).
- Execute failover verification scripts against isolated database snapshots or non-production replicas rather than mutating primary production data.Answer
- DMigrate all global database workloads to standard Cloud SQL instances instead of Cloud Spanner to simplify regional failover testing.
Answer
The DR validation plan should include pre-verifying resource quotas in the target failover region and testing against isolated database snapshots.
Verifying resource quotas in the target DR region prior to testing prevents unexpected provisioning failures due to regional limits during failover. Performing DR validation against isolated snapshots or replicas protects production data from accidental modification during testing.
Step-by-Step Solution
Key Concept
Developing Procedures for Business Continuity and Disaster Recovery Validation