Examkin

Soru

Zorluk: OrtaDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A global supply chain management platform runs its core transactional fulfillment service on Compute Engine Managed Instance Groups (MIGs) and Cloud SQL for PostgreSQL in us-central1 as the primary region, with a cross-region read replica in us-east4 for disaster recovery. To meet compliance standards, the organization must regularly validate its business continuity and disaster recovery (DR) procedures. The business requires a Recovery Point Objective (RPO) of under 1 minute, a Recovery Time Objective (RTO) of under 15 minutes, and zero disruption to live customer traffic during validation drills. Which validation procedure should the Cloud Architect implement?

  1. A
    Reconfigure the disaster recovery procedure to rely on nightly Cloud Storage database backups, and validate recovery by restoring the latest database snapshot to cold-standby Compute Engine instances in us-east4 during the drill.
  2. Pre-verify compute and IP quota allocations in us-east4, promote a temporary isolated clone of the us-east4 read replica to test data integrity against recent transactions, and simulate application load against the cloned environment without switching live DNS records.Cevap
  3. C
    Initiate a full live DNS cutover to us-east4 during peak operational hours without prior quota verification, relying on MIG auto-scaling policy defaults in us-east4 to automatically request necessary compute quota increases during failover.
  4. D
    Migrate the primary relational database to a single-region Cloud Spanner instance in us-central1 with asynchronous exports to Cloud Storage in us-east4, validating recovery by importing backup files into a newly created Spanner instance during the drill.

Cevap

Pre-verify compute and IP quota allocations in us-east4, promote a temporary isolated clone of the us-east4 read replica to test data integrity against recent transactions, and simulate application load against the cloned environment without switching live DNS records.
The optimal DR validation procedure verifies regional quotas in advance to avoid capacity errors during failover and uses isolated database cloning to validate data replication integrity and RTO boot times without disrupting live production users or breaking continuous replication.

Adım Adım Çözüm

1
Assess quota and resource capacity in the target disaster recovery region (us-east4).
Ensures that Compute Engine CPU, memory, and IP quotas can accommodate production failover scale prior to running DR drills.
Quota requests require approval and cannot be dynamically increased during an emergency or failover drill.
2
Create an isolated clone of the secondary Cloud SQL read replica.
Produces a point-in-time test database with near-zero replication lag while keeping the active cross-region replication stream uninterrupted.
Cloning avoids impacting the primary database or breaking the continuous sync required for sub-minute RPO.
3
Execute functional validation and synthetic load tests on the cloned DR environment.
Verifies data integrity, RPO synchronization, and RTO application boot times without shifting live production DNS traffic.
Satisfies compliance validation requirements with zero operational downtime for end users.

Anahtar Kavram

Disaster Recovery Validation and Pre-Failover Capacity Verification
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation