A company is building a serverless web application that will serve customers globally by using REST API endpoints. The application must minimize latency regardless of the application us-er's…

Question

Options

• ADeploy an Amazon API Gateway REST API with edge-optimized API endpoints for all cus-
• BDeploy an Amazon API Gateway REST API with Regional API endpoints for all customers.
• CDeploy an Amazon API Gateway REST API with Regional API endpoints for all customers.
• DDeploy a Network Load Balancer in each AWS Region where customers are located. Create

• A
  90% (37)
• B
  2% (1)
• C
  5% (2)
• D
  2% (1)

Explanation

For globally distributed consumers of REST APIs, API Gateway edge-optimized endpoints "route requests to the nearest CloudFront edge location, which then forwards them to your API in the [home] Region," reducing latency for users worldwide and scaling automatically for unknown or spiky traffic. By contrast, Regional endpoints are intended for clients within the same or nearby Region and do not provide global edge acceleration. AWS Lambda provides automatic scaling for serverless backends; latency can be further reduced by right-sizing memory (which also increases CPU) and, when needed, enabling provisioned concurrency to keep functions initialized and eliminate cold starts for critical paths. Using NLBs across Regions is not serverless and adds operational complexity without CloudFront edge acceleration. Therefore, combining API Gateway edge-optimized REST APIs with Lambda meets the requirements of minimal global latency and unknown initial traffic.

No community discussion yet for this question.