Which solution will meet these requirements?

Explanations:

While deploying a new set of Lambda functions in a new Region and using an edge-optimized API endpoint may seem viable, it does not effectively facilitate failover, as it doesn’t directly use Route 53 for DNS-based failover. Moreover, Lambda functions cannot be shared across Regions; they must be deployed separately in each Region.

This option suggests changing the Route 53 DNS record to a multivalue answer, which can allow routing to multiple resources. However, it doesn’t specify that the Route 53 configuration should enable failover, meaning it wouldn’t automatically route traffic to a healthy API in another Region during an outage. Additionally, multivalue routing doesn’t provide a robust failover mechanism.

This option correctly utilizes a failover DNS record in Route 53, which is specifically designed to route traffic to a secondary Region when the primary becomes unhealthy. By enabling target health monitoring, Route 53 can check the health of both API Gateway endpoints and switch traffic to the secondary API if the primary fails. Converting DynamoDB tables to global tables ensures data availability across Regions, supporting the failover mechanism.

Although this option mentions using a multivalue answer in Route 53, which can support multiple endpoints, it does not specifically implement a failover strategy. Using global Lambda functions is not feasible since Lambda functions cannot be deployed globally; they need to be deployed in each Region. Therefore, this solution does not provide an effective failover capability.