SAA-C03 · Question #147
A solutions architect needs to implement a solution that can handle up to 5,000 messages per second. The solution must publish messages as events to multiple consumers. The messages are upto 500 KB…
The correct answer is A. Kinesis Data Streams: Supports high throughput, strict ordering, multiple consumers, and data. Kinesis Data Streams satisfies every requirement simultaneously: it handles well over 5,000 messages/second by scaling shards, supports records up to 1 MB (comfortably fitting 500 KB messages), enforces strict ordering within each shard, offers configurable retention up to 365…
Question
A solutions architect needs to implement a solution that can handle up to 5,000 messages per second. The solution must publish messages as events to multiple consumers. The messages are upto 500 KB in size. The message consumers need to have the ability to use multiple programming languages to consume the messages with minimal latency. The solution must retain published messages for more than 3 months. The solution must enforce strict ordering of the messages. Which solution will meet these requirements?
Options
- AKinesis Data Streams: Supports high throughput, strict ordering, multiple consumers, and data
- BSNS + SQS FIFO: Can enforce ordering but lacks native support for 500 KB messages and
- CEventBridge: Lacks strict ordering and message size compatibility.
- DSNS + Firehose: Not designed for strict ordering or large message sizes.
How the community answered
(54 responses)- A78% (42)
- B11% (6)
- C4% (2)
- D7% (4)
Explanation
Kinesis Data Streams satisfies every requirement simultaneously: it handles well over 5,000 messages/second by scaling shards, supports records up to 1 MB (comfortably fitting 500 KB messages), enforces strict ordering within each shard, offers configurable retention up to 365 days (far exceeding the 3-month requirement), and is accessible via AWS SDKs across virtually all major programming languages with low latency via Enhanced Fan-Out for multiple consumers.
SNS + SQS FIFO (B) breaks on two requirements: SQS has a 256 KB message size limit (rejecting 500 KB messages) and FIFO queues cap at 3,000 TPS with batching - well short of 5,000/second. EventBridge (C) also enforces a 256 KB event size limit and provides no strict ordering guarantee, making it a poor fit for both constraints. SNS + Firehose (D) is a delivery pipeline designed for bulk data ingestion into storage targets (S3, Redshift), not a low-latency fan-out broker with ordering guarantees.
Memory tip: When you see the combo of high throughput + strict ordering + long retention + large messages + multi-consumer, think Kinesis Data Streams - it's the only AWS messaging service that checks all four boxes natively. If ordering is required but messages are small and throughput is modest, SQS FIFO is the runner-up.
Topics
Community Discussion
No community discussion yet for this question.