Default exchange behavior in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the Default Exchange Routing

In RabbitMQ, what happens when a message is published to the default exchange with a routing key matching a queue name?

A The message is routed directly to the queue with the name equal to the routing key.

B The message is broadcast to all queues regardless of the routing key.

C The message is discarded because the default exchange does not route messages.

D The message is routed to a queue with a name that partially matches the routing key.

💡 Hint

Think about how the default exchange uses the routing key as the queue name.

The default exchange in RabbitMQ is a direct exchange with no name. It routes messages to the queue whose name exactly matches the routing key.

💻 Command Output

intermediate

Result of Publishing to Default Exchange

Given a queue named task_queue exists, what is the output or effect of running this command?

rabbitmqadmin publish exchange= routing_key=task_queue payload='Hello'

A The message is discarded silently.

B The message 'Hello' is delivered to the 'task_queue' queue.

C The message is sent to all queues bound to the default exchange.

D An error occurs because the exchange name is empty.

💡 Hint

The default exchange is identified by an empty string as its name.

Using an empty string for the exchange name targets the default exchange, which routes messages to the queue named by the routing key.

❓ Troubleshoot

advanced

Why is my message not delivered when using the default exchange?

You published a message to the default exchange with routing key my_queue, but the message does not appear in the queue. Which of the following is the most likely cause?

A Messages to the default exchange require a special header to be delivered.

B The default exchange is disabled by default and must be enabled manually.

C The routing key must be empty when publishing to the default exchange.

D The queue <code>my_queue</code> does not exist or is not declared.

💡 Hint

The default exchange routes only to queues that exist with the exact routing key name.

If the queue named by the routing key does not exist, the message cannot be routed and is dropped or returned depending on settings.

🔀 Workflow

advanced

Sequence to Bind a Queue to the Default Exchange

Which sequence correctly describes how to send a message to a queue using the default exchange in RabbitMQ?

A 4,1,2,3

B 1,4,2,3

C 4,2,1,3

D 1,3,4,2

💡 Hint

Think about what must be ready before declaring queues and publishing messages.

The server must be running first, then the queue declared, then messages published, and finally consumers started to receive messages.

✅ Best Practice

expert

Best Practice for Using the Default Exchange in Production

Which practice is recommended when using the default exchange in a production RabbitMQ environment?

A Use the default exchange exclusively to simplify routing logic.

B Bind multiple queues to the default exchange with the same routing key for load balancing.

C Avoid using the default exchange for complex routing; use named exchanges instead.

D Disable the default exchange to prevent accidental message loss.

💡 Hint

Consider scalability and routing flexibility in production systems.

The default exchange only routes by exact queue name, limiting routing flexibility. Named exchanges allow more complex routing patterns.