Message queue use cases in RabbitMQ - Interactive Code 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'

A"task_queue"

Btask_queue

Cqueue_name

Dqueue

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the queue name.

The queue name must be a string enclosed in quotes.

2fill in blank

medium

Complete the code to publish a message to a queue.

RabbitMQ

channel.basic_publish(exchange='', routing_key=[1], body=message)

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

A""

Bmessage

C"task_queue"

Dexchange

Attempts:

3 left

💡 Hint

Common Mistakes

Using empty string or variable instead of queue name.

The routing_key should be the queue name as a string.

3fill in blank

hard

Fix the error in the consumer callback function to acknowledge message receipt.

RabbitMQ

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

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

Amethod.delivery_tag

Bbody

Cproperties.delivery_tag

Dch.delivery_tag

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong parameter for delivery_tag.

The delivery_tag is accessed from the method parameter to acknowledge the message.

4fill in blank

hard

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

RabbitMQ

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

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

ATrue

Bpika.BasicProperties(delivery_mode=2)

CFalse

Dpika.BasicProperties(delivery_mode=1)

Attempts:

3 left

💡 Hint

Common Mistakes

Setting durable to False or missing delivery_mode=2.

Durable queues survive server restarts and persistent messages are marked with delivery_mode=2.

5fill in blank

hard

Fill all three blanks to set up a fanout exchange and bind a queue to it.

RabbitMQ

channel.exchange_declare(exchange=[1], exchange_type=[2])
channel.queue_bind(exchange=[3], queue='logs')

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

A"logs"

B"fanout"

C"logs_exchange"

D"direct"

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong exchange type or mismatched exchange names.

The exchange is named 'logs_exchange' with type 'fanout'. The queue is bound to the same exchange.

Practice

1. What is a primary use case of a message queue like RabbitMQ in system design?

easy

A. To enable asynchronous communication between different parts of a system

B. To store large amounts of data permanently

C. To directly serve web pages to users

D. To replace a database for all data storage needs

Solution

1. Step 1: Understand message queue purpose

   Message queues allow parts of a system to send messages without waiting for immediate response, enabling asynchronous communication.

2. Step 2: Compare options with message queue role

   Storing large data, serving web pages, or replacing databases are not typical message queue roles.

3. Final Answer:

   To enable asynchronous communication between different parts of a system -> Option A

4. Quick Check:

   Message queue = asynchronous communication [OK]

Hint: Message queues help parts talk without waiting [OK]

Common Mistakes:

• Thinking message queues store data permanently
• Confusing message queues with web servers
• 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('task_queue', durable=False)

B. channel.create_queue('task_queue', persistent=True)

C. channel.queue_declare(queue='task_queue', durable=True)

D. channel.queue('task_queue', durable=True)

Solution

1. Step 1: Recall RabbitMQ queue declaration syntax

   The correct method is channel.queue_declare with parameters like queue and durable.

2. Step 2: Check each option's method and parameters

   Only channel.queue_declare(queue='task_queue', durable=True) uses the correct method name and parameters. Others use incorrect method names or parameters.

3. Final Answer:

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

4. Quick Check:

   Correct method is queue_declare with queue and durable [OK]

Hint: Use channel.queue_declare with queue name and durable flag [OK]

Common Mistakes:

• Using wrong method names like create_queue
• Confusing parameter names like persistent instead of durable
• Omitting the channel object

3. Given the following RabbitMQ setup, what will happen if the consumer is slower than the producer?

channel.queue_declare(queue='jobs')
for i in range(10):
    channel.basic_publish(exchange='', routing_key='jobs', body=f'job-{i}')
# Consumer processes messages one by one slowly

medium

A. Messages will be lost if consumer is slow

B. Producer will block and wait for consumer to finish each message

C. Consumer will skip messages if it is slow

D. Messages will queue up in RabbitMQ until the consumer processes them

Solution

1. Step 1: Understand RabbitMQ message flow

   RabbitMQ stores messages in the queue until consumers process them, allowing producers to send messages quickly.

2. Step 2: Analyze slow consumer effect

   If consumer is slow, messages accumulate in the queue, waiting to be processed, not lost or skipped.

3. Final Answer:

   Messages will queue up in RabbitMQ until the consumer processes them -> Option D

4. Quick Check:

   Slow consumer = messages queue up [OK]

Hint: Slow consumer causes message backlog in queue [OK]

Common Mistakes:

• Assuming producer blocks on slow consumer
• Thinking messages get lost automatically
• Believing consumer skips messages if slow

4. A developer wrote this RabbitMQ consumer code but it never receives messages:

channel.queue_declare(queue='tasks')
channel.basic_consume(queue='task', on_message_callback=callback, auto_ack=True)
channel.start_consuming()

What is the likely problem?

medium

A. Queue name mismatch between declare and consume calls

B. Missing call to channel.queue_declare

C. auto_ack should be False to receive messages

D. Callback function is not defined

Solution

1. Step 1: Compare queue names in declare and consume

   The queue is declared as 'tasks' but consumed from 'task' - names differ.

2. Step 2: Understand effect of queue name mismatch

   Consumer listens on a different queue than the one declared, so it receives no messages.

3. Final Answer:

   Queue name mismatch between declare and consume calls -> Option A

4. Quick Check:

   Queue names must match to receive messages [OK]

Hint: Check queue names match exactly in declare and consume [OK]

Common Mistakes:

• Ignoring queue name spelling differences
• Thinking auto_ack affects receiving messages
• Assuming callback must be defined to start consuming

5. You want to design a system using RabbitMQ to handle image processing tasks that may take time. Which approach best uses message queues to improve system scalability and reliability?

hard

A. Use RabbitMQ only for logging, not for task processing

B. Send image processing requests to a durable queue and have multiple worker consumers process them asynchronously

C. Store images in the queue and process them only when the queue is empty

D. Process images immediately in the web server without queues to reduce latency

Solution

1. Step 1: Identify system needs for scalability and reliability

   Image processing tasks are time-consuming and benefit from asynchronous handling and multiple workers.

2. Step 2: Match RabbitMQ use case to system design

   Using a durable queue with multiple consumers allows tasks to be processed reliably and in parallel, improving scalability.

3. Final Answer:

   Send image processing requests to a durable queue and have multiple worker consumers process them asynchronously -> Option B

4. Quick Check:

   Durable queue + multiple workers = scalable, reliable processing [OK]

Hint: Use durable queues and multiple workers for heavy tasks [OK]

Common Mistakes:

• Processing tasks synchronously in web server
• Storing large data directly in queues
• Using message queues only for logging