SAA-C03 · Question #176
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 up to 500 KB…
The correct answer is A. Publish messages to an Amazon Kinesis Data Streams data stream. Enable enhanced fan-out. AmazonKinesis Data Streamsis the best choice for this scenario: Message throughput: Kinesis Data Streams supports high throughput with enhanced fan-out and dedicated throughput for consumers. Large message size: Supports message sizes up to 1 MB, meeting the 500 KB requirement…
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 up to 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 this requirement?
Options
- APublish messages to an Amazon Kinesis Data Streams data stream. Enable enhanced fan-out.
- BPublish messages to an Amazon Simple Notification Service (Amazon SNS) topic. Ensure that
- CPublish messages to Amazon EventBridge. Allow each consumer to create rules to deliver
- DPublish messages to an Amazon Simple Notification Service (Amazon SNS) topic. Ensure that
How the community answered
(30 responses)- A60% (18)
- B13% (4)
- C23% (7)
- D3% (1)
Explanation
AmazonKinesis Data Streamsis the best choice for this scenario: Message throughput: Kinesis Data Streams supports high throughput with enhanced fan-out and dedicated throughput for consumers. Large message size: Supports message sizes up to 1 MB, meeting the 500 KB requirement. Message retention: Data streams can retain messages for up to 365 days. Strict ordering: Guarantees message ordering within shards. Why Other Options Are Not Ideal: While SQS FIFO supports strict ordering, SNS topics do not. SNS also does not natively support message retention or strict ordering across consumers.Does not meet requirements. EventBridge does not provide strict ordering guarantees or message retention beyond 24 hours.Does not meet requirements. SNS topics with Data Firehose are not designed for use cases requiring strict ordering or long message retention.Does not meet requirements.
Community Discussion
No community discussion yet for this question.