Dead letter exchanges and queues in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Dead Letter Exchanges

What is the main purpose of a dead letter exchange (DLX) in RabbitMQ?

A To speed up message delivery by bypassing normal queues

B To automatically delete messages after they are consumed

C To encrypt messages before they reach the consumer

D To route messages that cannot be delivered or are rejected to a special queue for later inspection

💡 Hint

Think about what happens to messages that fail processing or expire.

Dead letter exchanges are used to catch messages that are rejected, expired, or cannot be routed, so they can be inspected or retried later.

💻 Command Output

intermediate

Output of Declaring a Queue with DLX

What is the output or effect of running this RabbitMQ CLI command?

rabbitmqadmin declare queue name=myqueue durable=true arguments='{"x-dead-letter-exchange":"dlx-exchange"}'

A Creates a queue named 'myqueue' but ignores the dead letter exchange argument

B Creates a durable queue named 'myqueue' that sends rejected or expired messages to 'dlx-exchange'

C Fails with a syntax error due to incorrect JSON format in arguments

D Creates a non-durable queue named 'myqueue' without dead letter functionality

💡 Hint

Check how the 'arguments' parameter is used to set dead letter exchange.

The command creates a durable queue with a dead letter exchange set, so messages rejected or expired from 'myqueue' go to 'dlx-exchange'.

🔀 Workflow

advanced

Configuring Dead Letter Queue Workflow

Which sequence of steps correctly sets up a dead letter exchange and queue in RabbitMQ?

A 1,2,3,4

B 3,1,2,4

C 2,1,3,4

D 1,3,2,4

💡 Hint

Think about the order: exchanges and queues must exist before binding and usage.

You must first create the DLX, then the DLQ and bind it, then configure the main queue to use the DLX, and finally publish messages.

❓ Troubleshoot

advanced

Troubleshooting Missing Dead Letter Messages

You configured a queue with a dead letter exchange, but messages rejected from the queue do not appear in the dead letter queue. What is a likely cause?

A The dead letter queue is not bound to the dead letter exchange with the correct routing key

B The main queue is not durable

C The dead letter exchange type is set to 'fanout'

D The messages are not published as persistent

💡 Hint

Check bindings between exchange and queue carefully.

If the dead letter queue is not bound correctly to the dead letter exchange, messages sent to the DLX will not be routed to the DLQ.

✅ Best Practice

expert

Best Practice for Handling Poison Messages

What is the best practice for handling poison messages (messages that always fail processing) in a RabbitMQ dead letter queue setup?

A Re-publish poison messages endlessly to the main queue to retry processing

B Automatically delete poison messages from the dead letter queue to save space

C Set a maximum retry count and move poison messages to a separate queue for manual inspection

D Ignore poison messages and let them accumulate in the dead letter queue

💡 Hint

Think about how to avoid infinite retry loops and keep the system healthy.

Setting a retry limit and isolating poison messages prevents infinite loops and allows manual debugging or fixing.