Publish-subscribe for broadcasting in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does the publish-subscribe pattern work in RabbitMQ?

In RabbitMQ, what is the main role of the exchange in the publish-subscribe pattern?

A It receives messages from producers and routes them to queues based on binding rules.

B It stores messages until consumers retrieve them directly from the exchange.

C It acts as a consumer that processes messages and sends acknowledgments.

D It deletes messages after they are published to prevent duplicates.

💡 Hint

Think about how messages get from the sender to multiple receivers.

The exchange receives messages from producers and routes them to one or more queues based on binding rules. This allows multiple consumers to receive copies of the message.

💻 Command Output

intermediate

Output of binding a queue to a fanout exchange

What is the output of the following RabbitMQ command when binding a queue named logs to a fanout exchange named broadcast?

rabbitmqadmin declare binding source=broadcast destination=logs

A {"result": "success", "source": "broadcast", "destination": "logs"}

B SyntaxError: missing required parameter 'routing_key'

C Error: exchange 'broadcast' does not exist

D Warning: fanout exchange ignores routing_key parameter

💡 Hint

Fanout exchanges do not require a routing key when binding queues.

Binding a queue to a fanout exchange succeeds without a routing key. The command returns a success JSON with source and destination.

🔀 Workflow

advanced

Correct order to set up publish-subscribe with RabbitMQ fanout exchange

Arrange the steps in the correct order to set up a publish-subscribe system using a fanout exchange in RabbitMQ.

A 3,2,1,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about declaring resources before using them.

You first declare the exchange, then create queues, bind them to the exchange, and finally publish messages.

❓ Troubleshoot

advanced

Why are subscribers not receiving messages in a fanout exchange setup?

You set up a fanout exchange and bound multiple queues to it. However, subscribers connected to these queues do not receive any messages. What is the most likely cause?

A The queues were declared as exclusive and deleted when the publisher disconnected.

B The exchange type was set to direct instead of fanout.

C The queues were not bound to the exchange.

D The routing key was missing when publishing messages.

💡 Hint

Check if the queues are connected to the exchange properly.

If queues are not bound to the exchange, messages published to the exchange have nowhere to go, so subscribers receive nothing.

✅ Best Practice

expert

Best practice for durable publish-subscribe setup in RabbitMQ

Which option describes the best practice to ensure messages are not lost in a publish-subscribe system using RabbitMQ fanout exchanges?

A Declare queues as exclusive and auto-delete to clean up resources automatically.

B Declare the exchange and queues as durable and publish messages as persistent.

C Use transient queues and non-persistent messages for faster delivery.

D Publish messages without acknowledgments to reduce latency.

💡 Hint

Think about how to keep messages safe even if RabbitMQ restarts.

Declaring exchanges and queues as durable and publishing persistent messages ensures messages survive broker restarts and are not lost.