The API stack contains the following three tiers:• Amazon API Gateway• AWS Lambda• Amazon DynamoDBWhich 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 updathe data in a DynamoDB table.
Explanations:
While this option ensures requests are routed to the correct region, it does not provide optimal response times since it does not leverage latency-based routing or global tables. It risks higher latency for users in Europe if they are always routed to North America.
This option effectively uses latency-based routing in Route 53 to direct users to the closest API Gateway endpoint (either in North America or Europe), ensuring low latency. It also uses a DynamoDB global table, allowing for fast data retrieval and updates from either region, which is essential for high reliability and response times.
This option involves a manual disaster recovery process which may lead to increased downtime during failover. It does not utilize latency-based routing, potentially resulting in suboptimal performance. Although it uses a global table, the reliance on manual checks and updates can complicate failover processes and increase latency.
This option only configures Route 53 to point to the North American API Gateway, neglecting users in Europe. It lacks the necessary latency-based routing for optimal performance across regions, potentially leading to increased latency for European users. Additionally, it does not mention the use of a global DynamoDB table, limiting data accessibility.