The reference architecture must meet the following requirements:✑ High availability within an AWS Region✑ Able to fail over in 1 minute to another AWS Region for disaster recovery✑ Provide the most efficient solution while minimizing the impact on the user experienceWhich combination of steps will meet these requirements?
(Choose three.)
Use an Amazon Route 53 weighted routing policy set to 100/0 across the two selected Regions. Set Time to Live (TTL) to 1 hour.
Use an Amazon Route 53 failover routing policy for failover from the primary Region to the disaster recovery Region. Set Time to Live (TTL) to 30 seconds.
Use a global table within Amazon DynamoDB so data can be accessed in the two selected Regions.
Back up data from an Amazon DynamoDB table in the primary Region every 60 minutes and then write the data to Amazon S3. Use S3 cross-Region replication to copy the data from the primary Region to the disaster recovery Region. Have a script import the data into DynamoDB in a disaster recovery scenario.
Implement a hot standby model using Auto Scaling groups for the web and application layers across multiple Availability Zones in the Regions. Use zonal Reserved Instances for the minimum number of servers and On-Demand Instances for any additional resources.
Use Auto Scaling groups for the web and application layers across multiple Availability Zones in the Regions. Use Spot Instances for the required resources.
Explanations:
The Amazon Route 53 failover routing policy ensures automatic failover between Regions in case of a failure, and setting TTL to 30 seconds helps minimize downtime.
Amazon DynamoDB global tables provide multi-Region, fully replicated tables, allowing data to be accessed in both Regions, which is ideal for high availability and disaster recovery.
Implementing a hot standby model with Auto Scaling groups across multiple Availability Zones ensures high availability within each Region and fast failover to the disaster recovery Region.
The weighted routing policy (100/0) would not facilitate failover between Regions and doesn’t meet the disaster recovery requirement. TTL of 1 hour would also cause delays in failover.
Backing up data every 60 minutes and manually importing it into DynamoDB in the disaster recovery Region is too slow and complex for meeting the 1-minute failover requirement.
Spot Instances are not suitable for high availability and disaster recovery scenarios, as they can be terminated by AWS at any time, potentially disrupting the service.
As far as I can tell, the answer is:
Use an Amazon Route 53 failover routing policy for failover from the primary Region to the disaster recovery Region. Set Time to Live (TTL) to 30 seconds.
I strategize that the answer is:
Use an Amazon Route 53 failover routing policy for failover from the primary Region to the disaster recovery Region. Set Time to Live (TTL) to 30 seconds.