Message durability and persistence in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding message durability in RabbitMQ

Which statement best describes the role of message durability in RabbitMQ?

A Durable messages are stored only in memory and lost on broker restart.

B Durable messages survive broker restarts only if the queue is durable.

C Durable messages automatically replicate to all consumers.

D Durable messages are deleted immediately after being consumed.

💡 Hint

Think about what happens to messages when RabbitMQ restarts.

Durable messages are saved to disk and survive broker restarts only if the queue they are in is also durable.

💻 Command Output

intermediate

Result of publishing a non-persistent message to a durable queue

What happens when you publish a non-persistent message to a durable queue and then restart RabbitMQ?

RabbitMQ

rabbitmqadmin publish routing_key=test_queue payload='Hello' delivery_mode=1
# Then restart RabbitMQ server

A The message is duplicated after restart.

B The message is saved and delivered after restart.

C The message is lost after restart.

D RabbitMQ throws an error on publishing.

💡 Hint

Consider what delivery_mode=1 means for message persistence.

Delivery mode 1 means non-persistent message; such messages are not saved to disk even if the queue is durable, so they are lost on restart.

❓ Configuration

advanced

Correct queue declaration for durable message persistence

Which RabbitMQ queue declaration ensures messages are durable and survive broker restarts?

RabbitMQ

channel.queue_declare(queue='task_queue', durable=___)

A True

B False

C None

D 0

💡 Hint

Durable queues require a specific boolean value.

Setting durable=True makes the queue survive broker restarts, allowing durable messages to persist.

🔀 Workflow

advanced

Ensuring message persistence in a RabbitMQ workflow

Which sequence of steps correctly ensures that messages are persistent and survive RabbitMQ restarts?

A Declare queue with durable=True, publish messages with delivery_mode=2, restart broker

B Declare queue with durable=True, publish messages with delivery_mode=1, restart broker

C Declare queue with durable=False, publish messages with delivery_mode=2, restart broker

D Declare queue with durable=False, publish messages with delivery_mode=1, restart broker

💡 Hint

Both queue and message must be durable for persistence.

Only durable queues combined with persistent messages (delivery_mode=2) ensure messages survive restarts.

❓ Troubleshoot

expert

Diagnosing lost messages despite durable queue and persistent messages

You declared a durable queue and published messages with delivery_mode=2, but messages are lost after RabbitMQ restarts. What is the most likely cause?

A The messages were published with the wrong routing key.

B The messages were consumed before the restart, so none remained.

C The RabbitMQ server was not properly restarted.

D The queue was declared after messages were published, so it was recreated as non-durable.

💡 Hint

Consider the timing of queue declaration relative to message publishing.

If the queue is redeclared without durable=True after messages are published, the queue is recreated as non-durable, causing message loss on restart.