Examkin

Soru

Zorluk: Çok zorDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A national smart power grid operator ingests real-time telemetry from millions of edge meters into Google Cloud across a primary region (us-central1) and a secondary disaster recovery region (us-east4). The organization must execute a scheduled business continuity validation drill to prove recovery capability without corrupting live state or exceeding target Recovery Point Objective (RPO) and Recovery Time Objective (RTO) limits. In what sequential order should the cloud architecture team execute the following procedure steps to validate regional disaster recovery failover?

  1. 1Audit compute quota limits and verify active capacity reservations in the secondary target region (us-east4).
  2. 2Perform database failover by updating Cloud Spanner regional leader assignments and verifying transactional commit state consistency.
  3. 3Update Cloud DNS routing policies and Global External Application Load Balancer backend service groups to direct live IoT traffic to us-east4.
  4. 4Execute synthetic telemetry validation tests to measure end-to-end processing latencies and verify compliance with RTO and RPO metrics.
  5. 5Re-establish cross-region database replication back to us-central1 and verify sync state to prepare for failback.

Cevap

The correct operational sequence begins with pre-drill quota and capacity reservation validation in the target region, followed by database state transition and integrity verification, then live traffic redirection via Cloud DNS and Global Load Balancing, followed by synthetic workload testing for RPO/RTO validation, and concludes with restoring cross-region database replication back to the primary region.
Disaster recovery validation requires a strict dependency order: verifying infrastructure capacity prerequisites (quota and reservations), transitioning the persistent state layer (database failover), shifting network ingress routing (DNS and load balancing), validating application health against RPO/RTO metrics using synthetic tests, and finally re-establishing reverse data replication to guarantee ongoing business continuity.

Adım Adım Çözüm

1
Pre-drill infrastructure audit
Ensures us-east4 has sufficient quota and reserved compute instances ready to launch.
Failing to check quota prior to failover can lead to instance launch failures during peak load migration.
2
Database failover and data integrity check
Transitions database write leadership to us-east4 and confirms zero data loss.
Data persistence integrity must be guaranteed before live network traffic is allowed to write to the secondary location.
3
Network traffic steering transition
Switches ingress endpoints and DNS records to target us-east4 services.
Routing live client connections to an unready or non-primary database destination will cause system outages.
4
RPO/RTO validation and synthetic testing
Verifies that service performance and data integrity meet business continuity objectives.
Validation drills require explicit verification against business SLOs while operating in the secondary region.
5
Replication re-establishment and stabilization
Restores bidirectional or target-to-primary data sync for failback readiness.
A secondary region operating without an active replication target invalidates high availability post-failover.

Anahtar Kavram

Disaster Recovery Validation Procedures and Operational Execution Order
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation