Which backup architecture will meet these requirements?

Your customer wishes to deploy an enterprise application to AWS which will consist of several web servers,
several application servers and a small (50GB) Oracle database information is stored, both in the database and
the file systems of the various servers. The backup system must support database recovery whole server and
whole disk restores, and individual file restores with a recovery time of no more than two hours. They have
chosen to use RDS Oracle as the database.
Which backup architecture will meet these requirements?

A.
Backup RDS using automated daily DB backups Backup the EC2 instances using AMIs and supplement
with file-level backup to S3 using traditional enterprise backup software to provide file level restore

B.
Backup RDS using a Multi-AZ Deployment Backup the EC2 instances using Amis, and supplement by
copying file system data to S3 to provide file level restore.

C.
Backup RDS using automated daily DB backups Backup the EC2 instances using EBS snapshots and
supplement with file-level backups to Amazon Glacier using traditional enterprise backup software to
provide file level restore

D.
Backup RDS database to S3 using Oracle RMAN Backup the EC2 instances using Amis, and supplement
with EBS snapshots for individual volume restore.

Explanation:
Point-In-Time Recovery
In addition to the daily automated backup, Amazon RDS archives database change logs. This enables you to
recover your database to any point in time during the backup retention period, up to the last five minutes of
database usage.
Amazon RDS stores multiple copies of your data, but for Single-AZ DB instances these copies are stored in a
single availability zone. If for any reason a Single-AZ DB instance becomes unusable, you can use point-in-time
recovery to launch a new DB instance with the latest restorable data. For more information on working with
point-in-time recovery, go to Restoring a DB Instance to a Specified Time.
Note
Multi-AZ deployments store copies of your data in different Availability Zones for greater levels of data
durability. For more information on Multi-AZ deployments, see High Availability (Multi-AZ).