Message TTL (Time To Live) in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this RabbitMQ queue declaration with TTL?

You declare a queue with the following command. What will be the TTL (in milliseconds) for messages in this queue?

RabbitMQ

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

A 60000

B 6000

C 0

D 3600000

💡 Hint

TTL is set in milliseconds in the x-message-ttl argument.

The x-message-ttl argument sets the message time to live in milliseconds. Here, 60000 means 60 seconds.

🧠 Conceptual

intermediate

What happens to a message when its TTL expires in RabbitMQ?

In RabbitMQ, if a message's TTL expires while it is still in the queue, what is the expected behavior?

A The message is delivered immediately regardless of TTL.

B The message is discarded or dead-lettered if configured.

C The message TTL resets and the message stays in the queue indefinitely.

D The queue deletes itself automatically.

💡 Hint

TTL means the message should not live beyond a certain time in the queue.

When a message's TTL expires, RabbitMQ removes it from the queue. If a dead-letter exchange is configured, the message is sent there; otherwise, it is discarded.

❓ Configuration

advanced

Which queue declaration sets a message TTL of 30 seconds and dead-letters expired messages to 'dlx' exchange?

Choose the correct RabbitMQ queue declaration command that sets a 30-second message TTL and routes expired messages to a dead-letter exchange named 'dlx'.

A rabbitmqadmin declare queue name=task_queue arguments={"x-message-ttl":30000,"x-dead-letter-exchange":"dlx"}

B rabbitmqadmin declare queue name=task_queue arguments={"x-message-ttl":30000,"x-dead-letter-exchange":""}

C rabbitmqadmin declare queue name=task_queue arguments={"x-message-ttl":3000,"x-dead-letter-exchange":"dlx"}

