Examkin

Question

Difficulty: MediumDeveloping Procedures for Business Continuity and Disaster Recovery Validation

An enterprise operates a real-time connected vehicle telemetry ingestion platform on Google Cloud. The core architecture uses Google Kubernetes Engine (GKE) and Cloud Spanner deployed in a primary region (us-central1). The organization requires quarterly Disaster Recovery (DR) validation to ensure failover capability to a secondary region (us-east4) under a strict Recovery Point Objective (RPO) of less than 5 seconds and a Recovery Time Objective (RTO) of less than 15 minutes. The validation procedure must not disrupt active production traffic in us-central1. Which procedure should the cloud architect mandate to validate DR readiness effectively?

  1. Pre-request and continuously audit compute and database quotas in us-east4, deploy non-production workload pipelines via automated IaC templates into an isolated testing VPC in us-east4, and perform synthetic workload testing against a regional database clone.Answer
  2. B
    Implement a cold-standby strategy in us-east4 relying on scheduled hourly Cloud Storage database export files, and validate DR readiness by restoring disk snapshots and database dumps into us-east4 during the quarterly test window.
  3. C
    Initiate a full live production DNS failover during peak telemetry ingestion hours to route live vehicle traffic into us-east4 without prior verification of regional GKE core quotas in us-east4.
  4. D
    Replace Cloud Spanner with a single-zone Cloud SQL instance in us-central1 paired with an asynchronous cross-region read replica in us-east4 to streamline the database failover validation process.

Answer

Pre-request and continuously audit compute and database quotas in us-east4, deploy non-production workload pipelines via automated IaC templates into an isolated testing VPC in us-east4, and perform synthetic workload testing against a regional database clone.
The correct procedure mandates checking resource quotas in the secondary region ahead of time, using automated Infrastructure as Code to deploy validation infrastructure into an isolated VPC, and performing synthetic testing against database clones. This guarantees DR operational readiness without causing downtime or risk to live production telemetry pipelines.

Step-by-Step Solution

1
Evaluate RPO and RTO constraints against potential DR validation strategies.
Near-zero RPO (< 5 seconds) and low RTO (< 15 minutes) require warm/active-passive or multi-region replication rather than cold backup/restore mechanisms.
Cold backup restores take hours and result in significant data loss windows that violate the required metrics.
2
Ensure target region resource availability prior to failover drills.
Audit regional CPU, IP address, and GKE quotas in us-east4 to ensure the region can absorb full production workloads immediately.
Unrequested quota limits in secondary regions are a primary root cause of DR failover failures.
3
Validate failover execution safely without impacting active production users.
Provision isolated environments using IaC scripts and run synthetic data validation tests against a cloned dataset.
Using isolated testing environments prevents accidental corruption or disruption of production vehicle telemetry traffic.

Key Concept

Developing Procedures for Business Continuity and Disaster Recovery Validation
Rate this question

Topics

Developing Procedures for Business Continuity and Disaster Recovery Validation