Your company currently has a 2-tier web application running in an on-premises data center.
You have experienced several infrastructure failures in the past few months resulting in significant
financial losses. Your CIO is strongly considering moving the application to AWS. While working
on achieving buy-In from the other company executives, he asks you to develop a disaster
recovery plan to help improve business continuity in the short term. He specifies a target
Recovery Time Objective (RTO) of 4 hours and a Recovery Point Objective (RPO) of 1 hour or
less. He also asks you to implement the solution within 2 weeks.
Your database is 200GB in size and you have a 20Mbps Internet connection.
How would you do this while minimizing costs?

A.
Create an EBS backed private AMI which includes a fresh install of your application.
Develop a CloudFormation template which includes your AMI and the required EC2, AutoScaling,
and ELB resources to support deploying the application across Multiple-Availability-Zones.
Asynchronously replicate transactions from your on-premises database to a database instance in
AWS across a secure VPN connection.

B.
Deploy your application on EC2 instances within an Auto Scaling group across multiple
availability zones. Asynchronously replicate transactions from your on-premises database to a
database instance in AWS across a secure VPN connection.

C.
Create an EBS backed private AMI which includes a fresh install of your application.
Setup a script in your data center to backup the local database every 1 hour and to encrypt and
copy the resulting file to an S3 bucket using multi-part upload.

D.
Install your application on a compute-optimized EC2 instance capable of supporting the
application’s average load.
Synchronously replicate transactions from your on-premises database to a database instance in
AWS across a secure Direct Connect connection.