SAA-C03 · Question #163
A company has developed an API by using an Amazon API Gateway REST API and AWS Lambda functions. The API serves static content and dynamic content to users worldwide. The company wants to decrease…
The correct answer is A. Deploy the REST API as an edge-optimized API endpoint. Enable caching. Enable content. Edge-Optimized API: Designed for global users by routing requests through CloudFront's edge locations, reducing latency. Content Encoding: Enabling content encoding compresses data, further optimizing performance by decreasing payload size. Caching: Adding API Gateway caching…
Question
A company has developed an API by using an Amazon API Gateway REST API and AWS Lambda functions. The API serves static content and dynamic content to users worldwide. The company wants to decrease the latency of transferring the content for API requests. Which solution will meet these requirements?
Options
- ADeploy the REST API as an edge-optimized API endpoint. Enable caching. Enable content
- BDeploy the REST API as a Regional API endpoint. Enable caching. Enable content encoding in
- CDeploy the REST API as an edge-optimized API endpoint. Enable caching. Configure reserved
- DDeploy the REST API as a Regional API endpoint. Enable caching. Configure reserved
How the community answered
(25 responses)- A88% (22)
- C4% (1)
- D8% (2)
Explanation
Edge-Optimized API: Designed for global users by routing requests through CloudFront's edge locations, reducing latency. Content Encoding: Enabling content encoding compresses data, further optimizing performance by decreasing payload size. Caching: Adding API Gateway caching reduces the number of calls to Lambda and database backends, improving latency. Reserved Concurrency: Although useful, this does not directly affect latency for transferring static and dynamic content.
Community Discussion
No community discussion yet for this question.