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.