A knotweed-dike message fails repeatedly and keeps looping through workers. Where should Service Bus place it after max delivery attempts?
Select an answer to reveal the explanation.
Short Explanation
Infinite worker retries are a hamster wheel. After max delivery (or an explicit DeadLetter), Service Bus parks the message on the dead-letter subqueue for inspection.
Full Explanation
Service Bus moves messages that exceed max delivery count — or that the app dead-letters explicitly — to the dead-letter subqueue for later inspection. That is distinct from Event Grid's blob dead-letter destination and from Azure Functions/Storage poison-queue conventions on Storage queues.