Bird
Raised Fist0
RabbitMQdevops~10 mins

Lazy queues for memory management in RabbitMQ - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to declare a lazy queue in RabbitMQ using the command line.

RabbitMQ
rabbitmqadmin declare queue name=my_lazy_queue durable=true arguments={'x-queue-mode': '[1]'}
Drag options to blanks, or click blank then click option'
Alazy
Beager
Cdefault
Dtransient
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'eager' instead of 'lazy' causes messages to stay in memory.
2fill in blank
medium

Complete the JSON configuration snippet to declare a lazy queue in RabbitMQ.

RabbitMQ
{
  "queue": "my_queue",
  "durable": true,
  "arguments": {"x-queue-mode": "[1]"}
}
Drag options to blanks, or click blank then click option'
Alazy
Btransient
Ceager
Ddefault
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'eager' will keep messages in RAM, increasing memory usage.
3fill in blank
hard

Fix the error in the queue declaration command to make the queue lazy.

RabbitMQ
rabbitmqadmin declare queue name=task_queue durable=true arguments={'x-queue-mode': '[1]'}
Drag options to blanks, or click blank then click option'
Aeager
Bdefault
Clazy
Dtransient
Attempts:
3 left
💡 Hint
Common Mistakes
Leaving the mode as 'eager' causes high memory usage.
4fill in blank
hard

Fill both blanks to declare a durable lazy queue with the correct argument key and value.

RabbitMQ
rabbitmqadmin declare queue name=lazy_queue durable=true arguments={{'[1]': '[2]'}}
Drag options to blanks, or click blank then click option'
Ax-queue-mode
Bdurable
Clazy
Dtransient
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'durable' as argument key or 'transient' as value.
5fill in blank
hard

Fill all three blanks to create a Python dictionary for a lazy queue declaration with the correct key, value, and durability flag.

RabbitMQ
{'[1]': '[2]', 'durable': [3]
Drag options to blanks, or click blank then click option'
Ax-queue-mode
Blazy
Ctrue
Dfalse
Attempts:
3 left
💡 Hint
Common Mistakes
Setting durable to false or using wrong keys or values.

Practice

(1/5)
1. What is the main benefit of using lazy queues in RabbitMQ?
easy
A. They automatically delete messages after consumption
B. They increase message processing speed
C. They replicate messages across multiple nodes
D. They store messages on disk to reduce memory usage

Solution

  1. Step 1: Understand lazy queue behavior

    Lazy queues keep messages on disk instead of memory to save RAM.
  2. Step 2: Compare benefits

    This reduces memory usage but may slow down processing speed.
  3. Final Answer:

    They store messages on disk to reduce memory usage -> Option D
  4. Quick Check:

    Lazy queues = disk storage for memory saving [OK]
Hint: Lazy queues save RAM by storing messages on disk [OK]
Common Mistakes:
  • Confusing lazy queues with faster queues
  • Thinking lazy queues delete messages automatically
  • Assuming lazy queues replicate messages
2. Which is the correct way to declare a lazy queue using RabbitMQ's policy with rabbitmqctl?
easy
A. rabbitmqctl set_policy lazy-queue ".*" '{"mode":"lazy"}'
B. rabbitmqctl set_policy lazy-queue ".*" '{"lazy-queue":"true"}'
C. rabbitmqctl set_policy lazy-queue ".*" '{"queue-type":"lazy"}'
D. rabbitmqctl set_policy lazy-queue ".*" '{"queue-mode":"lazy"}'

Solution

  1. Step 1: Recall RabbitMQ policy syntax for lazy queues

    The correct key to set lazy mode is "mode" with value "lazy".
  2. Step 2: Match the correct JSON format

    rabbitmqctl set_policy lazy-queue ".*" '{"mode":"lazy"}' uses '{"mode":"lazy"}', which is the correct syntax.
  3. Final Answer:

    rabbitmqctl set_policy lazy-queue ".*" '{"mode":"lazy"}' -> Option A
  4. Quick Check:

    mode = lazy for lazy queues [OK]
Hint: Use 'mode' key with value 'lazy' in policy JSON [OK]
Common Mistakes:
  • Using incorrect JSON keys like 'queue-mode' or 'queue-type'
  • Missing quotes around JSON keys or values
  • Incorrect policy name or regex pattern
3. Given a queue declared as lazy, what will be the expected behavior when publishing 1000 messages rapidly?
medium
A. Messages will be stored on disk to reduce memory usage
B. Messages will be stored mostly in memory for fast access
C. Messages will be dropped if memory is full
D. Messages will be replicated to all consumers immediately

Solution

  1. Step 1: Understand lazy queue message storage

    Lazy queues store messages on disk to save memory, especially under load.
  2. Step 2: Analyze behavior on rapid publishing

    When many messages arrive quickly, lazy queues keep them on disk rather than memory.
  3. Final Answer:

    Messages will be stored on disk to reduce memory usage -> Option A
  4. Quick Check:

    Lazy queue + rapid publish = disk storage [OK]
Hint: Lazy queues store messages on disk, not memory, under load [OK]
Common Mistakes:
  • Assuming messages stay in memory for speed
  • Thinking messages get dropped automatically
  • Confusing replication with storage
4. You set a policy to make queues lazy but notice memory usage is still high. What is a likely cause?
medium
A. The queue-mode is set to 'default' instead of 'lazy'
B. The policy regex does not match the queue names
C. Messages are too small to affect memory
D. Consumers are not connected

Solution

  1. Step 1: Check policy application

    If the regex pattern does not match queue names, the policy won't apply.
  2. Step 2: Understand effect on memory

    Without the policy applied, queues remain normal and use more memory.
  3. Final Answer:

    The policy regex does not match the queue names -> Option B
  4. Quick Check:

    Policy regex mismatch = no lazy effect [OK]
Hint: Ensure policy regex matches queue names exactly [OK]
Common Mistakes:
  • Assuming policy applies without matching regex
  • Ignoring queue-mode value correctness
  • Blaming consumers for memory usage
5. You want to optimize a RabbitMQ cluster with many large queues and limited RAM. Which approach best uses lazy queues effectively?
hard
A. Disable lazy mode and increase RAM instead
B. Set all queues to lazy mode regardless of size
C. Apply a policy with {"queue-mode":"lazy"} to all large queues only
D. Use lazy mode only on queues with few messages

Solution

  1. Step 1: Identify queues needing lazy mode

    Large queues benefit most from lazy mode to save memory.
  2. Step 2: Apply policy selectively

    Applying lazy mode only to large queues balances memory saving and performance.
  3. Step 3: Avoid unnecessary lazy mode

    Setting all queues lazy may slow down small queues unnecessarily.
  4. Final Answer:

    Apply a policy with {"queue-mode":"lazy"} to all large queues only -> Option C
  5. Quick Check:

    Lazy mode for large queues = best memory use [OK]
Hint: Use lazy mode selectively on large queues for best results [OK]
Common Mistakes:
  • Applying lazy mode to all queues blindly
  • Ignoring queue size when applying policies
  • Relying only on hardware upgrades
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard