ExamPark
Course menuDEA-C01

Exams / DEA-C01 / Streaming ingestion with Kinesis and MSK / Question 1

DEA-C01 practice question: Streaming ingestion with Kinesis and MSK (1 of 3)

Data Ingestion and Transformation A free question from our original DEA-C01 practice exam. Try it, then open the answer to see why each option is right or wrong.

Last verified against current AWS documentation ·How we write our questions

An esports league runs a match-telemetry platform that publishes about 40,000 events per second from its game servers. Eleven analytics services already consume the stream through Apache Kafka client libraries, and their consumer groups and offsets are tuned.

The league is moving the platform to AWS and does not want to rewrite those consumers. It needs a managed service that keeps the Kafka protocol, topics and partitions, and AWS should handle broker patching and replacement.

Which solution meets these requirements?

Choose one answer.

  1. A. Create an Amazon MSK cluster, keep the existing Kafka clients, topics and partitions, and let AWS manage the brokers and their patching.
  2. B. Replace the Kafka clients with the Kinesis Client Library and move every consumer group to a Kinesis Data Streams application with its own offset logic.
  3. C. Install Kafka on Amazon EC2 instances in an Auto Scaling group, and use AWS Systems Manager Patch Manager to update the brokers on a schedule.
  4. D. Send the events through Amazon Data Firehose into Amazon S3, and have each consumer read new objects in batches on a schedule.
Show the answer and explanation

Answer: A

  • A. Right: Correct. Amazon MSK runs Apache Kafka with the standard Kafka APIs, so the consumers keep their code, consumer groups and offsets. AWS operates the brokers and applies patches, which meets both requirements. Learn more: Welcome to the Amazon MSK Developer Guide (opens in a new tab)
  • B. Wrong: Kinesis Data Streams handles high-throughput streaming well, but it does not speak the Kafka protocol. Each of the eleven services would need to be rewritten, which the league has ruled out. Learn more: What is Amazon Kinesis Data Streams? (opens in a new tab)
  • C. Wrong: This keeps the Kafka protocol, but the league would still run and recover the brokers itself. Patch Manager updates operating systems, not the Kafka cluster, so the operating burden stays with the team.
  • D. Wrong: Firehose buffers records and delivers them to S3, which adds delay and removes the streaming consumer model. The services would still need to be rewritten to read files instead of streams. Learn more: What is Amazon Data Firehose? (opens in a new tab)

Explanation

Kafka clients should not need rewriting when a platform moves to AWS. Amazon MSK keeps the Kafka API, topics, partitions and consumer offsets, and AWS manages the brokers. Kinesis Data Streams and Firehose are capable services, but each would require changes on the consumer side.

Study

Keep practicing

Answer questions with a score at the end, or practice just this topic with the explanation after each one. No sign-up needed.

Take the free DEA-C01 practice examPractice Streaming ingestion with Kinesis and MSKAll Streaming ingestion with Kinesis and MSK questions

Want more on Streaming ingestion with Kinesis and MSK? The 5 full-length practice sets have 13 more Streaming ingestion with Kinesis and MSK questions, 325 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets