Answer: Edge-optimized endpoint

## Explanation **Edge-optimized endpoint** is the correct choice for this scenario because: 1. **Geographically distributed users**: The web application users are distributed across different geographic locations, which means API requests will come from various regions. 2. **Latency reduction requirement**: The company specifically wants to reduce latency for API requests. 3. **How edge-optimized endpoints work**: - Edge-optimized endpoints are designed for geographically distributed clients - They use Amazon CloudFront distributions to route requests to the nearest CloudFront edge location - This reduces latency by bringing the API endpoint closer to users - API Gateway still executes the API in a single AWS region, but the CloudFront distribution handles request routing **Why other options are incorrect**: - **A. Private endpoint**: Used for accessing APIs from within a VPC, not for reducing latency for geographically distributed users - **B. Regional endpoint**: Best for clients in the same region as the API, but doesn't optimize for geographically distributed users - **C. Interface VPC endpoint**: Used for private connectivity to AWS services from within a VPC, not for public API access or latency optimization **Key takeaway**: When you need to serve API requests to users across different geographic locations with minimal latency, edge-optimized endpoints are the recommended solution as they leverage CloudFront's global edge network.

Author: LeetQuiz Editorial Team