Queue TTL and auto-expiry in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Queue TTL behavior in RabbitMQ

What happens to messages in a RabbitMQ queue when the queue has a TTL (time-to-live) set on messages?

A Messages are moved to a dead-letter queue only if the TTL is set on the queue, not on messages.

B Messages expire and are removed from the queue after the TTL duration, even if they are not consumed.

C Messages are deleted immediately when the queue is declared with TTL, regardless of message age.

D Messages remain in the queue indefinitely until consumed, TTL only applies to the queue itself.

💡 Hint

Think about what TTL means for individual messages in a queue.

Message TTL means each message has a lifespan. If it is not consumed before the TTL expires, RabbitMQ removes it automatically.

💻 Command Output

intermediate

Queue auto-expiry effect on queue existence

Given a queue declared with x-expires set to 60000 (60 seconds), what happens if the queue is unused for 70 seconds?

RabbitMQ

rabbitmqctl list_queues name messages
# After 70 seconds of no consumers or messages

A The queue is automatically deleted and will not appear in the list.

B The queue remains but all messages inside expire.

C The queue remains with zero messages but is not deleted.

D The queue is paused and will not accept new messages.

💡 Hint

Consider what x-expires controls in RabbitMQ.

The x-expires argument sets the queue auto-expiry time. If the queue is unused (no consumers, no messages) for that time, RabbitMQ deletes it automatically.

❓ Configuration

advanced

Correct queue declaration with message TTL and auto-expiry

Which of the following queue declarations correctly sets a message TTL of 30 seconds and auto-expiry of 2 minutes?

A rabbitmqadmin declare queue name=myqueue arguments={"x-message-ttl":120000,"x-expires":30000}

B rabbitmqadmin declare queue name=myqueue arguments={"x-expires":30000,"x-message-ttl":120000}

C rabbitmqadmin declare queue name=myqueue arguments={"x-message-ttl":30000,"x-expires":120000}

D rabbitmqadmin declare queue name=myqueue arguments={"x-expires":60000,"x-message-ttl":60000}

💡 Hint

Remember TTL values are in milliseconds and x-message-ttl is for messages, x-expires is for queue expiry.

Option C correctly sets x-message-ttl to 30000 ms (30 seconds) and x-expires to 120000 ms (2 minutes). Other options swap or use wrong values.

❓ Troubleshoot

advanced

Diagnosing why messages are not expiring as expected

You set x-message-ttl to 10000 (10 seconds) on a queue, but messages remain indefinitely. What is the most likely cause?

A The messages were published with individual TTLs overriding the queue TTL.

B The queue has active consumers that keep messages from expiring.

C The queue is a classic queue and does not support TTL.

D The <code>x-message-ttl</code> argument was set on the queue but not on the messages.

💡 Hint

Consider how message TTLs interact with queue TTL settings.

Individual messages can have TTLs set when published. If these override the queue TTL, messages may live longer than expected.

🔀 Workflow

expert

Sequence to configure and verify queue TTL and auto-expiry

Arrange the steps in the correct order to configure a RabbitMQ queue with message TTL and auto-expiry, then verify the settings.

A 2,1,3,4

B 3,1,2,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about what must happen before publishing messages and verifying settings.

You must first declare the queue with TTL settings, then publish messages, verify the settings, and finally observe expiry behavior.