Consumer acknowledgment strategies in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding manual acknowledgment in RabbitMQ

In RabbitMQ, what happens when a consumer uses manual acknowledgments but fails to send an acknowledgment for a received message?

A The message is automatically acknowledged after a timeout period.

B The message is duplicated and sent to all other consumers immediately.

C The message remains unacknowledged and will be requeued when the consumer disconnects.

D The message is lost and removed from the queue permanently.

💡 Hint

Think about what RabbitMQ does to ensure messages are not lost if a consumer crashes.

When manual acknowledgments are used, RabbitMQ waits for the consumer to send an acknowledgment. If the consumer disconnects without acknowledging, the message is requeued for delivery to another consumer.

💻 Command Output

intermediate

Output of RabbitMQ consumer with auto-ack enabled

What is the output behavior when a RabbitMQ consumer is started with autoAck=true and the consumer crashes before processing the message?

RabbitMQ

channel.basicConsume(queueName, true, consumer);

A The message is duplicated and sent to all consumers.

B The message is requeued and delivered to another consumer.

C The message is held until the consumer recovers and processes it.

D The message is lost because it was auto-acknowledged immediately.

💡 Hint

Auto-ack means the message is acknowledged as soon as it is delivered.

With autoAck=true, RabbitMQ considers the message acknowledged immediately upon delivery, so if the consumer crashes before processing, the message is lost.

🔀 Workflow

advanced

Correct sequence for manual acknowledgment in RabbitMQ consumer

Arrange the steps in the correct order for a RabbitMQ consumer using manual acknowledgments to process a message safely.

A 1,4,2,3

B 1,2,3,4

C 2,1,3,4

D 1,3,2,4

💡 Hint

Acknowledge only after successful processing.

The consumer must first receive the message, then process it. If processing succeeds, it sends an acknowledgment. Errors should be handled after processing and before acknowledgment.

❓ Troubleshoot

advanced

Identifying cause of message duplication in RabbitMQ

A RabbitMQ consumer using manual acknowledgments notices duplicate messages being processed. Which of the following is the most likely cause?

A The consumer is not acknowledging messages, causing RabbitMQ to requeue them after disconnect.

B The consumer is acknowledging messages before processing them.

C The queue is configured with <code>autoDelete=true</code>.

D The consumer is using <code>autoAck=true</code>.

💡 Hint

Think about what happens if messages are not acknowledged.

If messages are not acknowledged manually, RabbitMQ will requeue them when the consumer disconnects, causing duplicates when redelivered.

✅ Best Practice

expert

Best practice for ensuring message processing reliability in RabbitMQ

Which consumer acknowledgment strategy best ensures that messages are processed exactly once, even if the consumer crashes during processing?

A Use manual acknowledgments and acknowledge messages only after successful processing.

B Use <code>autoAck=true</code> to acknowledge messages immediately upon receipt.

C Use manual acknowledgments but acknowledge messages before processing starts.

D Disable acknowledgments and rely on queue durability.

💡 Hint

Consider when to send acknowledgment to avoid message loss or duplication.

Manual acknowledgment after successful processing ensures messages are not lost or duplicated, even if the consumer crashes during processing.

Practice

1. What does setting autoAck=false in a RabbitMQ consumer do?

easy

A. It pauses message delivery until the consumer is ready.

B. It automatically acknowledges messages as soon as they are received.

C. It rejects messages immediately without processing.

D. It requires the consumer to manually acknowledge messages after processing.

Solution

1. Step 1: Understand autoAck parameter

   The autoAck flag controls if messages are acknowledged automatically or manually.

2. Step 2: Effect of setting autoAck to false

   When autoAck=false, the consumer must explicitly send an acknowledgment after processing each message.

3. Final Answer:

   It requires the consumer to manually acknowledge messages after processing. -> Option D

4. Quick Check:

   autoAck=false means manual ack [OK]

Hint: autoAck=false means manual message acknowledgment [OK]

Common Mistakes:

• Thinking autoAck=false auto-acknowledges messages
• Confusing autoAck with message rejection
• Assuming autoAck pauses message delivery

2. Which of the following is the correct way to send a manual acknowledgment in RabbitMQ using the client library?

easy

