Bird
Raised Fist0

Why does at-most-once delivery in Kafka not guarantee message persistence?

hard🧠 Conceptual Q10 of Q15
Kafka - Message Delivery Semantics

Why does at-most-once delivery in Kafka not guarantee message persistence?

ABecause consumer commits offsets too early
BBecause Kafka disables message storage in this mode
CBecause producer does not wait for broker acknowledgment
DBecause messages are always duplicated
Step-by-Step Solution
Solution:

  1. Step 1: Understand producer behavior in at-most-once

    Producer sends messages without waiting for broker acknowledgment (acks=0).

  2. Step 2: Effect on message persistence

    Without acknowledgment, messages may not be stored by broker, so persistence is not guaranteed.

  3. Final Answer:

    Because producer does not wait for broker acknowledgment -> Option C

  4. Quick Check:

    No ack wait means no persistence guarantee [OK]
Quick Trick: No ack wait means no guarantee of message persistence [OK]
Common Mistakes:
MISTAKES
  • Thinking Kafka disables storage in at-most-once
  • Confusing consumer offset commits with delivery
  • Assuming duplicates cause persistence issues

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Kafka Connect - Standalone vs distributed mode - Quiz 12easy Kafka Connect - Kafka Connect architecture - Quiz 8hard Kafka Streams - Why stream processing transforms data - Quiz 3easy Kafka with Java/Python - Python consumer - Quiz 2easy Kafka with Java/Python - Java consumer client - Quiz 8hard Kafka with Java/Python - Python consumer - Quiz 8hard Monitoring and Operations - Key broker metrics - Quiz 11easy Monitoring and Operations - Why monitoring prevents outages - Quiz 8hard Schema Registry - Schema evolution (backward, forward, full) - Quiz 12easy Schema Registry - Schema compatibility rules - Quiz 6medium