Direct exchange in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does a direct exchange route messages in RabbitMQ?

In RabbitMQ, a direct exchange routes messages based on which of the following?

A The message header contains a matching key-value pair

B The exchange randomly selects a queue to send the message

C The message is broadcast to all queues regardless of keys

D The routing key exactly matches the binding key of the queue

💡 Hint

Think about how direct exchanges use routing keys to deliver messages.

A direct exchange delivers messages to queues where the routing key exactly matches the queue's binding key. This allows precise routing.

💻 Command Output

intermediate

What is the output of binding a queue with a routing key?

Given the RabbitMQ command below, what is the expected result?

rabbitmqadmin declare binding source=direct_logs destination=my_queue routing_key=error

A The queue 'my_queue' will receive all messages from 'direct_logs' exchange regardless of routing key

B The queue 'my_queue' will receive messages sent to 'direct_logs' exchange with routing key 'error'

C The command will fail because 'routing_key' is not valid in binding declaration

D The queue 'my_queue' will receive messages only if the exchange type is 'fanout'

💡 Hint

Consider what binding with a routing key does in a direct exchange.

Binding a queue with a routing key means the queue receives messages from the exchange only if the message's routing key matches the binding key.

🔀 Workflow

advanced

Order the steps to set up a direct exchange with a queue and binding

Arrange the following steps in the correct order to set up a direct exchange named 'logs', a queue named 'error_logs', and bind them with routing key 'error'.

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Think about what must exist before binding and publishing.

You must first declare the exchange, then the queue, then bind them before publishing messages.

❓ Troubleshoot

advanced

Why does a queue not receive messages from a direct exchange?

You have a direct exchange 'logs' and a queue 'info_logs' bound with routing key 'info'. You publish a message with routing key 'warning' but 'info_logs' does not receive it. Why?

A Because the routing key 'warning' does not match the binding key 'info'

B Because the queue 'info_logs' is not declared

C Because the message was published to the wrong exchange type

D Because direct exchanges broadcast messages to all queues regardless of routing key

💡 Hint

Recall how direct exchanges route messages based on routing keys.

Direct exchanges deliver messages only to queues with matching binding keys. Since 'warning' ≠ 'info', the queue does not get the message.

✅ Best Practice

expert

Which practice ensures reliable message delivery with direct exchanges?

When using a direct exchange in RabbitMQ, which practice best ensures that messages are not lost if the consumer is temporarily offline?

A Declare the queue as durable and publish messages as persistent

B Use a non-durable queue and transient messages for faster delivery

C Bind multiple queues with different routing keys to the exchange

D Publish messages without specifying a routing key to reach all queues

💡 Hint

Think about how RabbitMQ handles message durability and persistence.

Declaring queues as durable and publishing persistent messages ensures messages survive broker restarts and are stored until consumed.

Practice

1. What is the main behavior of a direct exchange in RabbitMQ?

easy

A. It broadcasts messages to all queues regardless of routing keys.

B. It routes messages based on pattern matching of routing keys.

C. It routes messages to queues with an exact matching routing key.

D. It stores messages without routing them to any queue.

Solution

1. Step 1: Understand direct exchange routing

   A direct exchange routes messages only to queues whose binding key exactly matches the message's routing key.

2. Step 2: Compare with other exchange types

   Unlike fanout (broadcast) or topic (pattern matching) exchanges, direct exchange requires exact key match.

3. Final Answer:

   It routes messages to queues with an exact matching routing key. -> Option C

4. Quick Check:

   Direct exchange = exact routing key match [OK]

Hint: Direct exchange matches routing keys exactly [OK]

Common Mistakes:

• Confusing direct with fanout exchange behavior
• Thinking direct exchange uses pattern matching
• Assuming messages go to all queues regardless of keys

2. Which of the following is the correct way to declare a direct exchange named logs_direct using RabbitMQ's command line tool rabbitmqadmin?

easy

