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

Question is asking for: RTO of 30 minutes and an RPO of 5 RPO RTO -> mode 24 24hr -> backup 12 4hr -> pilot light 1.4 15min -> warm standup 15min 5min -> active-active B because of above ^ D is obvious

I go with AD

Pilot light (RPO in minutes, RTO in tens of minutes): Provision a copy of your core workload infrastructure in the recovery Region. Replicate your data into the recovery Region and create backups of it there. Resources required to support data replication and backup, such as databases and object storage, are always on. Other elements such as application servers or serverless compute are not deployed, but can be created when needed with the necessary configuration and application code. https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_planning_for_recovery_disaster_recovery.html

I'll go with B and D

https://aws.amazon.com/blogs/architecture/disaster-recovery-dr-architecture-on-aws-part-iii-pilot-light-and-warm-standby/

I will go with A/D. The question highlights "optimizing costs". B - Hot standby would work but is more expensive. RTO and RPO is for data and D covers that.

Because of "The application and web layers are stateless" so dont have any data stored in EC2 Instance. If application dont have multiple deployments in a day, option A is cost effective. Cross-Region Aurora will effect to RPO/RTO and meet requirements. --> AD are best options!

C and D is right answer. A is non sense 24 hours "DAILY"

A is wrong. daily snapshot won't be enough for 30min/5min

AD, RTO & RPO only for Data tier,

AD for me B will work but it's too expensive cause you have active-active model, and the RTO and RPO within only minute, while the question say that it's can up to 30 minutes. A will work and more cost effective

B,D https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/plan-for-disaster-recovery-dr.html

I go with BD https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/plan-for-disaster-recovery-dr.html

Answer is B & D Hot Standby is the correct answer: Because, if we have fleet of EC2 Instances, which are stateless, why even we are taking snapshots. Suppost, if we have 5 instance in app later, 10 instances in BL, what is the use of taking the snapshot of the disk of App Layes which is stateless, instead of that, we can maintain thin layer of Hot Standby 1 instance in Web, 1 instance in BL behind autoscaling group with Cross Replication of Aurora, we can bring the entire layer with in few minutes by standing up the instance by Cloud Formation with the DR database: https://www.wellarchitectedlabs.com/reliability/disaster-recovery/workshop_4/ https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.html

Will go with B and D. The host standby solves the 30min RTO and the DB cross replication solves the 5min RPO

B and D as stated on Digital Cloud Training.

I'll go with A,D