Examkin

Soru

Zorluk: ZorDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An enterprise media streaming provider is executing a scheduled, non-disruptive disaster recovery (DR) validation procedure for its mission-critical workload hosted on Google Cloud. The application relies on Cloud Spanner for globally consistent state storage, Compute Engine Managed Instance Groups (MIGs) deployed across primary (`us-central1`) and failover (`us-east4`) regions, and Cloud DNS for global traffic routing. To ensure business continuity and satisfy compliance mandates without risking primary production operations, in what sequence should the cloud operations team execute the DR validation procedure steps?

  1. 1Verify regional compute quotas and request limit increases in the target failover region (`us-east4`) prior to running failover scripts.
  2. 2Validate Cloud Spanner cross-region replication latency metrics and transaction log synchronization to confirm compliance with target Recovery Point Objective (RPO).
  3. 3Spin up test application instances in `us-east4` in an isolated VPC network connected to Cloud Spanner read replicas for functional validation.
  4. 4Execute Cloud DNS routing policy updates to shift synthetic test traffic to `us-east4` endpoints and measure total failover duration against Recovery Time Objective (RTO).
  5. 5Revert Cloud DNS routing policy to `us-central1`, confirm primary cluster operational health, and decommission isolated DR testing resources.

Cevap

The correct execution order for DR validation is: 1) Verify regional compute quotas in the failover region, 2) Validate Cloud Spanner cross-region replication against RPO targets, 3) Deploy isolated application test instances in the failover region, 4) Update Cloud DNS routing policies to measure RTO performance, and 5) Revert Cloud DNS routing to the primary region and tear down DR test resources.
A structured DR validation procedure follows a logical sequence: pre-flight resource/quota checks, data replication and RPO validation, isolated workload instantiation, traffic redirection for RTO assessment, and final failback cleanup. Requesting quotas first ensures target capacity exists. Validating RPO metrics prevents loss of data integrity. Running isolated test workloads protects production data. Updating DNS tests routing under test conditions, and restoring DNS followed by resource teardown concludes the procedure safely.

Adım Adım Çözüm

1
Pre-verify quota availability in target DR region.
Ensures secondary region target resources can scale to match primary production demand.
Quota increases in GCP require time for approval; failing to check quota beforehand causes catastrophic scaling failures during actual or simulated failover.
2
Inspect storage replication lag and confirm RPO thresholds.
Guarantees data loss bounds remain within business limits prior to state transitions.
Cloud Spanner replication metrics must be healthy before cutting over service traffic.
3
Provision isolated test workloads in secondary region.
Validates infrastructure-as-code scripts, environment configurations, and startup scripts.
Isolation prevents test traffic from corrupting active production databases.
4
Update Cloud DNS and monitor RTO.
Measures real end-to-end failover time.
Routing updates evaluate global resolution propagation speeds against target business RTO metrics.
5
Revert traffic routing and clean up temporary test artifacts.
Restores primary baseline operation and avoids lingering resource costs.
Failback validation closes out the simulation loop safely.

Anahtar Kavram

Disaster Recovery Validation Procedures
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation