At-most-once delivery in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the producer to at-most-once delivery by disabling retries.

Kafka

props.put("retries", [1]);

Drag options to blanks, or click blank then click option'

A5

B0

C-1

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting retries to a positive number causes retries, which is not at-most-once.

Using -1 enables infinite retries, which is not at-most-once.

Setting retries to 0 disables retry attempts, ensuring at-most-once delivery.

2fill in blank

medium

Complete the code to disable idempotence for at-most-once delivery.

Kafka

props.put("enable.idempotence", [1]);

Drag options to blanks, or click blank then click option'

Afalse

Btrue

C"true"

D"false"

Attempts:

3 left

💡 Hint

Common Mistakes

Setting idempotence to true enables exactly-once semantics, not at-most-once.

Using string values instead of boolean can cause configuration errors.

Disabling idempotence by setting enable.idempotence to false allows at-most-once delivery.

3fill in blank

hard

Fix the error in the producer configuration to ensure at-most-once delivery by setting the acks correctly.

Kafka

props.put("acks", [1]);

Drag options to blanks, or click blank then click option'

A"0"

B"-1"

C"1"

D"all"

Attempts:

3 left

💡 Hint

Common Mistakes

Using "all" or "-1" waits for all replicas, which is not at-most-once.

Using "1" waits for leader acknowledgment, which can cause retries.

Setting acks to "0" means the producer does not wait for any acknowledgment, enabling at-most-once delivery.

4fill in blank

hard

Fill both blanks to create a producer config map for at-most-once delivery with no retries and no idempotence.

Kafka

Map<String, Object> props = new HashMap<>();
props.put("retries", [1]);
props.put("enable.idempotence", [2]);

Drag options to blanks, or click blank then click option'

A0

Btrue

Cfalse

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting retries to 1 or more enables retries, breaking at-most-once.

Setting idempotence to true enables exactly-once semantics.

Retries set to 0 disables retries, and idempotence set to false disables duplicate prevention, both needed for at-most-once delivery.

5fill in blank

hard

Fill all three blanks to configure a Kafka producer for at-most-once delivery: no retries, no idempotence, and no acknowledgments.

Kafka

props.put("retries", [1]);
props.put("enable.idempotence", [2]);
props.put("acks", [3]);

Drag options to blanks, or click blank then click option'

A1

Bfalse

C"0"

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using string "0" for retries instead of integer 0 causes errors.

Setting idempotence to true enables exactly-once semantics.

Setting acks to "1" or "all" waits for acknowledgments, not at-most-once.

Retries set to 0 disables retries, idempotence false disables duplicate prevention, and acks "0" disables waiting for acknowledgments, all together ensuring at-most-once delivery.

Practice

1.

What does at-most-once delivery guarantee in Kafka messaging?

easy

A. Messages are sent at least once, possibly duplicated

B. Messages are sent exactly once with no loss

C. Messages are sent only once but some may be lost

D. Messages are sent multiple times intentionally

Solution

1. Step 1: Understand at-most-once delivery meaning

   At-most-once delivery means messages are sent once without retries, so duplicates are avoided but some messages might be lost.

2. Step 2: Compare with other delivery guarantees

   At-least-once allows duplicates, exactly-once avoids loss and duplicates, so only at-most-once fits the description of possible loss but no duplicates.

3. Final Answer:

   Messages are sent only once but some may be lost -> Option C

4. Quick Check:

   At-most-once = no duplicates, possible loss [OK]

Hint: At-most-once means no retries, so possible message loss [OK]

Common Mistakes:

• Confusing at-most-once with exactly-once delivery
• Assuming no messages are ever lost
• Thinking duplicates can occur in at-most-once

2.

Which Kafka producer configuration enables at-most-once delivery?

producer = KafkaProducer(acks=?, retries=? )

easy

A. acks=all, retries=5

B. acks=0, retries=0

C. acks=1, retries=3

D. acks=all, retries=0

Solution

1. Step 1: Identify settings for at-most-once

   At-most-once requires no retries and no acknowledgments, so acks=0 and retries=0 are needed.

2. Step 2: Check other options

   Other options enable retries or acknowledgments, which allow retries and possible duplicates, not at-most-once.

3. Final Answer:

   acks=0, retries=0 -> Option B

4. Quick Check:

   acks=0 & retries=0 = at-most-once [OK]

Hint: Set acks and retries to zero for at-most-once [OK]

Common Mistakes:

• Setting retries > 0 allows retries, not at-most-once
• Using acks=all causes waiting for confirmation
• Confusing acks=1 with acks=0

3.

Given the following Kafka producer code snippet, what is the expected delivery guarantee?

producer = KafkaProducer(acks=0, retries=0)
producer.send('topic', b'message')

medium

A. At-most-once delivery with possible message loss

B. No message will be sent

C. Exactly-once delivery with no duplicates

D. At-least-once delivery with possible duplicates

Solution

1. Step 1: Analyze producer settings

   With acks=0 and retries=0, the producer does not wait for acknowledgment and does not retry on failure.

2. Step 2: Determine delivery guarantee

   This means messages may be lost if sending fails, but duplicates won't occur, matching at-most-once delivery.

3. Final Answer:

   At-most-once delivery with possible message loss -> Option A

4. Quick Check:

   acks=0 & retries=0 = at-most-once [OK]

Hint: acks=0 and retries=0 means no retries, so at-most-once [OK]

Common Mistakes:

• Assuming messages are always delivered
• Confusing at-most-once with exactly-once
• Thinking duplicates can happen here

4.

Identify the error in this Kafka producer configuration for at-most-once delivery:

producer = KafkaProducer(acks=1, retries=0)
producer.send('topic', b'message')

medium

A. acks=1 causes waiting for leader ack, not at-most-once

B. retries=0 causes infinite retries

C. Missing enable.idempotence=True

D. Topic name must be uppercase

Solution

1. Step 1: Check acks setting

   acks=1 means the producer waits for leader acknowledgment, allowing retries and possible duplicates, not at-most-once.

2. Step 2: Verify retries and other settings

   Retries=0 disables retries, but acks=1 still waits for confirmation, so this is not pure at-most-once.

3. Final Answer:

   acks=1 causes waiting for leader ack, not at-most-once -> Option A

4. Quick Check:

   acks must be 0 for at-most-once [OK]

Hint: acks must be 0 for at-most-once delivery [OK]

Common Mistakes:

• Thinking retries=0 means no retries but ignoring acks effect
• Assuming idempotence is required for at-most-once
• Believing topic names must be uppercase

5.

You want to configure a Kafka producer for at-most-once delivery but also need to minimize message loss. Which combination of settings is best?

Options:
A) acks=1, retries=0
B) acks=0, retries=0
C) acks=0, retries=3
D) acks=all, retries=0

hard

A. acks=all, retries=0 (wait for all acks, no retries)

B. acks=0, retries=0 (pure at-most-once, possible loss)

C. acks=0, retries=3 (retries with no ack, risky duplicates)

D. acks=1, retries=0 (wait for ack, no retries, less loss)

Solution

1. Step 1: Understand trade-offs

   Pure at-most-once (acks=0, retries=0) risks message loss. Waiting for ack reduces loss but may not be pure at-most-once.

2. Step 2: Evaluate options

   acks=1, retries=0 (wait for ack, no retries, less loss) waits for leader ack but disables retries, reducing loss while avoiding duplicates, closest to at-most-once with less loss.

3. Final Answer:

   acks=1, retries=0 (wait for ack, no retries, less loss) -> Option D

4. Quick Check:

   acks=1 & retries=0 balances loss and duplicates [OK]

Hint: Wait for ack but disable retries to reduce loss in at-most-once [OK]

Common Mistakes:

• Choosing retries > 0 breaks at-most-once
• Ignoring ack setting impact on loss
• Assuming acks=all with no retries is at-most-once