A cloud architect is establishing a standard operating procedure for validating disaster recovery (DR) failover of a mission-critical workload from a primary GCP region to a secondary target region. What is the correct sequence of steps to safely execute and validate this DR drill without impacting live production systems?
- 1Audit target region quota limits and request necessary regional CPU and storage quota increases to match production requirements.
- 2Create isolated point-in-time storage clones of the secondary database replicas to establish an isolated testing boundary.
- 3Provision application instances in the DR region using Infrastructure as Code templates configured to point to the isolated database clones.
- 4Execute automated synthetic test suites against the DR application endpoints to measure RTO and verify data consistency.
- 5Deprovision the test compute instances and delete the temporary database clones to clean up resources and log validation metrics.
Cevap
The correct sequence begins with auditing regional resource quotas, followed by creating isolated database clones, provisioning compute infrastructure via IaC, running synthetic validation tests, and concluding with environment teardown and metric logging.
Validating a DR environment safely requires a structured sequence: first ensuring GCP resource quotas in the target region are sufficient, isolating test data via point-in-time database cloning, deploying compute infrastructure via automated IaC templates, conducting synthetic transaction testing to verify RTO/RPO metrics, and finally cleaning up test resources while recording compliance results.
Adım Adım Çözüm
Anahtar Kavram
Disaster Recovery Validation Procedures
Tahmini Süre:1m 30s