Queues in message brokers in Data Structures Theory - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the role of queues in message brokers

What is the primary purpose of a queue in a message broker system?

A To store messages temporarily until they are processed by consumers

B To permanently save messages for future reference

C To prioritize messages based on their size

D To encrypt messages before sending them

💡 Hint

Think about how messages are handled between producers and consumers.

Queues in message brokers act as temporary storage holding messages until consumers are ready to process them. This ensures reliable communication between different parts of a system.

📋 Factual

intermediate

Message ordering in queues

Which statement best describes message ordering in a typical queue of a message broker?

A Messages are processed in reverse order of arrival (LIFO)

B Messages are processed randomly without any order

C Messages are processed based on their priority by default

D Messages are always processed in the order they arrive (FIFO)

💡 Hint

Consider the common queue behavior acronym FIFO.

Queues typically follow First-In-First-Out (FIFO) order, meaning messages are processed in the same order they arrive.

🔍 Analysis

advanced

Impact of queue size limits on message brokers

What happens when a message broker's queue reaches its maximum size limit?

A New messages are rejected or blocked until space is available

B Oldest messages are automatically deleted to make space

C Messages are compressed to fit more in the queue

D The queue size automatically increases without limit

💡 Hint

Think about how systems prevent overload and maintain stability.

When a queue is full, the broker typically rejects or blocks new messages to avoid losing data or crashing.

❓ Comparison

advanced

Difference between durable and non-durable queues

Which of the following correctly contrasts durable and non-durable queues in message brokers?

A Non-durable queues save messages permanently; durable queues delete messages after processing

B Durable queues process messages faster than non-durable queues

C Durable queues save messages to disk to survive broker restarts; non-durable queues do not

D Non-durable queues encrypt messages; durable queues do not

💡 Hint

Consider what happens to messages if the broker restarts unexpectedly.

Durable queues store messages on disk so they survive restarts, while non-durable queues keep messages only in memory and lose them if the broker stops.

❓ Reasoning

expert

Effect of multiple consumers on a single queue

In a message broker, what is the typical effect of having multiple consumers reading from the same queue?

A Only the first consumer receives messages; others wait

B Messages are distributed among consumers, allowing parallel processing

C All consumers receive every message, duplicating processing

D Messages are processed in reverse order to balance load

💡 Hint

Think about how queues help scale processing by sharing work.

Multiple consumers on one queue share the messages so each message is processed by only one consumer, enabling parallelism and faster throughput.

Practice

1. What is the primary purpose of a queue in a message broker system?

easy

A. To delete messages immediately after sending

B. To hold messages in order until they are processed

C. To encrypt messages for security

D. To store messages permanently without removal

Solution

1. Step 1: Understand the role of queues

   Queues temporarily hold messages to ensure they are processed in the order they arrive.

2. Step 2: Compare options with queue function

   Only To hold messages in order until they are processed describes holding messages in order until processing, which matches queue behavior.

3. Final Answer:

   To hold messages in order until they are processed -> Option B

4. Quick Check:

   Queue purpose = Hold messages in order [OK]

Hint: Queues store messages temporarily in order [OK]

Common Mistakes:

• Thinking queues delete messages immediately
• Confusing queues with encryption tools
• Assuming queues store messages permanently

2. Which of the following is the correct term for adding a message to a queue?

easy

A. Enqueue

B. Subscribe

C. Publish

D. Dequeue

Solution

1. Step 1: Recall queue operations

   Adding a message to a queue is called enqueueing.

2. Step 2: Match terms to actions

   Dequeue means removing, publish and subscribe relate to messaging but not queue operations.

3. Final Answer:

   Enqueue -> Option A

4. Quick Check:

   Add message = Enqueue [OK]

Hint: Enqueue means add to queue, dequeue means remove [OK]

Common Mistakes:

• Confusing enqueue with dequeue
• Mixing publish/subscribe with queue operations
• Using wrong terms for adding messages

3. Consider a queue that receives messages in this order: M1, M2, M3. If the system processes one message at a time, which message will be processed second?

medium

A. M1

B. M3

C. M2

D. None, all processed simultaneously

Solution

1. Step 1: Understand FIFO behavior of queues

   Queues process messages in the order they arrive: first in, first out.

2. Step 2: Identify the second message processed

   After processing M1 first, the next message processed is M2.

3. Final Answer:

   M2 -> Option C

4. Quick Check:

   Second processed = M2 [OK]

Hint: Queues process messages in arrival order [OK]

Common Mistakes:

• Choosing the first or last message incorrectly
• Assuming parallel processing of all messages
• Ignoring FIFO order

4. A developer wrote this pseudocode for removing a message from a queue:

message = queue.enqueue()

What is the error in this code?

medium

A. No error, code is correct

B. queue should be replaced with stack

C. enqueue() is correct for removing messages

D. enqueue() should be dequeue() to remove a message

Solution

1. Step 1: Identify the operation used

   The code uses enqueue() which adds messages, not removes them.

2. Step 2: Correct the operation for removal

   To remove a message, dequeue() should be used instead of enqueue().

3. Final Answer:

   enqueue() should be dequeue() to remove a message -> Option D

4. Quick Check:

   Remove message = dequeue() [OK]

Hint: Use dequeue() to remove, not enqueue() [OK]

Common Mistakes:

• Using enqueue() to remove messages
• Confusing queue with stack
• Assuming enqueue() removes messages

5. In a message broker, if multiple consumers read from the same queue, what happens to the messages?

hard

A. Messages are distributed so each consumer gets different messages

B. Messages are duplicated for each consumer

C. Each message is delivered to all consumers simultaneously

D. Messages are lost if multiple consumers connect

Solution

1. Step 1: Understand message distribution in queues

   Queues deliver each message to only one consumer to balance load.

2. Step 2: Analyze behavior with multiple consumers

   Messages are distributed among consumers so each gets different messages, not duplicates.

3. Final Answer:

   Messages are distributed so each consumer gets different messages -> Option A

4. Quick Check:

   Multiple consumers share messages, no duplication [OK]

Hint: Queues distribute messages among consumers evenly [OK]

Common Mistakes:

• Thinking all consumers get all messages
• Assuming messages are duplicated
• Believing messages get lost with multiple consumers