A. channel.acknowledge(deliveryTag);

B. channel.basicAck(deliveryTag, false);

C. channel.sendAck(deliveryTag, true);

D. channel.confirm(deliveryTag);

Solution

1. Step 1: Identify the correct method name

   The RabbitMQ client uses basicAck to acknowledge messages manually.

2. Step 2: Understand parameters of basicAck

   The first parameter is the deliveryTag identifying the message; the second is multiple flag, usually false for single ack.

3. Final Answer:

   channel.basicAck(deliveryTag, false); -> Option B

4. Quick Check:

   Manual ack uses basicAck method [OK]

Hint: Manual ack uses basicAck(deliveryTag, false) [OK]

Common Mistakes:

• Using non-existent methods like acknowledge or sendAck
• Confusing confirm with ack
• Passing wrong parameters to basicAck

3. Given the following code snippet, what will happen if the consumer crashes before calling channel.basicAck(deliveryTag, false);?

channel.basicConsume(queueName, false, consumerTag, new DefaultConsumer(channel) {
  public void handleDelivery(String consumerTag, Envelope envelope, AMQP.BasicProperties properties, byte[] body) {
    // process message
    // no ack sent yet
  }
});

medium

A. The message will be requeued and delivered again to another consumer.

B. The message will be lost and never delivered again.

C. The message will be acknowledged automatically despite no ack call.

D. The consumer will block and wait indefinitely.

Solution

1. Step 1: Understand manual ack behavior on consumer crash

   If a consumer crashes before sending basicAck, RabbitMQ considers the message unacknowledged.

2. Step 2: RabbitMQ requeues unacknowledged messages

   Unacknowledged messages are requeued and delivered to other consumers to avoid message loss.

3. Final Answer:

   The message will be requeued and delivered again to another consumer. -> Option A

4. Quick Check:

   Unacked message + crash = requeue [OK]

Hint: Unacked messages get requeued on consumer crash [OK]

Common Mistakes:

• Assuming message is lost without ack
• Thinking message auto-acks on crash
• Believing consumer blocks indefinitely

4. You have a consumer with autoAck=false but forgot to call basicAck after processing messages. What problem will this cause?

medium

A. Messages will pile up as unacknowledged and may block new deliveries.

B. Messages will be acknowledged automatically anyway.

C. RabbitMQ will delete the queue automatically.

D. The consumer will crash immediately.

Solution

1. Step 1: Effect of missing manual acknowledgments

   Without calling basicAck, messages remain unacknowledged in RabbitMQ.

2. Step 2: Consequence of unacknowledged messages

   Unacknowledged messages accumulate and can block further message delivery due to prefetch limits.

3. Final Answer:

   Messages will pile up as unacknowledged and may block new deliveries. -> Option A

4. Quick Check:

   No ack + autoAck=false = message pileup [OK]

Hint: No ack with autoAck=false causes message buildup [OK]

Common Mistakes:

• Assuming messages auto-acknowledge anyway
• Thinking RabbitMQ deletes queues automatically
• Believing consumer crashes without ack

5. You want to ensure that a batch of 5 messages is processed before sending a single acknowledgment to RabbitMQ. Which strategy should you use?

hard

A. Set autoAck=true to acknowledge messages automatically.

B. Call basicAck(deliveryTag, false) after each message individually.

C. Call basicAck(deliveryTag, true) after processing the 5th message to acknowledge all previous messages.

D. Call basicReject(deliveryTag, false) after processing the batch.

Solution

1. Step 1: Understand the multiple flag in basicAck

   Setting the second parameter of basicAck to true acknowledges all messages up to the given deliveryTag.

2. Step 2: Use batch acknowledgment for efficiency

   After processing 5 messages, calling basicAck(deliveryTag, true) acknowledges all 5 at once, improving performance.

3. Final Answer:

   Call basicAck(deliveryTag, true) after processing the 5th message to acknowledge all previous messages. -> Option C

4. Quick Check:

   Batch ack uses basicAck with multiple=true [OK]

Hint: Use basicAck with multiple=true for batch ack [OK]

Common Mistakes:

• Calling basicAck with multiple=false for batch
• Using autoAck=true when manual control needed
• Confusing basicReject with acknowledgment