Publishing messages in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this RabbitMQ publish command?

You run the following command to publish a message to a RabbitMQ queue named task_queue. What is the expected output or result?

RabbitMQ

rabbitmqadmin publish routing_key=task_queue payload='Hello World!'

A Message published but returned an error code 500

B Error: Queue 'task_queue' does not exist

C Syntax error: missing exchange parameter

D Message published successfully with no output

💡 Hint

The default exchange is used if no exchange is specified, so the message goes directly to the queue.

When you publish a message with rabbitmqadmin without specifying an exchange, it uses the default exchange which routes messages to the queue named by the routing key. If the queue exists, the message is accepted silently.

🧠 Conceptual

intermediate

Which RabbitMQ exchange type routes messages to all bound queues?

You want to send a message that all queues bound to an exchange will receive. Which exchange type should you use?

A Direct exchange

B Topic exchange

C Fanout exchange

D Headers exchange

💡 Hint

Think of a loudspeaker broadcasting to everyone.

A fanout exchange routes messages to all queues bound to it, ignoring routing keys. This is like broadcasting to all listeners.

❓ Configuration

advanced

Which configuration snippet correctly declares a durable queue and publishes a persistent message?

You want to ensure that your queue survives RabbitMQ restarts and that messages are not lost. Which configuration snippet achieves this?

A

queue_declare(queue='task_queue', durable=False)
publish(exchange='', routing_key='task_queue', body='data', properties={'delivery_mode': 1})

B

queue_declare(queue='task_queue', durable=True)
publish(exchange='', routing_key='task_queue', body='data', properties={'delivery_mode': 2})

C

queue_declare(queue='task_queue')
publish(exchange='', routing_key='task_queue', body='data')

D

queue_declare(queue='task_queue', durable=True)
publish(exchange='', routing_key='task_queue', body='data', properties={'delivery_mode': 1})

💡 Hint

Durable queues and persistent messages require specific flags.

Setting durable=True makes the queue survive restarts. Setting delivery_mode=2 marks messages as persistent so they are saved to disk.

❓ Troubleshoot

advanced

Why does this publish command fail with a channel error?

You run this command: rabbitmqadmin publish exchange=logs routing_key=info payload='Test' But it fails with a channel error. What is the most likely cause?

A The exchange 'logs' does not exist

B The routing key 'info' is invalid syntax

C The payload is missing required headers

D The rabbitmqadmin tool is outdated

💡 Hint

Check if the exchange you are publishing to exists.

Publishing to a non-existent exchange causes a channel error because RabbitMQ cannot route the message.

🔀 Workflow

expert

What is the correct sequence to publish a message with confirmation in RabbitMQ?

Arrange the steps in the correct order to publish a message and confirm it was received by RabbitMQ.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 2,3,1,4

💡 Hint

You must enable confirms before publishing.

First enable confirms, then publish, then wait for ack/nack, then handle errors if any.