Why exchanges route messages to queues in RabbitMQ - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a topic exchange named 'logs'.

RabbitMQ

channel.exchange_declare(exchange='[1]', exchange_type='topic')

Drag options to blanks, or click blank then click option'

Amessages

Bqueue

Clogs

Ddirect

Attempts:

3 left

💡 Hint

Common Mistakes

Using exchange type instead of exchange name

Using queue name instead of exchange name

The exchange name is 'logs' as declared in the code.

2fill in blank

medium

Complete the code to bind the queue 'error_logs' to the exchange 'logs' with routing key 'error'.

RabbitMQ

channel.queue_bind(queue='error_logs', exchange='logs', routing_key='[1]')

Drag options to blanks, or click blank then click option'

Ainfo

Bwarning

Cdebug

Derror

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong routing key like 'info' or 'debug'

The routing key 'error' binds the queue to receive error messages.

3fill in blank

hard

Fix the error in the code to publish a message with routing key 'info' to the exchange 'logs'.

RabbitMQ

channel.basic_publish(exchange='logs', routing_key='[1]', body='System started')

Drag options to blanks, or click blank then click option'

Ainfo

Berror

Cwarning

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using routing key that does not match queue bindings

The routing key must match the intended message type, here 'info'.

4fill in blank

hard

Fill both blanks to create a binding where the queue 'all_logs' receives all messages regardless of routing key.

RabbitMQ

channel.queue_bind(queue='all_logs', exchange='logs', routing_key='[1]')
channel.basic_publish(exchange='logs', routing_key='[2]', body='Test message')

Drag options to blanks, or click blank then click option'

B*

C#

Dall

Attempts:

3 left

💡 Hint

Common Mistakes

Using '*' which matches only one word

Using empty string which matches no keys

The routing key '#' matches all routing keys, so the queue receives all messages.

5fill in blank

hard

Fill all three blanks to create a topic exchange 'topic_logs', bind queue 'kern_logs' to routing key 'kern.*', and publish a message with routing key 'kern.critical'.

RabbitMQ

channel.exchange_declare(exchange='[1]', exchange_type='topic')
channel.queue_bind(queue='kern_logs', exchange='topic_logs', routing_key='[2]')
channel.basic_publish(exchange='topic_logs', routing_key='[3]', body='Kernel critical error')

Drag options to blanks, or click blank then click option'

Atopic_logs

Bkern.*

Ckern.critical

Ddirect_logs

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong exchange name

Using incorrect routing key patterns

The exchange is 'topic_logs' of type 'topic'. The queue binds to 'kern.*' to receive all kernel messages. The message is published with routing key 'kern.critical'.

Practice

1. Why do RabbitMQ exchanges route messages to queues?

easy

A. To convert messages into a different format

B. To store messages permanently in the exchange

C. To deliver messages to the correct queues based on routing rules

D. To delete messages after receiving them

Solution

1. Step 1: Understand the role of exchanges

   Exchanges receive messages from producers and decide where to send them.

2. Step 2: Understand routing to queues

   Exchanges route messages to queues based on bindings and routing keys to ensure correct delivery.

3. Final Answer:

   To deliver messages to the correct queues based on routing rules -> Option C

4. Quick Check:

   Exchanges route messages to queues = D [OK]

Hint: Exchanges send messages to queues using routing rules [OK]

Common Mistakes:

• Thinking exchanges store messages permanently
• Believing exchanges delete messages
• Assuming exchanges change message format

2. Which of the following is the correct way to bind a queue named myQueue to an exchange named myExchange in RabbitMQ?

easy

A. channel.queue_bind(queue='myQueue', exchange='myExchange')

B. queue.bind(exchange='myExchange', queue='myQueue')

C. exchange.bind(queue='myQueue', exchange='myExchange')

D. channel.bind_queue(exchange='myExchange', queue='myQueue')

Solution

1. Step 1: Recall RabbitMQ binding syntax

   The correct method to bind a queue to an exchange is channel.queue_bind(queue, exchange).

2. Step 2: Match the correct parameter order and method

   channel.queue_bind(queue='myQueue', exchange='myExchange') uses channel.queue_bind(queue='myQueue', exchange='myExchange'), which is correct syntax.

3. Final Answer:

   channel.queue_bind(queue='myQueue', exchange='myExchange') -> Option A

4. Quick Check:

   Correct binding syntax = A [OK]

Hint: Use channel.queue_bind(queue, exchange) to bind queues [OK]

Common Mistakes:

• Using wrong method names like queue.bind or exchange.bind
• Swapping queue and exchange parameters
• Using non-existent methods like bind_queue

3. Given a direct exchange logs and a queue errorQueue bound with routing key error, what happens when a message is published with routing key info?

medium

A. The message is discarded because no queue matches info

B. The message is routed to errorQueue

C. The message is routed to all queues bound to the exchange

D. The message is stored in the exchange

Solution

1. Step 1: Understand direct exchange routing

   A direct exchange routes messages only to queues with matching routing keys.

2. Step 2: Analyze the routing key mismatch

   The queue errorQueue is bound with error, but the message uses info, so no match occurs.

3. Final Answer:

   The message is discarded because no queue matches info -> Option A

4. Quick Check:

   Direct exchange routes only matching keys = A [OK]

Hint: Direct exchange routes only matching keys; others are discarded [OK]

Common Mistakes:

• Assuming message goes to all queues
• Thinking message is stored in exchange
• Believing message routes despite key mismatch

4. You have a topic exchange topicLogs and a queue queue1 bound with routing key kern.*. A message with routing key kern.error is not delivered to queue1. What is the likely cause?

medium

A. The binding key kern.* does not match kern.error

B. The queue queue1 is not bound correctly to the exchange

C. The message payload is empty

D. The exchange type is not set to topic

Solution

1. Step 1: Verify exchange type for topic routing

   Topic routing keys like kern.* work only if the exchange type is set to topic.

2. Step 2: Check exchange type mismatch

   If the exchange is not topic type, the binding pattern won't work, causing message delivery failure.

3. Final Answer:

   The exchange type is not set to topic -> Option D

4. Quick Check:

   Topic routing requires topic exchange = C [OK]

Hint: Topic bindings need topic exchange type set correctly [OK]

Common Mistakes:

• Assuming binding key syntax is wrong
• Ignoring exchange type setting
• Blaming empty message payload

5. You want to route messages with routing keys info and warning to queueA, and all other messages to queueB. Which exchange type and binding setup achieves this?

hard

A. Use a direct exchange; bind queueA with keys info, warning; bind queueB with no key

B. Use a topic exchange; bind queueA with keys info, warning; bind queueB with #

C. Use a fanout exchange; bind both queues to the exchange

D. Use a headers exchange; set headers for queueA and queueB

Solution

1. Step 1: Identify routing needs

   Messages with keys info and warning go to queueA, others to queueB.

2. Step 2: Choose exchange type and bindings

   A topic exchange allows binding with specific keys and a catch-all # pattern for queueB.

3. Step 3: Confirm binding setup

   Bind queueA with info and warning, and queueB with # to catch all other keys.

4. Final Answer:

   Use a topic exchange; bind queueA with keys info, warning; bind queueB with # -> Option B

5. Quick Check:

   Topic exchange with specific and catch-all bindings = B [OK]

Hint: Use topic exchange with # for catch-all routing [OK]

Common Mistakes:

• Using direct exchange without catch-all binding
• Using fanout exchange which sends all messages to all queues
• Confusing headers exchange for routing keys