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 hourly DB backups to 53, with transaction logs stored in 53 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 53 every 5 minutes.
D . Take 15 minute DB backups stored In Glacier with transaction logs stored in 53 every 5 minutes.
Answer: A
Latest AWS-Solution-Architect-Associate Dumps Valid Version with 986 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund