A jonquil-row storage account should notify a webhook on Microsoft.Storage.BlobCreated. Which Event Grid resource type surfaces that built-in Azure service event?
Select an answer to reveal the explanation.
Short Explanation
Built-in Azure events ride system topics. Wire a system topic on that storage account for BlobCreated, not a homemade custom topic for the same job.
Full Explanation
Built-in Azure service events such as Microsoft.Storage.BlobCreated are surfaced through an Event Grid system topic associated with the resource (here, the jonquil-row storage account). Subscribers attach to that system topic to receive the official event schema when blobs are created, without inventing a parallel bus.
A custom topic invented only for city council email digests fails this requirement: custom topics (and namespace topics) are for your application’s own events, not the built-in Azure resource events that system topics expose.
An Event Hubs partition key named BlobCreated with no Event Grid resource fails because a partition key is a routing property inside Event Hubs, not an Event Grid resource type that surfaces storage system events.
A Service Bus SQL filter on a queue that pretends to be Blob Storage fails because Service Bus filters messages already on a queue or topic; they do not replace an Event Grid system topic on the storage account.
Exam caveat: system topics are Azure-owned event sources; you subscribe to them—you do not “publish BlobCreated” yourself as if it were a custom app event. Operational check: enable the storage system topic (or confirm it exists), create a subscription for Microsoft.Storage.BlobCreated, upload a blob, and verify the handler receives the system event payload.