Which of the below mentioned service configurations does not help the organization achieve the said RPO and RTO?
Take a snapshot of the data every 10 minutes and copy it to the other region.
Use an elastic IP to assign to a running instance and use Route 53 to map the user’s domain with that IP.
Create ELB with multi-region routing to allow automated failover when required.
Use an AMI copy to keep the AMI available in other regions.
Explanations:
Taking snapshots every 10 minutes and copying them to another region helps with disaster recovery by ensuring data is replicated. However, this process may not meet the 10-minute RPO as snapshots can take longer to create and replicate, potentially missing the 10-minute window.
Using an elastic IP with Route 53 mapping provides high availability by quickly rerouting traffic in case of an instance failure. This approach helps with RTO but does not address RPO, as it does not replicate data or ensure consistency between regions.
Creating an Elastic Load Balancer (ELB) with multi-region routing enables automated failover, which supports both high availability and disaster recovery. This setup directly contributes to meeting both RPO and RTO objectives by maintaining continuous service and automatic traffic routing.
Copying an AMI to another region ensures that a backup of the instance is available in case of disaster. However, it does not address the RPO or data consistency, as it does not facilitate real-time data replication, and it could take longer than 10 minutes to copy and launch the AMI in the event of a failure.
I evaluate that the answer is:
Create ELB with multi-region routing to allow automated failover when required.