Handling consumer failures in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens when a RabbitMQ consumer crashes without acknowledging a message?

Imagine a RabbitMQ consumer receives a message but crashes before sending an acknowledgment. What will RabbitMQ do with that message?

A The message remains unacknowledged and will be redelivered to another consumer after the connection closes.

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

C RabbitMQ automatically deletes the queue to prevent message loss.

D The message is acknowledged automatically by RabbitMQ to avoid blocking.

💡 Hint

Think about how RabbitMQ ensures messages are not lost when consumers fail.

RabbitMQ waits for an explicit acknowledgment from the consumer. If the consumer crashes before acknowledging, RabbitMQ will requeue the message and deliver it to another consumer once the connection closes.

💻 Command Output

intermediate

What is the output of this RabbitMQ consumer log snippet after a consumer failure?

Given the following log lines from a RabbitMQ consumer process:

2024-06-01 10:00:00 Consumer connected to queue 'task_queue'
2024-06-01 10:00:05 Received message: 'Process data'
2024-06-01 10:00:06 Consumer crashed unexpectedly
2024-06-01 10:00:07 Message requeued for delivery

What does the last line indicate?

A The message was acknowledged before the crash.

B The message was put back into the queue for another consumer.

C The message was lost due to the crash.

D The queue was deleted after the crash.

💡 Hint

Look for the meaning of 'requeued' in message queues.

'Message requeued for delivery' means the message was not lost but placed back into the queue to be delivered again.

❓ Configuration

advanced

Which RabbitMQ consumer configuration ensures messages are not lost if the consumer crashes?

Choose the correct consumer configuration snippet that guarantees message acknowledgment is manual and messages are requeued on failure.

A channel.basic_consume(queue='task_queue', auto_ack=False, on_message_callback=callback)

B channel.basic_consume(queue='task_queue', auto_ack=True, on_message_callback=callback)

C channel.basic_consume(queue='task_queue', auto_ack=True, exclusive=True)

D channel.basic_consume(queue='task_queue', no_ack=True, on_message_callback=callback)

💡 Hint

Consider how automatic acknowledgment affects message safety.

Setting auto_ack=False means the consumer must explicitly acknowledge messages. If the consumer crashes before acknowledgment, RabbitMQ will requeue the message.

❓ Troubleshoot

advanced

Why does a RabbitMQ queue keep growing even though consumers are running?

You notice that the message count in a RabbitMQ queue keeps increasing despite consumers being connected. Which of the following is the most likely cause?

A Consumers have <code>auto_ack=True</code> and messages are acknowledged immediately.

B The queue is set to <code>exclusive=True</code>, preventing message delivery.

C RabbitMQ automatically deletes messages after consumer failure.

D Consumers are crashing before acknowledging messages, causing messages to be requeued repeatedly.

💡 Hint

Think about what happens if messages are never acknowledged.

If consumers crash before acknowledging, messages remain unacknowledged and get requeued, causing the queue size to grow.

🔀 Workflow

expert

Order the steps RabbitMQ follows when a consumer fails before acknowledging a message

Put these RabbitMQ steps in the correct order when a consumer crashes before acknowledging a message.

A 2,1,3,4

B 1,3,2,4

C 1,2,3,4

D 1,2,4,3

💡 Hint

Think about the natural sequence of events from message receipt to requeue.

The consumer first receives the message, then crashes before acknowledgment. RabbitMQ detects the closed connection and requeues the message.