Queue storage basics in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Message Visibility Timeout Behavior

In Azure Queue Storage, what happens to a message after it is retrieved by a client but not deleted within the visibility timeout period?

A The message becomes visible again in the queue for other clients to process.

B The message is permanently deleted from the queue.

C The message is moved to a dead-letter queue automatically.

D The message is duplicated and both copies remain in the queue.

💡 Hint

Think about how Azure Queue Storage ensures messages are not lost if a client fails to process them.

When a message is retrieved, it becomes invisible for a set time (visibility timeout). If not deleted within this time, it reappears for processing by other clients.

❓ Architecture

intermediate

Best Practice for Processing Messages Exactly Once

Which design approach best ensures that each message in Azure Queue Storage is processed exactly once, even if the client crashes during processing?

A Delete the message immediately after retrieving it from the queue.

B Retrieve the message, process it, then delete it only after successful processing.

C Process the message multiple times to ensure it is handled at least once.

D Use a separate database to track processed messages and never delete messages from the queue.

💡 Hint

Consider how to avoid losing messages if a client fails after retrieval but before processing.

Deleting the message only after successful processing ensures messages are not lost if the client crashes during processing.

❓ Configuration

advanced

Configuring Message Time-to-Live (TTL)

You want messages in an Azure Queue to expire automatically after 2 hours if not processed. Which configuration achieves this?

A Configure the queue to move expired messages to a dead-letter queue after 2 hours.

B Set the queue's visibility timeout to 2 hours.

C Set the message TTL property to 7200 seconds when adding messages to the queue.

D Enable soft delete on the queue with a 2-hour retention period.

💡 Hint

TTL controls how long a message stays in the queue before automatic deletion.

Setting the message TTL to 7200 seconds (2 hours) ensures messages expire and are removed if not processed within that time.

❓ security

advanced

Securing Access to Azure Queue Storage

Which method provides the most secure way to grant temporary, limited access to an Azure Queue for a client application?

A Use a Shared Access Signature (SAS) token with specific permissions and expiry time.

B Make the queue public so anyone can access it without authentication.

C Share the storage account access key with the client application.

D Embed the storage account key directly in the client application code.

💡 Hint

Think about granting limited and time-bound access without exposing full account keys.

SAS tokens allow fine-grained, temporary access without exposing the full storage account keys, enhancing security.

🧠 Conceptual

expert

Understanding Message De-duplication in Azure Queue Storage

Azure Queue Storage does not natively support message de-duplication. Which approach best handles duplicate messages in a distributed system using Azure Queue Storage?

A Delete messages immediately after retrieval to avoid duplicates.

B Rely on Azure Queue Storage to automatically discard duplicate messages.

C Set the queue visibility timeout to zero to prevent duplicates.

D Implement an idempotent message processing logic that ignores duplicates based on unique message IDs stored externally.

💡 Hint

Consider how to handle duplicates when the storage service does not provide built-in support.

Since Azure Queue Storage does not remove duplicates, the application must track processed message IDs externally and ignore repeats.