Microsoft Azure Developer Associate AZ-204 Practice Question
You have a custom Azure Event Grid topic that currently delivers events to an HTTP endpoint exposed by a microservice named InventoryService. For scheduled maintenance, InventoryService can be offline for several days. You must redesign delivery so that no events are lost and their order is preserved while requiring minimal custom retry logic. What should you configure as the new destination in the event subscription?
An exponential retry policy of 72 hours on the existing HTTP endpoint.
A storage account configured as the dead-letter destination.
An Azure Service Bus queue.
A webhook endpoint that uses manual validation handshake.
Event Grid retries delivery to HTTP endpoints for up to 24 hours only. After that window, events are either dropped or sent to an optional dead-letter location, which still requires additional code to process and does not guarantee ordered delivery. Configuring the event subscription to point at an Azure Service Bus queue provides durable storage well beyond 24 hours and preserves FIFO ordering, allowing InventoryService to pull messages whenever it is available without implementing custom retry logic.
A storage account used solely for dead-lettering would collect undelivered events but would not automatically forward them to InventoryService, and ordering could be lost. Extending the retry policy to 72 hours is not possible because Event Grid has a fixed 24-hour limit. Manual handshake validation applies only to webhook endpoint setup and does not address long offline periods or durability.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is an Azure Service Bus queue and how does it work?