What is a message queue in RabbitMQ - Interactive Quiz & Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a queue in RabbitMQ.

RabbitMQ

channel.queue_declare(queue='[1]')

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

Aexchange

Btask_queue

Crouting_key

Dconnection

Attempts:

3 left

💡 Hint

Common Mistakes

Using exchange or routing_key instead of queue name.

The queue_declare method creates or checks a queue named 'task_queue'. This is where messages are stored.

2fill in blank

medium

Complete the code to send a message to the queue.

RabbitMQ

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

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

Aexchange

Bchannel

Cconnection

Dtask_queue

Attempts:

3 left

💡 Hint

Common Mistakes

Using exchange name instead of routing_key.

The routing_key specifies the queue name to send the message to. Here, it is 'task_queue'.

3fill in blank

hard

Fix the error in the code to consume messages from the queue.

RabbitMQ

channel.basic_consume(queue='[1]', on_message_callback=callback, auto_ack=True)

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

Aexchange

Bconnection

Ctask_queue

Dchannel

Attempts:

3 left

💡 Hint

Common Mistakes

Using exchange or connection instead of queue name.

The queue parameter must be the queue name to consume messages from, here 'task_queue'.

4fill in blank

hard

Fill both blanks to create a durable queue and send a persistent message.

RabbitMQ

channel.queue_declare(queue='[1]', durable=[2])
channel.basic_publish(exchange='', routing_key='task_queue', body='Important', properties=pika.BasicProperties(delivery_mode=2))

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

Atask_queue

BTrue

CFalse

Dlogs

Attempts:

3 left

💡 Hint

Common Mistakes

Using False for durable or wrong queue name.

Setting durable=True makes the queue survive server restarts. The queue name is 'task_queue'. The message is marked persistent with delivery_mode=2.

5fill in blank

hard

Fill all three blanks to set up a consumer with manual message acknowledgment.

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=callback, auto_ack=[3])

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

Amethod.delivery_tag

B'task_queue'

CFalse

DTrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using auto_ack=True disables manual ack.

Wrong queue name or missing delivery_tag.

The delivery_tag is used to acknowledge the message manually. The queue is 'task_queue'. Setting auto_ack=False means manual acknowledgment is required.

Practice

1. What is the main purpose of a message queue like RabbitMQ in a system?

easy

A. To safely store messages until the receiver is ready to process them

B. To directly connect two systems without any delay

C. To speed up the CPU processing power

D. To replace the database for storing user data

Solution

1. Step 1: Understand message queue role

   A message queue stores messages temporarily to ensure they are delivered reliably and in order.

2. Step 2: Compare options with message queue function

   Only To safely store messages until the receiver is ready to process them describes storing messages safely until processing, which matches the queue's purpose.

3. Final Answer:

   To safely store messages until the receiver is ready to process them -> Option A

4. Quick Check:

   Message queue purpose = safe message storage [OK]

Hint: Message queues store messages until receivers are ready [OK]

Common Mistakes:

• Thinking message queues speed up CPU
• Confusing message queues with direct connections
• Assuming message queues replace databases

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

easy

A. queue.declare(channel='task_queue')

B. channel.create_queue('task_queue')

C. channel.queue_declare(queue='task_queue')

D. channel.queue('task_queue')

Solution

1. Step 1: Recall RabbitMQ queue declaration syntax

   The correct method to declare a queue is channel.queue_declare with the queue name as a parameter.

2. Step 2: Match options with correct syntax

   Only channel.queue_declare(queue='task_queue') matches the correct method and parameter format.

3. Final Answer:

   channel.queue_declare(queue='task_queue') -> Option C

4. Quick Check:

   Queue declaration syntax = channel.queue_declare [OK]

Hint: Remember method name: queue_declare on channel object [OK]

Common Mistakes:

• Using create_queue instead of queue_declare
• Swapping parameter order
• Calling queue as a method directly

3. Given this Python code snippet using RabbitMQ, what will be printed?

import pika
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(' [x] Sent Hello World!')

medium

A. Hello World!

B. [x] Sent Hello World!

C. Error: queue not declared

D. No output

Solution

1. Step 1: Analyze code execution flow

   The code connects to RabbitMQ, declares a queue, publishes a message, then prints a confirmation string.

2. Step 2: Identify printed output

   The print statement outputs ' [x] Sent Hello World!' exactly as shown.

3. Final Answer:

   [x] Sent Hello World! -> Option B

4. Quick Check:

   Print statement output = ' [x] Sent Hello World!' [OK]

Hint: Look for print() statements for output, not message body [OK]

Common Mistakes:

• Confusing message body with printed output
• Assuming error without checking queue declaration
• Ignoring print statement

4. In this RabbitMQ code snippet, what is the error?

channel.basic_publish(exchange='', routing_key='task_queue', body='Task')

medium

A. Missing queue declaration before publishing

B. Incorrect exchange name

C. routing_key should be exchange name

D. body parameter should be bytes, not string

Solution

1. Step 1: Check message body type requirement

   RabbitMQ expects the message body as bytes, not a plain string.

2. Step 2: Validate other parameters

   Exchange can be empty string for default, routing_key is queue name, so those are correct.

3. Final Answer:

   body parameter should be bytes, not string -> Option D

4. Quick Check:

   Message body must be bytes [OK]

Hint: Message body must be bytes, encode strings before sending [OK]

Common Mistakes:

• Ignoring data type of message body
• Assuming exchange name must be non-empty
• Confusing routing_key with exchange

5. You want to design a system using RabbitMQ to handle user requests that may arrive faster than they can be processed. Which design choice best ensures no requests are lost and processing happens smoothly?

hard

A. Use a durable queue with message acknowledgments and multiple consumers

B. Send requests directly to consumers without queueing

C. Use a non-durable queue and no acknowledgments for speed

D. Store requests only in a database, not in RabbitMQ

Solution

1. Step 1: Identify requirements for reliability and smooth processing

   To avoid losing requests, queues must be durable and messages acknowledged after processing.

2. Step 2: Choose design that supports scaling and reliability

   Multiple consumers allow parallel processing, and durable queues with acknowledgments ensure messages persist and are not lost.

3. Final Answer:

   Use a durable queue with message acknowledgments and multiple consumers -> Option A

4. Quick Check:

   Durable queue + ack + consumers = reliable processing [OK]

Hint: Durable queues + ack + multiple consumers = no lost messages [OK]

Common Mistakes:

• Using non-durable queues causing message loss
• Skipping acknowledgments leading to lost messages
• Not scaling consumers causing backlog