DAS-C01 · Question #111
A company wants to collect and process events data from different departments in near-real time. Before storing the data in Amazon S3, the company needs to clean the data by standardizing the format…
The correct answer is C. Use Amazon Managed Streaming for Apache Kafka. Amazon MSK (Managed Streaming for Apache Kafka) is the correct choice due to the record size constraint. Kinesis Data Streams (A) has a hard limit of 1MB per record, making it unable to handle 10MB records. Kinesis Data Firehose (B) also inherits the 1MB record size limit for…
Question
A company wants to collect and process events data from different departments in near-real time. Before storing the data in Amazon S3, the company needs to clean the data by standardizing the format of the address and timestamp columns. The data varies in size based on the overall load at each particular point in time. A single data record can be 100 KB-10 MB. How should a data analytics specialist design the solution for data ingestion?
Options
- AUse Amazon Kinesis Data Streams.
- BUse Amazon Kinesis Data Firehose.
- CUse Amazon Managed Streaming for Apache Kafka.
- DUse Amazon Simple Queue Service (Amazon SQS).
How the community answered
(36 responses)- A14% (5)
- B6% (2)
- C75% (27)
- D6% (2)
Explanation
Amazon MSK (Managed Streaming for Apache Kafka) is the correct choice due to the record size constraint. Kinesis Data Streams (A) has a hard limit of 1MB per record, making it unable to handle 10MB records. Kinesis Data Firehose (B) also inherits the 1MB record size limit for streaming ingestion. Amazon SQS (D) has a maximum message size of 256KB (standard queues), far below the 10MB maximum. Amazon MSK can be configured to support large messages (up to the broker's max.message.bytes setting, which can be set to 10MB or more), making it the only option that can reliably handle the full 100KB–10MB record size range.
Topics
Community Discussion
No community discussion yet for this question.