An enterprise online gaming platform processes real-time multiplayer state and inventory data on Google Cloud, operating primarily out of us-east4 with a disaster recovery (DR) standby target in us-west1. The business mandates a Recovery Point Objective (RPO) of less than 5 seconds and a Recovery Time Objective (RTO) of less than 15 minutes. The lead cloud architect is establishing a validation procedure for bi-annual DR drills to confirm operational readiness and failover execution without disrupting live production traffic. Which of the following procedural steps must be included in the DR validation framework to satisfy these business continuity requirements? (Select TWO.)
- Perform pre-drill verification of regional resource quotas and capacity reservations in us-west1, coupled with synthetic traffic generation against isolated DR staging endpoints to validate RTO bounds.Answer
- BRely on managed instance group (MIG) autoscaling rules in us-west1 during failover execution to dynamically request and provision higher regional vCPU quota as live traffic arrives.
- Implement continuous automated validation of database replication lag metrics between regions, verifying that the replication delta stays below 5 seconds prior to initiating failover simulation.Answer
- DReconfigure the secondary region database to hydrate from hourly Cloud Storage backups during the validation drill to lower continuous inter-region replication overhead while maintaining the RPO target.
Answer
The validation framework must include pre-drill verification of regional quota limits and capacity in the standby region alongside synthetic traffic testing against isolated endpoints, as well as continuous automated monitoring of database replication lag metrics to verify compliance with the RPO target.
To validate a DR strategy against an RPO < 5 seconds and RTO < 15 minutes without disrupting production, architects must ensure standby infrastructure quotas are pre-approved and perform synthetic load tests on isolated secondary endpoints. Furthermore, verifying that cross-region database replication lag remains consistently below 5 seconds validates that RPO targets are satisfied before failover is initiated.
Step-by-Step Solution
Key Concept
Disaster Recovery Validation and RPO/RTO Capacity Planning