Bird
0
0

Why does Kafka use a distributed commit log design instead of traditional queue-based messaging?

hard📝 Conceptual Q10 of 15
Kafka - Basics and Event Streaming
Why does Kafka use a distributed commit log design instead of traditional queue-based messaging?
ATo store messages only temporarily in memory
BTo allow multiple consumers to read the same data independently and replay messages
CTo limit message delivery to only one consumer at a time
DTo provide a graphical interface for message browsing
Step-by-Step Solution
Solution:

  1. Step 1: Understand commit log vs queue

    Kafka's commit log stores messages durably and allows multiple consumers to read independently.

  2. Step 2: Contrast with queue behavior

    Traditional queues deliver messages to one consumer and remove them, Kafka allows replay and multiple readers.

  3. Final Answer:

    To allow multiple consumers to read the same data independently and replay messages -> Option B

  4. Quick Check:

    Kafka commit log = Multi-consumer replay capability [OK]
Quick Trick: Commit log lets many consumers read and replay messages [OK]
Common Mistakes:
  • Thinking Kafka limits delivery to one consumer
  • Assuming messages are only in memory
  • Expecting Kafka to provide GUIs

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Consumer Groups - Rebalancing behavior - Quiz 13medium Consumer Groups - Partition assignment - Quiz 5medium Consumer Groups - Consumer group concept - Quiz 15hard Consumers - Subscribing to topics - Quiz 11easy Consumers - Subscribing to topics - Quiz 5medium Consumers - Offset management - Quiz 3easy Consumers - Consumer configuration - Quiz 11easy Kafka Basics and Event Streaming - Kafka installation and setup - Quiz 10hard Kafka Cluster Architecture - Leader election - Quiz 4medium Producers - Why producers publish data - Quiz 5medium