SAP-C02 · Question #470
A company needs to build a disaster recovery (DR) solution for its ecommerce website. The web application is hosted on a fleet of t3.large Amazon EC2 instances and uses an Amazon RDS for MySQL DB…
The correct answer is B. Use infrastructure as code (IaC) to provision the new infrastructure in the DR Region. Create a. The company needs a cost-effective disaster recovery solution for an e-commerce website (EC2 fleet in ASG, RDS MySQL) with an RPO of 30 seconds and an RTO of 10 minutes.
Question
A company needs to build a disaster recovery (DR) solution for its ecommerce website. The web application is hosted on a fleet of t3.large Amazon EC2 instances and uses an Amazon RDS for MySQL DB instance. The EC2 instances are in an Auto Scaling group that extends across multiple Availability Zones. In the event of a disaster, the web application must fail over to the secondary environment with an RPO of 30 seconds and an RTO of 10 minutes. Which solution will meet these requirements MOST cost-effectively?
Options
- AUse infrastructure as code (IaC) to provision the new infrastructure in the DR Region. Create a
- BUse infrastructure as code (IaC) to provision the new infrastructure in the DR Region. Create a
- CSet up a backup plan in AWS Backup to create cross-Region backups for the EC2 instances and
- DUse infrastructure as code (IaC) to provision the new infrastructure in the DR Region. Create an
How the community answered
(18 responses)- A28% (5)
- B50% (9)
- C6% (1)
- D17% (3)
Why each option
The company needs a cost-effective disaster recovery solution for an e-commerce website (EC2 fleet in ASG, RDS MySQL) with an RPO of 30 seconds and an RTO of 10 minutes.
While an RDS Read Replica can provide a low RPO, running a full secondary database instance is generally less cost-effective than a backup and restore strategy for disaster recovery when the RTO allows for some provisioning time.
Using infrastructure as code (IaC) allows for rapid provisioning of the DR environment, while enabling Amazon RDS cross-Region automated backups with point-in-time recovery for MySQL meets the 30-second RPO for the database. Leveraging Amazon EBS snapshots for EC2 instances, combined with IaC to rebuild the EC2 fleet and attach volumes, enables a cost-effective pilot light strategy that can meet both RPO and RTO for the application components.
A 'scheduled daily backup plan for the EC2 instances' in AWS Backup would result in an RPO of up to 24 hours for EC2 instance configuration and root volumes, which fails to meet the stringent 30-second RPO requirement for the entire application.
An RDS Multi-AZ DB instance provides high availability within a single AWS Region, not a cross-Region disaster recovery solution. Restoring EC2 instances solely from EBS snapshots would require manual configuration and attachment, potentially increasing RTO and not fully capturing instance state.
Concept tested: Disaster recovery strategies (Pilot Light) and RPO/RTO
Source: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RestoreFromSnapshot.html#USER_RestoreFromSnapshot.PITR_Restore
Community Discussion
No community discussion yet for this question.