The API stack contains the following three tiers:Amazon API Gateway -AWS Lambda -Amazon DynamoDB -Which solution will meet the requirements?
Configure Amazon Route 53 to point to API Gateway APIs in North America and Europe using health checks. Configure the APIs to forward requests to a Lambda function in that Region. Configure the Lambda functions to retrieve and update the data in a DynamoDB table in the same Region as the Lambda function.
Configure Amazon Route 53 to point to API Gateway APIs in North America and Europe using latency-based routing and health checks. Configure the APIs to forward requests to a Lambda function in that Region. Configure the Lambda functions to retrieve and update the data in a DynamoDB global table.
Configure Amazon Route 53 to point to API Gateway in North America, create a disaster recovery API in Europe, and configure both APIs to forward requests to the Lambda functions in that Region. Retrieve the data from a DynamoDB global table. Deploy a Lambda function to check the North America API health every 5 minutes. In the event of a failure, update Route 53 to point to the disaster recovery API.
Configure Amazon Route 53 to point to API Gateway API in North America using latency-based routing. Configure the API to forward requests to the Lambda function in the Region nearest to the user. Configure the Lambda function to retrieve and update the data in a DynamoDB table.
Explanations:
This solution does not use a DynamoDB global table, which is necessary for seamless data access across multiple regions. It restricts data access to a single region, making it less optimal for a globally distributed setup.
This solution uses latency-based routing with Amazon Route 53, ensuring that users are directed to the API in the nearest region. It also utilizes DynamoDB global tables, which allow the Lambda functions in different regions to read and write to the same table, ensuring data consistency and high availability.
This approach introduces unnecessary complexity with a disaster recovery API and manual health checks. DynamoDB global tables would be a more efficient way to ensure global data access, and Route 53 latency-based routing would handle traffic distribution without the need for manual failover.
This solution only uses latency-based routing to direct users to the North American API and does not address the need for a multi-region setup. It lacks the use of DynamoDB global tables for data synchronization across regions, which is critical for fast response times and high availability.