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

Exactly-Once Semantics (EOS) — Concept Check

Questions on Exactly-Once Semantics (EOS). Exactly-once semantics guarantees each message is delivered and processed precisely once, even during failures. It requires idempotent producers, transactional APIs, and read_committed consumers.

8 minutes 8 questions Pass at 70%
Time Limit
8 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

8 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 developer sets up a Kafka producer with `enable.idempotence=false`. What is the likely consequence?

    • AConsumers will receive uncommitted messages.
    • BDuplicate messages may be sent during retries.
    • CMessages will never be sent due to configuration error.
    • DTransactions will be ignored by the producer.
  2. 2.In a Spring Boot application, a transactional producer is configured, but `executeInTransaction` is not used. What might happen?

    • AMessages may not be sent atomically across topics.
    • BMessages will be sent twice to each topic.
    • CConsumers will see uncommitted messages.
    • DThe producer will throw an exception on send.
  3. 3.A Kafka consumer is set with `isolation.level=read_uncommitted`. What issue might arise?

    • AIt will only see committed messages.
    • BIt may process messages from aborted transactions.
    • CIt will ignore all transactional messages.
    • DIt will duplicate messages during processing.
  4. 4.A producer sends messages to multiple topics using `executeInTransaction`. What does this ensure?

    • AMessages are sent atomically across topics.
    • BMessages are sent without any retries.
    • CMessages are sent with reduced latency.
    • DMessages are sent with increased throughput.
  5. 5.A developer configures a Kafka producer with `transactional.id` but forgets to set `enable.idempotence=true`. What is the outcome?

    • AThe producer will send messages without any retries.
    • BThe producer will throw an exception on startup.
    • CThe producer will ignore the transactional ID.
    • DThe producer will not support exactly-once semantics.
  6. 6.What is the role of `enable.idempotence` in Kafka producers?

    • AIt allows consumers to see only committed messages.
    • BIt ensures messages are sent with low latency.
    • CIt prevents duplicate messages during retries.
    • DIt increases the throughput of message sending.
  7. 7.A consumer is configured with `read_committed`. What is the benefit of this setting?

    • AIt reduces the load on the Kafka broker.
    • BIt only processes committed transaction messages.
    • CIt allows processing of all messages, committed or not.
    • DIt increases the speed of message consumption.
  8. 8.In a Kafka setup, why might a producer use `executeInTransaction`?

    • ATo reduce the number of messages sent.
    • BTo ensure atomic message delivery across multiple topics.
    • CTo increase the speed of message delivery.
    • DTo allow consumers to process uncommitted messages.