Exam AWS Certified Solutions Architect - Professional topic 1 question 702 discussion

My pick would be A. https://docs.aws.amazon.com/aws-backup/latest/devguide/cross-region-backup.html C and D don't really make sense to me. EC2 image builder is for deploying an creating new AMIs. Glue is for data integration. With B I am not sure how drift detection would help as that would just allow a rollback and is not geared towards backup. Also A seemed to be the only one that addressed backing up the web and app servers along with RDS.

Answer CANNOT be A, deploying a brand new RDS instance will take >30 minutes. You will use EC2 Image builder to put the AMIs into the new region, but not use image builder to LAUNCH them. To me the answer is clearly C.

https://aws.amazon.com/blogs/storage/point-in-time-recovery-and-continuous-backup-for-amazon-rds-with-aws-backup/ - this link supports A.

Answer is C and can't be A. RPO is just 5 minutes means the time span between the latest backup timestamp and the crash timestamp is 5 minutes. when you do AWS Backup, it usually takes more than 1 hour. Clearly you need read replica or global database.

RPO of 5 mnutes requires an warm stndy or pilot light environment. Id say C is the only option here

I'll go with C https://aws.amazon.com/blogs/storage/point-in-time-recovery-and-continuous-backup-for-amazon-rds-with-aws-backup/

RTO is not provided hence we are covered with option A

This article describes continuous backup for RDS (not Aurora, not EC2, just RDS) with AWS backup (RPO under 5 min), which means that backups of all servers every 5 minutes is NOT possible, only RDS can be handled, I think I will have to go with C: https://aws.amazon.com/blogs/storage/point-in-time-recovery-and-continuous-backup-for-amazon-rds-with-aws-backup/

Between A and C... I go for C ... Time to restore the data will take times.. and having AWS CloudFormation also take time to rebuilt the infras.... all within 5 minutes is questionable. On C, AMI, and Database are already in place on DR site. Just need to activite the failover to make the DR become production.. All this can happen in 5 mins... Thus my pick i C.

C is Correct; Note that we have aggressive RPO. Now, Disaster Strategy - Cold DR (Backup & Restore) vs Hot DR (active to active); due to aggressive RPO => Replication (Hot DR) Article on DR for RDS (though it has SQL server instead of MySQL; concept remains same) - To meet very aggressive RPO and RTO requirements, your DR strategy needs to consider continuous replication capability https://aws.amazon.com/blogs/database/cross-region-disaster-recovery-of-amazon-rds-for-sql-server/

Because RPO is 5 minutes, not RTO.

Should be C https://aws.amazon.com/image-builder/faqs/#:~:text=Image%20Builder%20can%20copy%20AMIs%20to%20selected%20AWS%20regions%20using%20existing%20AMI%20sharing%20mechanisms.%20The%20distribution%20can%20be%20gated%20on%20the%20passing%20of%20tests%20with%20Image%20Builder. If A, it should be included Point-In-Time Recovery https://docs.aws.amazon.com/aws-backup/latest/devguide/point-in-time-recovery.html

I support A, a simple require that need 5 mins of RPO (Not RTO). A meet the requirement with least complexity. Although C would work but it have higher cost when you have active-active model which is not require in the question, I prefer the simpler solution

A is correct here, promoting RDS Mysql read replica as primary needs to be done manually and also RDS instance has to be rebooted.. this will not meet 5 minutes RPO

Agree with hbrand

A is not feasible because of 5 min restore time. Restore point objective less than 5 min, the limit for aws backup way more than that. The only way to achieve it is with a read replica.

It's C.