AZ-204 Practice Question: Queue Storage visibility timeout behavior when…
A background worker retrieves a message from Azure Queue Storage and begins processing. The processing logic takes longer than the configured visibility timeout. Before the worker finishes, the timeout expires. What happens to the message?
⚠ Common exam trap
It's easy for candidates to assume the dequeue operation permanently locks or deletes the message, but Azure Queue Storage only hides it temporarily, and the worker must explicitly delete it to prevent reprocessing.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The message becomes visible again in the queue and another worker can dequeue it
When the visibility timeout expires, the message becomes visible again in the queue because Azure Queue Storage uses a lease-based mechanism. The worker that dequeued the message loses its exclusive visibility lease, allowing another worker to dequeue and process the same message. This ensures at-least-once delivery semantics, preventing message loss if a worker fails or takes too long.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The message becomes visible again in the queue and another worker can dequeue it
Why this is correct
This is the core at-least-once delivery guarantee. The visibility timeout is a lease, not a lock. When the lease expires, the queue re-exposes the message. To prevent double-processing, the worker should call UpdateMessage to extend the timeout, or ensure processing is idempotent.
- ✗
The message is permanently deleted because the worker already dequeued it
Why it's wrong here
When a worker dequeues a message from Azure Queue Storage, the message is not immediately deleted. Instead, it becomes invisible to other consumers for a specified duration, known as the visibility timeout. The worker is responsible for explicitly calling the DeleteMessage operation upon successful processing to remove the message from the queue. If the worker fails to delete the message within the visibility timeout, the message will reappear in the queue, making it available for other workers to process, ensuring at-least-once delivery.
- ✗
The message moves to a dead-letter queue after the visibility timeout expires
Why it's wrong here
Azure Queue Storage does not have a built-in dead-letter queue. Messages that exceed the maximum dequeue count are deleted or can be moved to a poison message queue only if the application implements that logic explicitly.
- ✗
Processing continues uninterrupted; the visibility timeout applies only to the initial retrieval window
Why it's wrong here
The visibility timeout is a real deadline. Once it expires, the queue re-exposes the message regardless of whether the original worker is still processing. The worker must extend the timeout via UpdateMessage if processing takes longer than expected.
Go deeper
Related to this question
About these practice questions
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.