D }"xld":"egnahcxe-rettel-daed-x",00003:"ltt-egassem-x"{=stnemugra eueuq_ksat=eman eueuq eralced nimdaqmtibbar

💡 Hint

TTL is in milliseconds and dead-letter exchange name must be a string.

Option A correctly sets TTL to 30000 ms (30 seconds) and dead-letters expired messages to 'dlx'. Option A disables dead-lettering. Option A sets TTL to 3000 ms (3 seconds). Option A is identical to B and also valid.

❓ Troubleshoot

advanced

Why are expired messages not removed from a RabbitMQ queue with TTL set?

You set a message TTL on a queue, but expired messages remain in the queue indefinitely. What is the most likely cause?

A RabbitMQ does not support message TTL on queues.

B The TTL value was set too high, so messages have not expired yet.

C The queue has no consumers, so expired messages are not removed automatically.

D The messages were published with a per-message TTL overriding the queue TTL.

💡 Hint

Expired messages are removed during queue operations like delivery or purge.

RabbitMQ removes expired messages lazily during queue operations. If no consumers are connected, expired messages may remain until the queue is accessed.

🔀 Workflow

expert

Order the steps to configure and verify message TTL with dead-lettering in RabbitMQ.

Put these steps in the correct order to set up a queue with message TTL and dead-letter exchange, then verify expired messages are dead-lettered.

A 3,1,2,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

You must create the dead-letter exchange before referencing it in the queue.

First create the dead-letter exchange, then declare the queue with TTL and dead-letter settings, publish messages, and finally consume from the dead-letter queue to verify.

Practice

1. What does setting a Message TTL (Time To Live) in RabbitMQ do?

easy

A. It sets the maximum size of a message in bytes.

B. It specifies the priority level of messages in the queue.

C. It controls the number of consumers allowed to read from a queue.

D. It defines how long a message stays in a queue before it is removed.

Solution

1. Step 1: Understand the purpose of Message TTL

   Message TTL controls the lifetime of messages in a queue before they expire and get removed.

2. Step 2: Compare options with TTL definition

   Only It defines how long a message stays in a queue before it is removed. correctly describes TTL as the time a message stays before removal.

3. Final Answer:

   It defines how long a message stays in a queue before it is removed. -> Option D

4. Quick Check:

   Message TTL = message lifetime in queue [OK]

Hint: TTL means message lifetime before removal [OK]

Common Mistakes:

• Confusing TTL with message size limit
• Thinking TTL controls consumer count
• Mixing TTL with message priority

2. Which of the following is the correct way to set a queue-level message TTL of 60000 milliseconds in RabbitMQ using the policy command?

easy

A. rabbitmqctl set_policy TTL "^myqueue$" '{"message-ttl":60000}' --apply-to queues

B. rabbitmqctl set_policy TTL "myqueue" '{"message-ttl":60000}' --apply-to exchanges

C. rabbitmqctl set_policy TTL "^myqueue$" '{"queue-ttl":60000}' --apply-to queues

D. rabbitmqctl set_policy TTL "myqueue" '{"message-ttl":60}' --apply-to queues

Solution

1. Step 1: Identify correct policy syntax for message TTL

   The policy command uses regex for queue names, JSON for arguments, and --apply-to queues for queue policies.

2. Step 2: Check each option's correctness

   rabbitmqctl set_policy TTL "^myqueue$" '{"message-ttl":60000}' --apply-to queues uses regex ^myqueue$, correct key "message-ttl" with 60000 ms, and applies to queues. Others have wrong keys, apply-to exchanges, or wrong TTL units.

3. Final Answer:

   rabbitmqctl set_policy TTL "^myqueue$" '{"message-ttl":60000}' --apply-to queues -> Option A

4. Quick Check:

   Policy syntax with regex and message-ttl key [OK]

Hint: Use regex and 'message-ttl' key with --apply-to queues [OK]

Common Mistakes:

• Using 'queue-ttl' instead of 'message-ttl'
• Applying policy to exchanges instead of queues
• Not using regex for queue name

3. Given the following queue declaration in RabbitMQ with a message TTL of 5000 ms:

channel.queue_declare(queue='task_queue', arguments={'x-message-ttl': 5000})

What happens to a message published to this queue if it is not consumed within 6 seconds?

medium

A. The message remains in the queue indefinitely until consumed.

B. The message is removed from the queue after 5 seconds and will not be delivered.

C. The message is moved to a dead-letter queue immediately.

D. The message TTL resets every time a consumer connects.

Solution

1. Step 1: Understand x-message-ttl effect on messages

   The 'x-message-ttl' argument sets how long messages live in the queue before expiring if not consumed.

2. Step 2: Analyze the timing and behavior

   Since TTL is 5000 ms (5 seconds), a message not consumed within 6 seconds expires and is removed from the queue.

3. Final Answer:

   The message is removed from the queue after 5 seconds and will not be delivered. -> Option B

4. Quick Check:

   Message TTL 5000 ms means removal after 5 seconds [OK]

Hint: Message expires after TTL if not consumed [OK]

Common Mistakes:

• Assuming message stays forever without consumer
• Thinking TTL resets on consumer connection
• Confusing dead-letter queue behavior

4. You set a message TTL of 10000 ms on a queue, but messages are not expiring as expected. Which of the following is the most likely cause?

medium

A. The queue was declared without the 'x-message-ttl' argument, so TTL is not applied.

B. The messages have individual TTLs that override the queue TTL with longer values.

C. The RabbitMQ server does not support message TTL feature.

D. The consumer is acknowledging messages too quickly.

Solution

1. Step 1: Understand common causes for TTL not applying

   The most frequent issue is omitting the 'x-message-ttl' argument during queue declaration, despite intending to set it.

2. Step 2: Evaluate each option's likelihood

   The queue was declared without the 'x-message-ttl' argument, so TTL is not applied. is most likely, as missing the argument prevents TTL enforcement. The messages have individual TTLs that override the queue TTL with longer values. is incorrect, as RabbitMQ uses the minimum TTL (queue wins if shorter). The RabbitMQ server does not support message TTL feature. is false. The consumer is acknowledging messages too quickly. causes consumption before expiration, not TTL failure.

3. Final Answer:

   The queue was declared without the 'x-message-ttl' argument, so TTL is not applied. -> Option A

4. Quick Check:

   Missing x-message-ttl arg prevents expiration [OK]

Hint: Verify x-message-ttl in queue declaration arguments [OK]

Common Mistakes:

• Omitting 'x-message-ttl' argument in queue_declare
• Believing longer per-message TTL prevents queue TTL expiration
• Assuming RabbitMQ lacks TTL support
• Confusing fast consumption with TTL malfunction

5. You want to configure a RabbitMQ queue so that messages expire after 10 seconds if not consumed, and expired messages are sent to a dead-letter exchange named dlx_exchange. Which queue arguments should you set?

hard

A. {"x-message-ttl": 10000, "x-dead-letter-exchange": ""}

B. {"x-queue-ttl": 10000, "x-dead-letter-exchange": "dlx_exchange"}

C. {"x-message-ttl": 10000, "x-dead-letter-exchange": "dlx_exchange"}

D. {"x-message-ttl": 10000, "x-dead-letter-routing-key": "dlx_exchange"}

Solution

1. Step 1: Identify correct TTL and dead-letter arguments

   To expire messages after 10 seconds, use "x-message-ttl": 10000. To send expired messages to a dead-letter exchange, use "x-dead-letter-exchange" with the exchange name.

2. Step 2: Evaluate options for correctness

   {"x-message-ttl": 10000, "x-dead-letter-exchange": "dlx_exchange"} correctly sets both "x-message-ttl" and "x-dead-letter-exchange". {"x-queue-ttl": 10000, "x-dead-letter-exchange": "dlx_exchange"} uses "x-queue-ttl" which expires the whole queue, not messages. {"x-message-ttl": 10000, "x-dead-letter-routing-key": "dlx_exchange"} misuses "x-dead-letter-routing-key" for exchange name. {"x-message-ttl": 10000, "x-dead-letter-exchange": ""} sets dead-letter exchange to empty string, disabling dead-lettering.

3. Final Answer:

   {"x-message-ttl": 10000, "x-dead-letter-exchange": "dlx_exchange"} -> Option C

4. Quick Check:

   Use x-message-ttl and x-dead-letter-exchange keys [OK]

Hint: Use x-message-ttl and x-dead-letter-exchange keys [OK]

Common Mistakes:

• Using x-queue-ttl instead of x-message-ttl
• Confusing dead-letter exchange with routing key
• Leaving dead-letter exchange empty disables dead-lettering