QuizzesExactly-Once Semantics (EOS) — Concept Check
intermediate
kafka

Exactly-Once Semantics (EOS) — Concept Check

Questions on Exactly-Once Semantics (EOS). Achieved by combining idempotent producer, transactions, and isolation.level=read_committed on consumers; Kafka Streams supports EOS with processing.guarantee=exactly_once_v2.

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 Exactly-Once Semantics (EOS) — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A producer in a Kafka system retries sending a message after a failure. What ensures that the message is not duplicated?

    • AIdempotent producer with PID and sequence number
    • BConsumer with isolation.level=read_committed
    • CKafka Streams with processing.guarantee=exactly_once_v2
    • DTransactional producer with multiple partitions
  2. 2.In a Kafka Streams application, what configuration ensures exactly-once semantics?

    • Aprocessing.guarantee=exactly_once_v2
    • Benable.idempotence=true
    • Cacks=all
    • Disolation.level=read_committed
  3. 3.A producer writes to two partitions atomically but crashes before committing offsets. What prevents duplicate processing?

    • ATransactional producer commits offsets atomically
    • BIdempotent producer deduplicates messages
    • CKafka Streams handles retries automatically
    • DConsumer skips uncommitted records
  4. 4.A consumer reads from a Kafka topic and processes uncommitted transactional records. What setting is likely missing?

    • Aprocessing.guarantee=exactly_once_v2
    • Backs=all
    • Cenable.idempotence=true
    • Disolation.level=read_committed
  5. 5.What happens if a Kafka producer with enable.idempotence=true restarts?

    • ATransactions are automatically aborted
    • BThe PID remains the same, maintaining idempotence
    • CThe PID changes, breaking idempotence across sessions
    • DAll partitions are reset, causing data loss
  6. 6.A Kafka producer sends messages to multiple partitions but only some are visible to consumers. What might be the issue?

    • AIdempotence was not enabled, causing duplicates
    • BIsolation level was set to read_uncommitted
    • CProducer retries were not handled properly
    • DTransactions were aborted, hiding some messages
  7. 7.A Kafka Streams application is set up without processing.guarantee=exactly_once_v2. What might occur?

    • ASkipping of uncommitted records
    • BAutomatic handling of retries
    • CDuplicate processing of records
    • DAtomic multi-partition writes