Work items for a city permits desk already land on an Azure Storage queue from another function’s output binding. The processor Function should run when a message appears. Which trigger fits?
Select an answer to reveal the explanation.
Short Explanation
Messages already ride the Storage queue—meet them with a Queue Storage trigger. No need to rip out the pipes for Service Bus sessions just to process what is already enqueued.
Full Explanation
Azure Functions Queue Storage triggers run when messages arrive on a storage queue, matching an upstream output-binding producer. Redesigning onto Service Bus sessions is a Domain 5 messaging topology choice, not required for this Functions data-operation trigger. Timers and unrelated Cosmos triggers do not consume the queue messages.