You are designing a secure, event-driven solution in Azure. You have an Event Grid custom topic and a Webhook endpoint. You must route events from the custom topic to the Webhook endpoint.
To ensure reliability and security, you must meet the following requirements:
- If event delivery to the Webhook fails, events must be dead-lettered to an Azure Storage blob container.
- Event Grid must write the dead-letter events to the container using a system-assigned managed identity.
- The subscription must be successfully validated.
Which four actions should you perform in sequence to configure the solution? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
- 1Enable a system-assigned managed identity on the Event Grid custom topic.
- 2Assign the Storage Blob Data Contributor role to the custom topic's managed identity on the destination storage account.
- 3Configure the Webhook endpoint to parse the incoming JSON array and return the validationCode from the subscription validation request.
- 4Create the Event Grid subscription, specifying the Webhook endpoint, the storage container for dead-lettering, and configuring the subscription to use the custom topic's identity for dead-letter delivery.
Answer
First, enable a system-assigned managed identity on the Event Grid custom topic. Second, assign the Storage Blob Data Contributor role to the custom topic's managed identity on the destination storage account. Third, configure the Webhook endpoint to parse the incoming JSON array and return the validationCode from the subscription validation request. Finally, create the Event Grid subscription, specifying the Webhook endpoint, the storage container for dead-lettering, and configuring the subscription to use the custom topic's identity for dead-letter delivery.
To set up the scenario securely and reliably, you must follow a dependency chain. First, you enable a system-assigned managed identity on the Event Grid custom topic so that the security principal exists in Microsoft Entra. Second, you assign the Storage Blob Data Contributor role to that newly created identity on the storage account, ensuring the permission is active. Third, you configure the Webhook endpoint application to handle the subscription validation handshake. Finally, you create the Event Grid subscription, which triggers both the synchronous Webhook handshake and the dead-letter write validation using the configured managed identity.
Step-by-Step Solution
Key Concept
Azure Event Grid custom topic subscription lifecycle, including managed identities for dead-lettering and endpoint validation handshakes.
Estimated Time:3m 0s