SAA-C03 · Question #187
A company has an ecommerce application that users access through multiple mobile apps and web applications. The company needs a solution that will receive requests from the mobile apps and web…
The correct answer is B. Set up an Amazon API Gateway REST API with an integration to an Amazon Simple Queue. Why Option B is Correct: Amazon SQS: Ensures no requests are lost, even during traffic spikes. API Gateway: Handles dynamic traffic patterns efficiently, integrating with SQS for asynchronous processing. Lambda: Polls the queue and processes requests in a serverless and…
Question
A company has an ecommerce application that users access through multiple mobile apps and web applications. The company needs a solution that will receive requests from the mobile apps and web applications through an API. Request traffic volume varies significantly throughout each day. Traffic spikes during sales events. The solution must be loosely coupled and ensure that no requests are lost. Which solution will meet this requirement?
Options
- ACreate an Application Load Balancer (ALB). Create an AWS Elastic Beanstalk endpoint to
- BSet up an Amazon API Gateway REST API with an integration to an Amazon Simple Queue
- CCreate an Application Load Balancer (ALB). Create an AWS Lambda function to process the
- DSet up an Amazon API Gateway HTTP API with an integration to an Amazon Simple Notification
How the community answered
(58 responses)- A17% (10)
- B72% (42)
- C7% (4)
- D3% (2)
Explanation
Why Option B is Correct: Amazon SQS: Ensures no requests are lost, even during traffic spikes. API Gateway: Handles dynamic traffic patterns efficiently, integrating with SQS for asynchronous processing. Lambda: Polls the queue and processes requests in a serverless and scalable manner. Dead- Letter Queue (DLQ): Ensures failed messages are retried or logged for debugging. Why Other Options Are Not Ideal: Option A: Elastic Beanstalk cannot handle queue-based decoupling, making it unsuitable for Option C: ALB to Lambda does not provide buffering for traffic spikes, risking request loss. Option D: SNS is better suited for notifications, not reliable for ensuring message durability.
Community Discussion
No community discussion yet for this question.