AZ-204 Develop for Azure storage Practice Question
Which THREE of the following are true about Azure Storage queues? (Choose three.)
⚠ Common exam trap
Watch out — candidates often confuse Azure Storage queues with Azure Service Bus queues, leading them to select the 1 MB message size limit (which applies to Service Bus) instead of the correct 64 KB limit for Storage queues.
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 maximum time-to-live for a message is 7 days.
Option B is correct because an Azure Storage queue message can have a time-to-live of at most 7 days (the default is also 7 days, and it can be set to any value up to that maximum, or -1 for no expiry). Option D is correct because the maximum size of a single Azure Storage queue message is 64 KB; larger payloads must be split or stored elsewhere (e.g., in a blob) with only a reference placed on the queue. Option E is correct because the visibility timeout is exactly the mechanism that makes a dequeued message invisible to other consumers for a specified period while the consumer processes it, after which it becomes visible again if not deleted. Option A is not correct because Azure Storage queues guarantee at-least-once delivery and generally approximate FIFO ordering, but they do not guarantee strict FIFO order. Option C is not correct because 1 MB is not the queue message limit; 64 KB is the actual maximum for Azure Storage queue messages.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Messages are processed in strict FIFO order.
Why it's wrong here
Azure Storage Queues are primarily designed for high throughput and availability in a distributed environment, not for strict message ordering guarantees. While messages are generally dequeued in a first-in, first-out manner under ideal conditions, the distributed nature of the service, concurrent consumers, and potential internal partitioning mean that strict FIFO processing cannot be guaranteed. This makes them suitable for scenarios where message order is not absolutely critical for correctness.
- ✓
The maximum time-to-live for a message is 7 days.
Why this is correct
Azure Storage Queue messages have a configurable time-to-live (TTL) property, which dictates how long a message will remain in the queue before it is automatically removed if not processed. The maximum allowable value for this time-to-live is indeed 7 days, or 604,800 seconds. If a message is enqueued without specifying a TTL, it defaults to this 7-day maximum, ensuring messages do not persist indefinitely and preventing queue bloat.
- ✗
Messages can be up to 1 MB in size.
Why it's wrong here
The maximum size for a single message in an Azure Storage Queue is strictly limited to 64 KB, not 1 MB. This limit includes the message body, which is often Base64 encoded, adding to its overall size. Attempting to enqueue a message that exceeds this 64 KB threshold will result in a client-side error. For applications requiring larger payloads, the common pattern is to store the data in Azure Blob Storage and place a reference (e.g., a URL) to the blob within the 64 KB queue message.
- ✓
Messages can be up to 64 KB in size.
Why this is correct
Azure Storage Queue messages are designed to be lightweight and efficient for coordinating asynchronous tasks and work items. Each individual message has a maximum size limit of 64 KB. This constraint applies to the entire message content, including any metadata and the Base64 encoding that is typically applied to the message body. This size limit encourages developers to use queues for small, actionable commands or references to larger data stored elsewhere.
- ✓
The visibility timeout allows a consumer to hide a message from other consumers while processing it.
Why this is correct
When a message is successfully dequeued from an Azure Storage Queue, it is not immediately deleted. Instead, a visibility timeout is applied, rendering the message invisible to other consumers for a specified duration. This mechanism is crucial for fault tolerance, as it allows the current consumer time to process the message. If the consumer fails before deleting the message, it will automatically become visible again after the timeout expires, allowing another consumer to pick it up and ensure eventual processing.
Go deeper
Related to this question
About these practice questions
This AZ-204 question is part of Courseiva's 883-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.