AWS Certified Solutions Architect Associate SAA-C03 Practice Question
An e-commerce platform built with microservices experiences sudden traffic spikes during flash-sale campaigns. The order-ingestion service must hand off each order message for downstream processing with these requirements:
Every order message must be processed at least once; duplicate processing is acceptable.
Producers and consumers must scale independently to handle unpredictable surges without message loss.
The solution should minimize operational overhead and keep services loosely coupled.
Amazon Simple Queue Service (SQS) is designed for decoupling producers and consumers with a fully managed message queue. Standard queues provide at-least-once delivery and automatically scale to virtually any throughput, allowing independent scaling of microservices .
Amazon Kinesis Data Streams is optimized for real-time analytics of large, ordered data streams and requires shard management; it is more complex than needed for simple message hand-off and may lose data if consumers fall behind shard retention.
Amazon EventBridge offers at-least-once event delivery but is optimized for routing events to multiple targets and has soft throughput quotas that can throttle extreme burst traffic.
AWS Step Functions orchestrates stateful workflows rather than providing a high-throughput message buffer between microservices.
Therefore, SQS is the most appropriate choice.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is Amazon Simple Queue Service (SQS) and how does it work?
Open an interactive chat with Bash
What does 'at least once' processing mean in the context of message queuing?
Open an interactive chat with Bash
What are the benefits of decoupling components in microservices architecture?