Examkin

Soru

Zorluk: ZorDeveloping Procedures for Business Continuity and Disaster Recovery Validation

A global media streaming company operates an interactive video-on-demand platform on Google Cloud. The primary architecture runs in us-central1, with a secondary disaster recovery (DR) environment prepared in us-east4. The business defines a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 15 minutes. To comply with regulatory audits, the company must execute monthly disaster recovery validation procedures without disrupting live user streams or risking data corruption in production. Which validation procedure should the Cloud Architect implement to satisfy these business continuity requirements?

  1. Automate a non-disruptive DR validation workflow using Cloud Workflows that pre-verifies regional Compute Engine quota allocations and capacity reservations in us-east4, checks Cloud SQL cross-region read replica replication lag against the 5-minute RPO threshold, promotes a temporary database clone in an isolated VPC network for integration testing, and tears down test infrastructure upon completion.Cevap
  2. B
    Execute an unannounced failover simulation during peak traffic hours by updating Cloud DNS weighted routing to direct 100% of incoming production traffic to us-east4, relying on GKE Horizontal Pod Autoscaling to request and scale Compute Engine regional quota automatically upon traffic ingress.
  3. C
    Schedule a weekly DR validation procedure that takes a cold snapshot of the primary database in us-central1, transfers the snapshot to Cloud Storage in us-east4, and restores it to a new database instance to verify database consistency.
  4. D
    Reconfigure primary database replication to stream transactions over an unencrypted HA VPN connection to us-east4, and perform DR validation by terminating the primary database master instance in us-central1 to trigger automated master election.

Cevap

The optimal validation procedure is to automate a non-disruptive DR validation workflow that pre-verifies regional quotas and capacity reservations, monitors replication lag, tests failover in an isolated VPC network using temporary database clones, and cleans up resources without altering production Cloud DNS records.
The correct option outlines a comprehensive, non-disruptive DR testing procedure. Pre-verifying quotas and reservations guarantees resource availability, monitoring replication lag satisfies the 5-minute RPO, and running validation in an isolated VPC subnet ensures production traffic in us-central1 remains completely unaffected.

Adım Adım Çözüm

1
Pre-verify capacity and resource quota
Ensures the secondary region (us-east4) has adequate Compute Engine CPU, RAM, and IP quota allocations to host the full production workload during failover.
Prevents failover failure caused by unexpected regional quota limits during an actual disaster.
2
Validate data replication health against RPO constraints
Confirms that cross-region database replication lag remains well below the strict 5-minute RPO threshold.
Ensures minimal data loss before initiating any failover processes.
3
Perform isolated sandbox validation
Promotes a temporary point-in-time database clone in an isolated VPC network in us-east4 and runs automated integration test suites without updating live Cloud DNS records.
Validates application functionality and data integrity end-to-end without affecting active production user sessions in us-central1.
4
Automate tear-down and cleanup
Deletes temporary test resources and resets test state post-validation.
Controls operational infrastructure costs while keeping validation procedures fully automated and repeatable.

Anahtar Kavram

Business Continuity and Disaster Recovery Validation Procedures
Bu soruyu puanla

Konular

Developing Procedures for Business Continuity and Disaster Recovery Validation