Two worker pods poll the same municipal Queue. What does the visibility timeout provide after one consumer receives a message?
Select an answer to reveal the explanation.
Short Explanation
Visibility timeout is a short processing lock: after receive, the message is hidden from others so two workers do not double-handle it. It is not retention, not a Streaming offset, and not an Events filter.
Full Explanation
Official Queue visibility: after a consumer receives a message it is hidden for the visibility timeout (queue default 30 seconds; configurable in documented ranges at queue or get time). That temporary exclusivity prevents concurrent processing. Retention controls how long undeleted messages survive; visibility is the in-flight lock. Streaming offsets and Events filters are different concepts.