Which combination of deployment strategies will meet these requirements?
(Choose two.)
Create an Amazon Aurora cluster in one Availability Zone across multiple 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 Regions as the data store. In the event of a failure, promote the secondary Region as the master for the application.
Create an Amazon Aurora multi-master cluster across multiple Regions as the data store. Use a Network Load Balancer to balance the database traffic in different Regions.
Set up the application in two Regions and use Amazon Route 53 failover-based routing that points to the Application Load Balancers in both Regions. Use health checks to determine the availability in a given Region. Use Auto Scaling groups in each Region to adjust capacity based on demand.
Set up the application in two Regions and use a multi-Region Auto Scaling group behind Application Load Balancers to manage the capacity based on demand. In the event of a disaster, adjust the Auto Scaling group’s desired instance count to increase baseline capacity in the failover Region.
Explanations:
Amazon Aurora across multiple Regions with a single Availability Zone cannot meet the RPO and RTO requirements. The solution lacks redundancy and failover.
Aurora global database across two Regions provides automated failover capabilities. The secondary Region can be promoted to master, meeting RPO and RTO needs.
Aurora multi-master across multiple Regions would be complex to manage and may not meet the tight RTO and RPO requirements as effectively as the global database option.
Multi-Region setup with Route 53 failover-based routing and Auto Scaling groups ensures minimal downtime and meets both RPO and RTO requirements.
Multi-Region Auto Scaling groups behind Application Load Balancers alone may not ensure quick enough failover or meet the strict RTO of 10 minutes.
I gauge that the answer is:
Create an Amazon Aurora global database in two Regions as the data store. In the event of a failure, promote the secondary Region as the master for the application.