When a cooperative grower drops a harvest CSV into a Blob Storage container, a county Function should start processing immediately. Which trigger should the developer choose?
Select an answer to reveal the explanation.
Short Explanation
New file lands, function wakes—that’s a Blob trigger doing data-operation duty. Don’t babysit the container with a timer when Storage already rings the doorbell.
Full Explanation
Blob Storage triggers are the Functions data-operation pattern for reacting when blobs appear. Timers that list containers introduce latency and miss the evented model. Requiring a separate HTTP callback or an empty queue trigger does not start work from the CSV upload itself. Event Grid–backed blob patterns may also apply at scale, but the core choice remains an evented blob trigger versus polling.