Correct Answer: Enable the Dead-Letter Queue (DLQ) and set MaxDeliveryCount to 3
Every Service Bus queue and topic subscription has a built-in Dead-Letter Queue. When a message exceeds MaxDeliveryCount (set to 3), it is automatically moved to the DLQ with the f...
Correct Answer
Enable the Dead-Letter Queue (DLQ) and set MaxDeliveryCount to 3
Why This Answer Is Correct
Every Service Bus queue and topic subscription has a built-in Dead-Letter Queue. When a message exceeds MaxDeliveryCount (set to 3), it is automatically moved to the DLQ with the failure reason. You can then inspect, repair, and resubmit messages from the DLQ without losing them.
This question evaluates your knowledge of Azure Service Bus — a core concept tested in Microsoft Certified: Azure Developer Associate (AZ-204). Understanding Azure Service Bus is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are implementing a publish-subscribe pattern where multiple services (email, SMS, audit) need to receive every order event independently. Each subscriber must process all messages at its own pace without affecting other subscribers. Which Azure Service Bus feature should you use?
A payment processing microservice sends order events to an Azure Service Bus queue. Downstream consumers occasionally crash mid-processing, and in that case the message must be retried. However, if the same message fails more than 5 times, it must be moved to a separate queue for manual review without blocking healthy messages. Which Service Bus feature handles this automatically?