What DR strategy could be used to achieve this RTO and …

An ERP application is deployed across multiple AZs in a single region. In the event of failure, the
Recovery Time Objective (RTO) must be less than 3 hours, and the Recovery Point Objective
(RPO) must be 15 minutes. The customer realizes that data corruption occurred roughly 1.5
hours ago. What DR strategy could be used to achieve this RTO and RPO in the event of this
kind of failure?

An ERP application is deployed across multiple AZs in a single region. In the event of failure, the
Recovery Time Objective (RTO) must be less than 3 hours, and the Recovery Point Objective
(RPO) must be 15 minutes. The customer realizes that data corruption occurred roughly 1.5
hours ago. What DR strategy could be used to achieve this RTO and RPO in the event of this
kind of failure?

A.
Take 15 minute DB backups stored in Glacier with transaction logs stored in S3 every 5 minutes.

B.
Use synchronous database master-slave replication between two availability zones.

C.
Take hourly DB backups to EC2 instance store volumes with transaction logs stored In S3 every
5 minutes.

D.
Take hourly DB backups to S3, with transaction logs stored in S3 every 5 minutes.



Leave a Reply 0

Your email address will not be published. Required fields are marked *