Dead letter queues in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a dead letter queue for an Azure Service Bus queue.

Azure

deadLetterQueuePath = queueName + '/[1]'

Drag options to blanks, or click blank then click option'

Adeadletter

Bdeadletterqueue

Cdeadletters

Ddeadletter-queue

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect suffix like '/deadletterqueue' or '/deadletters'.

Forgetting to add the slash '/' before the suffix.

The dead letter queue path is formed by appending '/deadletter' to the main queue name.

2fill in blank

medium

Complete the code to receive messages from the dead letter queue in Azure Service Bus.

Azure

receiver = client.get_queue_receiver(queue_name=queueName + '/[1]')

Drag options to blanks, or click blank then click option'

Adeadletter

Bdeadletters

Cdeadletterqueue

Ddeadletter-queue

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong suffix like '/deadletterqueue'.

Omitting the slash '/' before the suffix.

To receive messages from the dead letter queue, append '/deadletter' to the queue name.

3fill in blank

hard

Fix the error in the code to forward dead letter messages to another queue.

Azure

forwardDeadLetteredMessagesTo = '[1]'

Drag options to blanks, or click blank then click option'

AmainQueue

BforwardToQueue

CdeadLetterQueue

DforwardDeadLetteredMessagesTo

Attempts:

3 left

💡 Hint

Common Mistakes

Setting the property to itself as a string.

Using the dead letter queue name instead of the target queue.

The property to forward dead letter messages must be set to the target queue name, e.g., 'forwardToQueue'.

4fill in blank

hard

Fill both blanks to configure a Service Bus queue with dead letter forwarding enabled.

Azure

queueDescription = ServiceBusQueueDescription(name='[1]', forwardDeadLetteredMessagesTo='[2]')

Drag options to blanks, or click blank then click option'

Aorders

Borders-dlq

Corders-forward

Ddeadletter

Attempts:

3 left

💡 Hint

Common Mistakes

Using the dead letter suffix as the main queue name.

Forwarding dead letter messages back to the same queue.

The main queue is named 'orders', and dead letter messages are forwarded to 'orders-forward'.

5fill in blank

hard

Fill all three blanks to create a dead letter queue client and receive messages.

Azure

dlq_path = '[1]' + '/[2]'
receiver = client.get_queue_receiver(queue_name=dlq_path, max_wait_time=[3])

Drag options to blanks, or click blank then click option'

Ainvoices

Bdeadletter

C30

Ddeadletters

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect dead letter suffix.

Setting max_wait_time to a string instead of a number.

The dead letter queue path is 'invoices/deadletter', and the receiver waits up to 30 seconds for messages.

Practice

1. What is the main purpose of a dead letter queue in Azure Service Bus?

easy

A. To store messages that cannot be processed after multiple retries

B. To speed up message delivery to consumers

C. To permanently delete messages after processing

D. To encrypt messages for security

Solution

1. Step 1: Understand message processing failures

   When a message cannot be processed successfully after several attempts, it needs a place to be stored for later inspection.

2. Step 2: Identify the role of dead letter queue

   The dead letter queue holds these failed messages separately to keep the main queue clean and allow troubleshooting.

3. Final Answer:

   To store messages that cannot be processed after multiple retries -> Option A

4. Quick Check:

   Dead letter queue = stores failed messages [OK]

Hint: Dead letter queue holds failed messages after retries [OK]

Common Mistakes:

• Thinking it speeds up delivery
• Confusing with message deletion
• Assuming it encrypts messages

2. Which property must be set to enable dead lettering on message expiration in Azure Service Bus?

easy

A. autoDeleteOnIdle

B. maxDeliveryCount

C. enableDeadLetteringOnMessageExpiration

D. lockDuration

Solution

1. Step 1: Identify dead lettering on expiration setting

   Azure Service Bus has a specific property to enable dead lettering when messages expire.

2. Step 2: Match property name

   The property enableDeadLetteringOnMessageExpiration controls this behavior.

3. Final Answer:

   enableDeadLetteringOnMessageExpiration -> Option C

4. Quick Check:

   Dead letter on expiration = enableDeadLetteringOnMessageExpiration [OK]

Hint: Look for 'enableDeadLettering' in property names [OK]

Common Mistakes:

• Confusing with maxDeliveryCount which controls retries
• Using autoDeleteOnIdle which deletes queues
• Using lockDuration which controls message lock time

3. Given the following Azure Service Bus queue settings:
maxDeliveryCount = 5
If a message fails processing 6 times, where will it be moved?

medium

A. It stays in the main queue for retry

B. It is deleted permanently

C. It is sent back to the sender

D. It is moved to the dead letter queue

Solution

1. Step 1: Understand maxDeliveryCount meaning

   This setting defines how many times a message can be delivered for processing before it is considered poison.

2. Step 2: Apply the retry logic

   After 5 failed attempts, the 6th failure triggers moving the message to the dead letter queue.

3. Final Answer:

   It is moved to the dead letter queue -> Option D

4. Quick Check:

   Retries exceeded = move to dead letter queue [OK]

Hint: More failures than maxDeliveryCount sends to dead letter queue [OK]

Common Mistakes:

• Assuming message stays in main queue indefinitely
• Thinking message is deleted immediately
• Believing message returns to sender automatically

4. You configured a queue with maxDeliveryCount = 3 but messages are not moving to the dead letter queue after 3 failures. What is the most likely cause?

medium

A. Dead lettering on message expiration is not enabled

B. The queue does not have dead letter queue enabled

C. The message lock duration is too short

D. The maxDeliveryCount value is ignored by Azure

Solution

1. Step 1: Check dead letter queue enablement

   For messages to move to dead letter queue after maxDeliveryCount, the queue must have dead lettering enabled.

2. Step 2: Identify missing configuration

   If dead lettering is not enabled, messages will not move even if maxDeliveryCount is reached.

3. Final Answer:

   The queue does not have dead letter queue enabled -> Option B

4. Quick Check:

   Dead letter queue must be enabled for message move [OK]

Hint: Dead letter queue must be enabled to move messages [OK]

Common Mistakes:

• Confusing message expiration with delivery count
• Blaming lock duration for dead lettering
• Thinking Azure ignores maxDeliveryCount

5. You want to design a system where messages that fail processing due to validation errors are sent to a dead letter queue, but messages that fail due to temporary system errors are retried multiple times. Which Azure Service Bus configuration best supports this?

hard

A. Use message properties to detect validation errors and explicitly dead letter those messages in code

B. Set maxDeliveryCount high and enable dead lettering on message expiration only

C. Disable dead letter queue and rely on manual message deletion

D. Set maxDeliveryCount to 1 and disable retries

Solution

1. Step 1: Understand different failure types

   Validation errors are permanent and should be dead lettered immediately; system errors are temporary and should be retried.

2. Step 2: Use message properties and code logic

   By inspecting message properties in processing code, you can dead letter validation errors explicitly, while letting other messages retry.

3. Step 3: Evaluate other options

   Setting maxDeliveryCount high or only dead lettering on expiration won't separate error types; disabling dead letter queue or retries is not practical.

4. Final Answer:

   Use message properties to detect validation errors and explicitly dead letter those messages in code -> Option A

5. Quick Check:

   Explicit dead lettering by code for validation errors [OK]

Hint: Use code to dead letter specific error types [OK]

Common Mistakes:

• Relying only on maxDeliveryCount for all errors
• Disabling dead letter queue entirely
• Setting maxDeliveryCount too low causing premature dead lettering