An online media streaming platform hosts its user entitlement system on Google Cloud across a primary region (us-central1) and a secondary failover region (us-east4). The cloud architecture team is updating their quarterly Disaster Recovery (DR) and Business Continuity Plan (BCP) validation procedures to ensure regional failover readiness without causing production disruptions. Which procedures should be included in the DR validation workflow to accurately validate failover preparedness and maintain compliance with recovery objectives? (Select TWO options.)
- Pre-verify regional Compute Engine resource quotas and request necessary quota increases in the target failover region prior to executing the failover drill.Cevap
- Perform automated data integrity verification and sequence checks on database replicas immediately after redirecting traffic to validate Recovery Point Objective (RPO) compliance.Cevap
- CTransition the multi-region database architecture to rely on asynchronous nightly exports to Cloud Storage during DR validation to test backup-and-restore failover speed.
- DReroute failover validation traffic over a temporary single HA VPN tunnel instead of existing Dedicated Interconnect links to simulate emergency network bandwidth throttling.
Cevap
The correct procedures are pre-verifying regional resource quotas in the target failover region prior to the drill and performing automated data integrity checks on database replicas immediately after rerouting traffic.
Comprehensive DR validation requires verifying infrastructure provisioning capacity beforehand and validating data consistency after traffic shift. Requesting regional Compute Engine quota increases prior to the drill ensures that target regions can accommodate incoming workloads. Performing automated data integrity checks right after shifting traffic verifies that database replication met RPO objectives without data loss.
Adım Adım Çözüm
Anahtar Kavram
Disaster Recovery Validation and Capacity Preparedness