Home › AWS SysOps Associate › cloudcomputing › sysopsmonitoring › A team needs disaster recovery with an RTO ≤ 15 …
A team needs disaster recovery with an RTO ≤ 15 minutes and RPO ≤ 5 minutes across two AWS Regions. Which strategy fits?
ABackup-and-restore using snapshots once a week with manual recovery
BWarm-standby multi-Region: scaled-down active stack in the secondary Region with continuous cross-Region replication (Aurora Global, S3 CRR, DynamoDB Global Tables)
CMigrating everything to AWS Snowball appliances
DSingle-AZ deployment with no multi-Region copies
Answer & Solution
Correct answer: B. Warm-standby multi-Region: scaled-down active stack in the secondary Region with continuous cross-Region replication (Aurora Global, S3 CRR, DynamoDB Global Tables)
Warm-standby provides minute-scale RTO/RPO with continuous replication and pre-provisioned (small) capacity ready to scale up. The other options have higher RTO/RPO or aren't DR strategies.
Related questions
An EC2 Auto Scaling group is set to launch from an AMI baked weekly. After the latest AMI Which service detects unexpected drift between an AWS resource's actual configuration and A multi-AZ RDS deployment for a write-heavy database experiences a primary AZ failure. WhaWhich automation pattern is BEST for self-healing a stuck EC2 instance — for example, restAn RDS database needs point-in-time-restore for 14 days plus a guaranteed daily backup. WhAn EC2 instance's CPU steady-state is fine but bursts to 100% during scheduled jobs. The tWhich Route 53 routing policy is used to fail traffic over from a primary endpoint to a stAn EC2 fleet behind an ALB needs to scale out when average CPU goes above 70% for 5 minute