A. rabbitmqadmin add exchange logs_direct type=fanout

B. rabbitmqadmin declare exchange name=logs_direct type=direct

C. rabbitmqadmin create exchange logs_direct direct

D. rabbitmqadmin declare exchange logs_direct type=topic

Solution

1. Step 1: Recall rabbitmqadmin syntax for exchange declaration

   The correct syntax is: rabbitmqadmin declare exchange name=EXCHANGE_NAME type=EXCHANGE_TYPE

2. Step 2: Match the command to declare a direct exchange named logs_direct

   rabbitmqadmin declare exchange name=logs_direct type=direct matches the syntax and specifies type=direct correctly.

3. Final Answer:

   rabbitmqadmin declare exchange name=logs_direct type=direct -> Option B

4. Quick Check:

   rabbitmqadmin declare exchange + name + type=direct [OK]

Hint: Use 'declare exchange name=... type=direct' syntax [OK]

Common Mistakes:

• Using 'create' instead of 'declare'
• Wrong exchange type like fanout or topic
• Missing 'name=' before exchange name

3. Given a direct exchange ex_direct with two queues bound: queue1 with routing key info and queue2 with routing key error. If a message is published with routing key info, which queues will receive the message?

medium

A. Only queue1

B. Only queue2

C. Both queue1 and queue2

D. No queue receives the message

Solution

1. Step 1: Identify bindings and routing keys

   queue1 is bound with routing key 'info', queue2 with 'error'. The message has routing key 'info'.

2. Step 2: Apply direct exchange routing rule

   Direct exchange routes messages only to queues with exact matching routing keys. So only queue1 matches.

3. Final Answer:

   Only queue1 -> Option A

4. Quick Check:

   Message routing key = queue binding key [OK]

Hint: Message goes only to queues with exact routing key match [OK]

Common Mistakes:

• Assuming message goes to all queues
• Confusing routing keys with patterns
• Thinking queue2 also receives message

4. You declared a direct exchange and bound a queue with routing key task. However, messages published with routing key tasks are not received by the queue. What is the most likely cause?

medium

A. Message payload is empty

B. Exchange type is incorrectly set to fanout

C. Queue is not declared properly

D. Routing key mismatch between binding and message

Solution

1. Step 1: Check routing key binding and message key

   The queue is bound with routing key 'task' but messages are sent with 'tasks'. These keys differ.

2. Step 2: Understand direct exchange routing behavior

   Direct exchange requires exact routing key match. A mismatch means the message won't be routed to the queue.

3. Final Answer:

   Routing key mismatch between binding and message -> Option D

4. Quick Check:

   Exact routing key match needed [OK]

Hint: Check routing keys for exact spelling match [OK]

Common Mistakes:

• Assuming fanout exchange routes by keys
• Blaming queue declaration without checking keys
• Thinking empty payload blocks routing

5. You have a direct exchange ex_direct with three queues bound: Q1 with routing key red, Q2 with routing key blue, and Q3 with routing key red. If you publish a message with routing key red, which queues receive the message and why?

hard

A. Q1 and Q3 both receive it because they share the same routing key

B. No queue receives it because multiple bindings cause conflict

C. Only Q3 receives it because it was bound last

D. Only Q1 receives it because it was bound first

Solution

1. Step 1: Identify queues bound with routing key 'red'

   Q1 and Q3 are both bound with routing key 'red'. Q2 is bound with 'blue'.

2. Step 2: Apply direct exchange routing logic

   Direct exchange routes messages to all queues with matching routing keys. So both Q1 and Q3 receive the message.

3. Final Answer:

   Q1 and Q3 both receive it because they share the same routing key -> Option A

4. Quick Check:

   Multiple queues with same key all get message [OK]

Hint: Multiple queues with same key all get messages [OK]

Common Mistakes:

• Thinking only one queue receives the message
• Assuming binding order affects routing
• Believing multiple bindings cause conflicts