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 primary 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:
Aurora clusters in a single Availability Zone across multiple Regions do not meet the RPO and RTO requirements as failover across Regions is not supported.
Aurora global database across two Regions allows for quick promotion of a secondary Region to the primary, meeting the RPO and RTO requirements.
Aurora multi-master clusters across multiple Regions are not suitable for RPO and RTO requirements as managing database traffic across Regions is complex.
Using Route 53 failover-based routing with Auto Scaling in two Regions ensures application availability and quick failover, meeting both RPO and RTO.
Multi-Region Auto Scaling with Application Load Balancers does not directly address the database failover needs for RPO and RTO.