Why RabbitMQ is the most popular message broker - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start the RabbitMQ server using the correct command.

RabbitMQ

sudo systemctl [1] rabbitmq-server

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

Astop

Brestart

Cstart

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stop' instead of 'start' will turn off the service.

Using 'status' only shows the current state but does not start the service.

The command sudo systemctl start rabbitmq-server starts the RabbitMQ service on your system.

2fill in blank

medium

Complete the code to declare a queue named 'task_queue' in RabbitMQ using the correct method.

RabbitMQ

channel.queue_[1]('task_queue', durable=True)

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

Adeclare

Bdelete

Cbind

Dconsume

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' removes the queue instead of creating it.

Using 'consume' is for receiving messages, not declaring queues.

The method queue_declare is used to create or check a queue in RabbitMQ.

3fill in blank

hard

Fix the error in the code to publish a message to the 'task_queue' with persistence.

RabbitMQ

channel.basic_publish(exchange='', routing_key='task_queue', body='Hello World!', properties=[1])

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

Apika.BasicProperties(expiration='60000')

Bpika.BasicProperties(delivery_mode=1)

Cpika.BasicProperties(priority=2)

Dpika.BasicProperties(delivery_mode=2)

Attempts:

3 left

💡 Hint

Common Mistakes

Using delivery_mode=1 sends non-persistent messages that can be lost.

Using priority or expiration does not ensure message persistence.

Setting delivery_mode=2 makes the message persistent, so it is saved to disk.

4fill in blank

hard

Fill both blanks to create a durable queue and ensure messages are persistent.

RabbitMQ

channel.queue_declare(queue='task_queue', [1]=True)
channel.basic_publish(exchange='', routing_key='task_queue', body='Work', properties=[2])

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

Adurable

Bpika.BasicProperties(delivery_mode=2)

Cpika.BasicProperties(delivery_mode=1)

Dexclusive

Attempts:

3 left

💡 Hint

Common Mistakes

Using exclusive instead of durable makes the queue only accessible by one connection.

Using delivery_mode=1 sends non-persistent messages.

Setting durable=True makes the queue survive server restarts, and delivery_mode=2 makes messages persistent.

5fill in blank

hard

Fill all three blanks to consume messages from 'task_queue' with manual acknowledgement.

RabbitMQ

def callback(ch, method, properties, body):
    print(f"Received {body}")
    ch.basic_ack(delivery_tag=[1])

channel.basic_consume(queue=[2], on_message_callback=[3], auto_ack=False)
channel.start_consuming()

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

Amethod.delivery_tag

B'task_queue'

Ccallback

D'task'

Attempts:

3 left

💡 Hint

Common Mistakes

Using auto_ack=True disables manual acknowledgement.

Using wrong queue name causes no messages to be consumed.

The delivery_tag is used to acknowledge the message manually. The queue name is 'task_queue', and the callback function is named 'callback'.

Practice

1. Why is RabbitMQ considered one of the most popular message brokers?

easy

A. Because it is reliable and supports many programming languages

B. Because it only works with one programming language

C. Because it does not support message queuing

D. Because it is difficult to set up and manage

Solution

1. Step 1: Understand RabbitMQ's core features

   RabbitMQ is known for reliability and multi-language support, making it versatile.

2. Step 2: Compare options with known facts

   The options claiming single-language support, lack of queuing support, or setup difficulty contradict these facts, leaving the reliability and multi-language support as correct.

3. Final Answer:

   Because it is reliable and supports many programming languages -> Option A

4. Quick Check:

   Reliability + multi-language = B [OK]

Hint: Pick the option mentioning reliability and language support [OK]

Common Mistakes:

• Choosing options that say RabbitMQ supports only one language
• Thinking RabbitMQ is hard to manage
• Ignoring its message queuing feature

2. Which of the following is the correct way to declare a queue in RabbitMQ using the command line?

easy

A. rabbitmqctl declare_queue myqueue

B. rabbitmqadmin declare queue name=myqueue

C. rabbitmqadmin declare queue name=myqueue durable=true

D. rabbitmqctl create queue myqueue durable

Solution

1. Step 1: Identify the correct RabbitMQ command syntax

   The rabbitmqadmin tool uses the syntax: declare queue name=myqueue durable=true to declare a durable queue.

2. Step 2: Eliminate incorrect commands

   Commands using rabbitmqctl are incorrect for queue declaration; the rabbitmqadmin command missing the durability setting is also wrong.

3. Final Answer:

   rabbitmqadmin declare queue name=myqueue durable=true -> Option C

4. Quick Check:

   Correct command with durability flag = D [OK]

Hint: Look for 'rabbitmqadmin' with 'declare queue' and 'durable=true' [OK]

Common Mistakes:

• Using rabbitmqctl instead of rabbitmqadmin for queue declaration
• Omitting the durable flag when needed
• Incorrect command syntax

3. Given the following Python code using pika library to send a message to RabbitMQ, what will be the output if the connection fails?

import pika
try:
    connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
    channel = connection.channel()
    channel.queue_declare(queue='hello')
    channel.basic_publish(exchange='', routing_key='hello', body='Hello World!')
    print('Message sent')
except Exception as e:
    print(f'Error: {e}')

medium

A. Message sent

B. Error: Connection refused

C. SyntaxError

D. No output

Solution

1. Step 1: Analyze the try-except block

   The code tries to connect to RabbitMQ on localhost. If the server is down, connection fails and raises an exception.

2. Step 2: Understand exception handling output

   The except block catches the exception and prints the error message, e.g., 'Error: Connection refused'.

3. Final Answer:

   Error: Connection refused -> Option B

4. Quick Check:

   Connection failure triggers error print = A [OK]

Hint: Connection failure prints error message in except block [OK]

Common Mistakes:

• Assuming 'Message sent' prints even if connection fails
• Confusing syntax errors with runtime exceptions
• Expecting no output on failure

4. You wrote a RabbitMQ consumer script but it never receives messages. Which of the following is the most likely cause?

medium

A. All of the above

B. The message broker is offline

C. The queue was not declared before consuming

D. The consumer is connected to the wrong queue name

Solution

1. Step 1: Identify common reasons for no message reception

   Not declaring the queue, broker offline, or wrong queue name all prevent message delivery.

2. Step 2: Evaluate options

   Each individual cause listed can prevent reception, so 'All of the above' covers all likely causes.

3. Final Answer:

   All of the above -> Option A

4. Quick Check:

   Multiple causes possible = C [OK]

Hint: If unsure, pick 'All of the above' when all options are valid [OK]

Common Mistakes:

• Ignoring broker offline as a cause
• Assuming queue declaration is automatic
• Not checking queue name spelling

5. You want to ensure messages are not lost even if RabbitMQ crashes. Which combination of features should you use?

hard

A. Temporary queues with no acknowledgments

B. Non-durable queues and non-persistent messages

C. Exclusive queues and auto-delete messages

D. Durable queues and persistent messages

Solution

1. Step 1: Understand durability and persistence

   Durable queues survive broker restarts; persistent messages are saved to disk.

2. Step 2: Match features to message safety

   Only durable queues combined with persistent messages guarantee no message loss on crash.

3. Final Answer:

   Durable queues and persistent messages -> Option D

4. Quick Check:

   Durability + persistence = message safety [OK]

Hint: Durable queues + persistent messages prevent loss [OK]

Common Mistakes:

• Using non-durable queues expecting message safety
• Confusing exclusive or temporary queues with durability
• Ignoring message persistence setting