A smart utility company operates a real-time smart grid monitoring platform on Google Cloud. The architecture uses a GKE cluster and a multi-region Cloud Bigtable instance deployed across a primary region (us-east4) and a secondary DR region (us-west1) to support a strict Recovery Point Objective (RPO) of under 1 minute and a Recovery Time Objective (RTO) of under 15 minutes. The team is developing an automated Disaster Recovery (DR) validation procedure to periodically test failover capabilities without disrupting active operations. Which two procedures should the cloud architect include in the DR validation workflow? (Select TWO.)
- Audit regional resource quota limits in us-west1 and pre-request necessary quota increases well in advance of scheduled failover simulations.Cevap
- BDefer checking target region resource quotas until after initiating failover execution to observe real-time dynamic quota limits under stress.
- Run automated synthetic transaction tests against the replicated secondary data store and compute pods before shifting production DNS traffic.Cevap
- DTemporarily replace continuous multi-region database replication with scheduled daily batch backups to lower cross-region network transfer costs during testing.
Cevap
The DR validation procedure must include auditing regional resource quotas in the target region prior to failover testing, as well as executing synthetic validation tests on the secondary cluster before switching live traffic.
Validating DR readiness requires both proactive infrastructure checks and post-failover, pre-traffic verification. Pre-requesting and auditing resource quotas ensures the secondary region has sufficient capacity to handle failover scale. Executing synthetic transaction tests verifies system health and data consistency in the secondary region before updating DNS or traffic routing.
Adım Adım Çözüm
Anahtar Kavram
Disaster Recovery Validation and Pre-Failover Readiness Procedures