Work queue for task distribution in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a work queue in RabbitMQ?

A work queue is a way to distribute time-consuming tasks among multiple workers to balance the load and improve performance.

intermediate

How does RabbitMQ ensure tasks are not lost if a worker crashes?

RabbitMQ can mark messages as persistent and use acknowledgments from workers to confirm task completion before removing messages from the queue.

beginner

What is the role of acknowledgments in RabbitMQ work queues?

Acknowledgments tell RabbitMQ that a worker has finished processing a task, so the message can be safely removed from the queue.

beginner

Why use multiple workers with a work queue?

Multiple workers allow tasks to be processed in parallel, speeding up overall processing and preventing any single worker from becoming a bottleneck.

intermediate

What happens if a worker dies before acknowledging a message in RabbitMQ?

The message is re-queued and delivered to another worker to ensure the task is completed.

What does a work queue in RabbitMQ help with?

A Distributing tasks among multiple workers

B Storing data permanently

C Creating user interfaces

D Encrypting messages

Work queues distribute tasks to multiple workers to balance load and improve processing speed.

How does RabbitMQ know a task is done?

A When the worker sends an acknowledgment

B When the message is created

C When the queue is empty

D When the server restarts

Workers send acknowledgments to confirm task completion so RabbitMQ can remove the message.

What happens if a worker crashes before acknowledging a message?

A The message is lost

B The message is deleted

C The message is re-queued for another worker

D The queue stops working

RabbitMQ re-queues unacknowledged messages to ensure tasks are not lost.

Why mark messages as persistent in RabbitMQ work queues?

A To delete messages automatically

B To make messages faster

C To encrypt messages

D To keep messages safe if RabbitMQ restarts

Persistent messages survive RabbitMQ restarts, preventing task loss.

What is the main benefit of using multiple workers with a work queue?

A Slower processing

B Parallel task processing

C More message loss

D Less reliability

Multiple workers process tasks in parallel, speeding up work completion.

Explain how RabbitMQ work queues distribute tasks and handle worker failures.

Think about how tasks move from the queue to workers and what happens if a worker crashes.

Describe the importance of message persistence and acknowledgments in RabbitMQ work queues.

Consider how RabbitMQ keeps tasks safe and confirms they are done.

Practice

1. What is the main purpose of a work queue in RabbitMQ?

easy

A. To create a backup of messages

B. To distribute tasks among multiple workers safely

C. To store user login information

D. To encrypt messages for security

Solution

1. Step 1: Understand the role of work queues

   Work queues are designed to share tasks among many workers so that the workload is balanced and tasks are processed efficiently.

2. Step 2: Eliminate unrelated options

   Storing login info, backing up messages, or encrypting messages are not the primary functions of work queues.

3. Final Answer:

   To distribute tasks among multiple workers safely -> Option B

4. Quick Check:

   Work queue = task distribution [OK]

Hint: Work queues share tasks among workers, not store or encrypt data [OK]

Common Mistakes:

• Confusing work queues with message encryption
• Thinking work queues store user data
• Assuming work queues backup messages automatically

2. Which RabbitMQ queue declaration option makes the queue survive server restarts?

easy

A. durable: true

B. autoDelete: true

C. exclusive: true

D. passive: true

Solution

1. Step 1: Identify durability option

   The 'durable: true' option ensures the queue is saved to disk and survives RabbitMQ server restarts.

2. Step 2: Understand other options

   'autoDelete' removes the queue when no consumers remain, 'exclusive' restricts queue to one connection, and 'passive' checks for queue existence without creating it.

3. Final Answer:

   durable: true -> Option A

4. Quick Check:

   durable = survive restart [OK]

Hint: Durable queues survive restarts; autoDelete removes queues [OK]

Common Mistakes:

• Using autoDelete instead of durable for persistence
• Confusing exclusive with durability
• Thinking passive creates durable queues

3. Given this worker code snippet in Python using pika:

channel.basic_consume(queue='task_queue', on_message_callback=callback, auto_ack=False)
channel.start_consuming()

What happens if the worker crashes before sending an acknowledgment?

medium

A. The message is requeued and delivered to another worker

B. The queue deletes all messages

C. The message is acknowledged automatically

D. The message is lost and never processed again

Solution

1. Step 1: Understand auto_ack=False behavior

   With auto_ack set to False, the worker must explicitly acknowledge messages after processing.

2. Step 2: Effect of worker crash before ack

   If the worker crashes before ack, RabbitMQ requeues the message to deliver it to another worker, ensuring no task is lost.

3. Final Answer:

   The message is requeued and delivered to another worker -> Option A

4. Quick Check:

   auto_ack=False + crash = requeue message [OK]

Hint: auto_ack=False means unacked messages get requeued on crash [OK]

Common Mistakes:

• Assuming messages are lost without ack
• Thinking messages auto-acknowledge on delivery
• Believing queue deletes messages on worker failure

4. You wrote this code to declare a durable queue:

channel.queue_declare(queue='task_queue', durable=False)

Why might this cause task loss after RabbitMQ restarts?

medium

A. Because exclusive=True is missing

B. Because the queue name is invalid

C. Because durable=True deletes messages on restart

D. Because durable=False means the queue is deleted on restart

Solution

1. Step 1: Analyze durable flag effect

   Setting durable=False means the queue is temporary and will be deleted when RabbitMQ restarts.

2. Step 2: Consequence on task persistence

   Since the queue is deleted, any unprocessed tasks in it are lost after restart.

3. Final Answer:

   Because durable=False means the queue is deleted on restart -> Option D

4. Quick Check:

   durable=False = queue lost on restart [OK]

Hint: durable=False queues vanish on restart, losing tasks [OK]

Common Mistakes:

• Confusing durable with exclusive
• Thinking queue name causes loss
• Believing durable=True deletes messages

5. You want to ensure tasks are not lost even if RabbitMQ crashes and workers fail. Which combination of settings should you use for the queue and messages?

hard

A. Declare queue with autoDelete=true and publish messages with delivery_mode=1

B. Declare queue with exclusive=true and publish messages with delivery_mode=1

C. Declare queue with durable=true and publish messages with delivery_mode=2

D. Declare queue with durable=false and publish messages with delivery_mode=2

Solution

1. Step 1: Ensure queue durability

   Setting durable=true makes the queue survive RabbitMQ restarts, preventing loss of the queue itself.

2. Step 2: Make messages persistent

   Publishing messages with delivery_mode=2 marks them as persistent, so they are saved to disk and not lost on server crash.

3. Step 3: Understand why other options fail

   autoDelete=true deletes the queue when no consumers remain, exclusive=true restricts queue to one connection, and durable=false means queue is temporary. delivery_mode=1 means messages are transient and can be lost.

4. Final Answer:

   Declare queue with durable=true and publish messages with delivery_mode=2 -> Option C

5. Quick Check:

   durable queue + persistent messages = no loss [OK]

Hint: Durable queue + delivery_mode=2 messages prevent loss [OK]

Common Mistakes:

• Using autoDelete instead of durable for persistence
• Publishing messages without delivery_mode=2
• Confusing exclusive with durability