Which combination of deployment strategies will meet these requirements?
(Choose two.)
Create an Amazon Aurora Single-AZ cluster in multiple AWS Regions as the data store. Use Aurora’s automatic recovery capabilities in the event of a disaster.
Create an Amazon Aurora global database in two AWS Regions as the data store. In the event of a failure, promote the secondary Region to the primary for the application. Update the application to use the Aurora cluster endpoint in the secondary Region.
Create an Amazon Aurora cluster in multiple AWS Regions as the data store. Use a Network Load Balancer to balance the database traffic in different Regions.
Set up the application in two AWS Regions. Use Amazon Route 53 failover routing that points to Application Load Balancers in both Regions. Use health checks and Auto Scaling groups in each Region.
Set up the application in two AWS Regions. Configure AWS Global Accelerator to point to Application Load Balancers (ALBs) in both Regions. Add both ALBs to a single endpoint group. Use health checks and Auto Scaling groups in each Region.
Explanations:
Amazon Aurora Single-AZ clusters are not suitable for multi-region disaster recovery. It lacks cross-region replication, which is necessary to meet the RPO and RTO requirements.
Amazon Aurora Global Database provides cross-region replication with low-latency failover capabilities. In the event of a disaster, the secondary region can be promoted to primary, meeting both RPO and RTO requirements.
Amazon Aurora clusters in multiple AWS Regions are not a recommended setup without proper cross-region replication support. Additionally, using a Network Load Balancer for database traffic isn’t appropriate for failover purposes in this context.
Setting up the application in two AWS Regions with Route 53 failover routing, Application Load Balancers, and Auto Scaling groups meets the RTO and RPO requirements for disaster recovery and failover.
While AWS Global Accelerator improves global application availability, using it in this case doesn’t directly address the database failover requirements, and it lacks clear cross-region database replication for MySQL or Aurora.
If I had to guess, I’d say the answer is:
Create an Amazon Aurora global database in two AWS Regions as the data store. In the event of a failure, promote the secondary Region to the primary for the application. Update the application to use the Aurora cluster endpoint in the secondary Region.
From what I’ve seen, the answer is:
Create an Amazon Aurora global database in two AWS Regions as the data store. In the event of a failure, promote the secondary Region to the primary for the application. Update the application to use the Aurora cluster endpoint in the secondary Region.