QuizzesAt-Least-Once Delivery — Concept Check
intermediate
kafka

At-Least-Once Delivery — Concept Check

Questions on At-Least-Once Delivery. At-least-once guarantees no message is lost; consumers may process duplicates after rebalance or restart, so consumer logic must be idempotent.

7 minutes 7 questions Pass at 70%
Time Limit
7 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

7 questions on At-Least-Once Delivery — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A Kafka consumer processes records 200-210 but crashes before committing offsets. What happens when it restarts?

    • ARecords 200-210 are skipped to avoid duplicates
    • BThe consumer waits for manual intervention
    • CProcessing resumes from the last processed record
    • DRecords 200-210 are reprocessed, causing duplicates
  2. 2.A consumer uses at-least-once delivery but processes duplicate records. What should be implemented to handle this?

    • AEnable auto-commit
    • BIdempotent consumer logic
    • CReduce the batch size
    • DIncrease the poll timeout
  3. 3.Why might a Kafka producer send duplicate messages even with acks=all and retries enabled?

    • AIncorrect partition assignment
    • BProducer buffer overflow
    • CNetwork errors causing retry without acknowledgment
    • DConsumer offset mismanagement
  4. 4.How can a consumer ensure it doesn't process the same Kafka message more than once?

    • AIncrease poll interval
    • BUse a single consumer per partition
    • CEnable auto-commit in Kafka
    • DUse a processed_events table for deduplication
  5. 5.A team notices duplicate processing despite using at-least-once delivery. What might they be missing?

    • AAdequate consumer group size
    • BIdempotent consumer logic
    • CCorrect topic configuration
    • DProper partition assignment
  6. 6.A developer claims that enabling idempotence on the producer side prevents all duplicates. Why is this incorrect?

    • AIdempotence only affects message order
    • BProducer idempotence requires manual configuration
    • CConsumer-side duplicates can still occur
    • DIt only works with acks=none
  7. 7.What is the primary benefit of at-least-once delivery in Kafka?

    • AOffsets are automatically committed
    • BNo message is lost, even if duplicates occur
    • CMessages are processed exactly once
    • DConsumers never need rebalancing