A sage-flat worker dequeues a resize job and another worker immediately grabs the same message. What Queue Storage behavior should the developer rely on to hide in-flight work?
Select an answer to reveal the explanation.
Short Explanation
Storage queues do not speak peek-lock. On dequeue, visibility timeout hides the message; finish and delete it, or it pops back when the timeout expires.
Full Explanation
Azure Queue Storage uses visibility timeout as the lock analog: after a get, the message is invisible to other workers until the timeout elapses, then it reappears unless deleted. Service Bus peek-lock APIs, Event Grid retries, and Cosmos TTL are not the Storage queue invisibility mechanism.