- A
The message is moved to the dead-letter sub-queue of the original queue
Dead-lettering on MaxDeliveryCount is automatic. The message's DeliveryCount property increments on each delivery attempt. When DeliveryCount exceeds MaxDeliveryCount, Service Bus moves the message to the /<queue>/$deadletterqueue path with a DeadLetterReason of 'MaxDeliveryCountExceeded'.
- B
The message is permanently deleted from the queue
Why wrong: Service Bus does not delete messages silently on delivery failure. Automatic deletion would cause undetectable data loss. Dead-lettering preserves the message for inspection and manual intervention.
- C
The message is returned to the front of the queue with its DeliveryCount reset to zero
Why wrong: Resetting the count would create an infinite retry loop for poison messages, blocking queue consumers indefinitely. The dead-letter mechanism prevents this by removing the message from the main queue after the configured threshold.
- D
The message expires and is discarded according to the Time-to-Live setting
Why wrong: Time-to-Live is an independent expiration mechanism. A message can be moved to the dead-letter queue before its TTL expires if MaxDeliveryCount is exceeded. TTL expiry and delivery count are separate conditions, either of which can trigger dead-lettering if the respective setting is enabled.
Quick Answer
The answer is that the message is moved to the dead-letter sub-queue of the original queue. This occurs because Azure Service Bus tracks each delivery attempt via the DeliveryCount property, and once that count exceeds the MaxDeliveryCount threshold (default 10), the broker automatically transfers the message to the dead-letter sub-queue to prevent infinite redelivery loops. On the AZ-204 exam, this concept tests your understanding of poison message handling and the dead-letter queue’s role in decoupling failed messages from the main processing flow. A common trap is assuming the message is simply deleted or returned to the main queue, but Service Bus preserves it in the dead-letter sub-queue for manual inspection and remediation. Remember the memory tip: “Max deliveries met? Dead-letter it.”
AZ-204 Practice Question: Service Bus dead-letter queue behavior after…
This AZ-204 practice question tests your understanding of connect to and consume azure services and third-party services. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: service Bus dead-letter queue. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Messages failing to process are redelivered by Azure Service Bus. After a message has been delivered and abandoned the maximum number of times (MaxDeliveryCount), where does Service Bus move the message?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The message is moved to the dead-letter sub-queue of the original queue
When a message in Azure Service Bus is delivered and abandoned the maximum number of times (as defined by the MaxDeliveryCount property, default 10), the message is automatically moved to the dead-letter sub-queue of the original queue. This dead-letter sub-queue stores messages that cannot be processed successfully, allowing you to inspect and handle them separately without losing the message entirely.
Key principle: Service Bus dead-letter queue
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The message is moved to the dead-letter sub-queue of the original queue
Why this is correct
Dead-lettering on MaxDeliveryCount is automatic. The message's DeliveryCount property increments on each delivery attempt. When DeliveryCount exceeds MaxDeliveryCount, Service Bus moves the message to the /<queue>/$deadletterqueue path with a DeadLetterReason of 'MaxDeliveryCountExceeded'.
Related concept
Service Bus dead-letter queue
- ✗
The message is permanently deleted from the queue
Why it's wrong here
Service Bus does not delete messages silently on delivery failure. Automatic deletion would cause undetectable data loss. Dead-lettering preserves the message for inspection and manual intervention.
- ✗
The message is returned to the front of the queue with its DeliveryCount reset to zero
Why it's wrong here
Resetting the count would create an infinite retry loop for poison messages, blocking queue consumers indefinitely. The dead-letter mechanism prevents this by removing the message from the main queue after the configured threshold.
- ✗
The message expires and is discarded according to the Time-to-Live setting
Why it's wrong here
Time-to-Live is an independent expiration mechanism. A message can be moved to the dead-letter queue before its TTL expires if MaxDeliveryCount is exceeded. TTL expiry and delivery count are separate conditions, either of which can trigger dead-lettering if the respective setting is enabled.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume messages are simply deleted or returned to the queue when the delivery count is exceeded, but Azure Service Bus explicitly moves them to a dead-letter sub-queue to ensure no data loss and to provide a mechanism for manual handling.
Detailed technical explanation
How to think about this question
Under the hood, Service Bus tracks the DeliveryCount property on each message, incrementing it each time the message is delivered and then abandoned (via AbandonAsync) or the lock expires. When DeliveryCount reaches MaxDeliveryCount, the broker atomically moves the message to the dead-letter sub-queue (accessible via the path `{queue}/$DeadLetterQueue`). This sub-queue supports all standard operations (Peek, Receive, Complete) and can be used to implement retry logic or manual intervention. A real-world scenario is a poison message that causes a deserialization error; moving it to the dead-letter sub-queue prevents it from blocking the main queue while preserving it for debugging.
KKey Concepts to Remember
- Service Bus dead-letter queue
- MaxDeliveryCount
- poison message handling
- dead-lettering
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Service Bus dead-letter queue
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Service Bus dead-letter queue Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Review service Bus dead-letter queue, then practise related AZ-204 questions on the same topic to reinforce the concept.
- →
Connect to and consume Azure services and third-party services — study guide chapter
Learn the concepts, then practise the questions
- →
Connect to and consume Azure services and third-party services practice questions
Targeted practice on this topic area only
- →
All AZ-204 questions
997 questions across all exam domains
- →
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
- →
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-204 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Develop Azure compute solutions practice questions
Practise AZ-204 questions linked to Develop Azure compute solutions.
Develop for Azure storage practice questions
Practise AZ-204 questions linked to Develop for Azure storage.
Implement Azure security practice questions
Practise AZ-204 questions linked to Implement Azure security.
Connect to and consume Azure services and third-party services practice questions
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Monitor, troubleshoot, and optimize Azure solutions practice questions
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
AZ-204 fundamentals practice questions
Practise AZ-204 questions linked to AZ-204 fundamentals.
AZ-204 scenario practice questions
Practise AZ-204 questions linked to AZ-204 scenario.
AZ-204 troubleshooting practice questions
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Start a free AZ-204 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-204 question test?
Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — Service Bus dead-letter queue.
What is the correct answer to this question?
The correct answer is: The message is moved to the dead-letter sub-queue of the original queue — When a message in Azure Service Bus is delivered and abandoned the maximum number of times (as defined by the MaxDeliveryCount property, default 10), the message is automatically moved to the dead-letter sub-queue of the original queue. This dead-letter sub-queue stores messages that cannot be processed successfully, allowing you to inspect and handle them separately without losing the message entirely.
What should I do if I get this AZ-204 question wrong?
Review service Bus dead-letter queue, then practise related AZ-204 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Service Bus dead-letter queue
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More AZ-204 practice questions
- An app must store relational state and perform transactions across multiple tables with T-SQL support. Which Azure data…
- You are monitoring an Azure App Service using Application Insights. You notice that the server response time is high for…
- Which TWO services can be used to implement a publish-subscribe messaging pattern in Azure?
- You need to monitor the CPU utilization of an Azure VM in real-time and set up an alert when it exceeds 90%. Which Azure…
- You are monitoring an Azure web application with Application Insights. You notice a sudden increase in the number of fai…
- You are monitoring an Azure web app using Application Insights. You need to create a query that returns the average dura…
Last reviewed: Jun 11, 2026
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.