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.

Practice

1. What is the main purpose of Azure Queue Storage?

easy

A. To store messages that help different parts of an app communicate

B. To store large files like videos and images

C. To run virtual machines in the cloud

D. To create databases for storing user data

Solution

1. Step 1: Understand the role of Azure Queue Storage

   Azure Queue Storage is designed to hold messages temporarily so different parts of an application can send and receive information reliably.

2. Step 2: Compare options with this purpose

   Options B, C, and D describe other Azure services like Blob Storage, Virtual Machines, and Databases, which are not for message passing.

3. Final Answer:

   To store messages that help different parts of an app communicate -> Option A

4. Quick Check:

   Queue Storage = Message storage for app communication [OK]

Hint: Queue Storage is for messages, not files or VMs [OK]

Common Mistakes:

• Confusing queue storage with blob storage
• Thinking queue storage runs code or VMs
• Mixing queue storage with database services

2. Which of the following is the correct way to add a message to an Azure queue using Azure SDK syntax?

easy

A. queueClient.addMessage('Hello World')

B. queueClient.sendMessage('Hello World')

C. queueClient.enqueueMessage('Hello World')

D. queueClient.pushMessage('Hello World')

Solution

1. Step 1: Recall Azure Queue Storage SDK method for adding messages

   The correct method to add a message to a queue is sendMessage.

2. Step 2: Check other options for correctness

   Methods like addMessage, enqueueMessage, and pushMessage are not valid Azure SDK methods for queues.

3. Final Answer:

   queueClient.sendMessage('Hello World') -> Option B

4. Quick Check:

   Send message = sendMessage() method [OK]

Hint: Use sendMessage() to add messages to Azure queues [OK]

Common Mistakes:

• Using incorrect method names like addMessage or pushMessage
• Confusing queue methods with blob storage methods
• Forgetting to call the method on the queue client object

3. Given this code snippet, what will be the output after reading the message?

const { QueueClient } = require('@azure/storage-queue');
const queueClient = new QueueClient('https://myaccount.queue.core.windows.net/myqueue', credential);

async function readMessage() {
  const response = await queueClient.receiveMessages();
  if (response.receivedMessageItems.length > 0) {
    return response.receivedMessageItems[0].messageText;
  } else {
    return 'No messages';
  }
}

readMessage().then(console.log);

medium

A. The text of the first message in the queue

B. An error because receiveMessages() does not exist

C. No messages if the queue is empty

D. The number of messages in the queue

Solution

1. Step 1: Understand receiveMessages() behavior

   The receiveMessages() method fetches messages from the queue. If messages exist, they are in receivedMessageItems.

2. Step 2: Analyze the code logic

   If there is at least one message, the code returns the text of the first message. Otherwise, it returns 'No messages'.

3. Final Answer:

   The text of the first message in the queue -> Option A

4. Quick Check:

   receiveMessages() returns messages array [OK]

Hint: receiveMessages() returns messages array, pick first text [OK]

Common Mistakes:

• Thinking receiveMessages() returns count or error
• Ignoring the check for empty message list
• Confusing method names or properties

4. You wrote this code to delete a message from an Azure queue but it fails:

const response = await queueClient.receiveMessages();
const message = response.receivedMessageItems[0];
await queueClient.deleteMessage(message.messageId);

What is missing to fix the error?

medium

A. You should use removeMessage() instead of deleteMessage()

B. You must call sendMessage() before deleteMessage()

C. You need to provide the message's popReceipt along with messageId to delete

D. No fix needed; the code is correct

Solution

1. Step 1: Understand deleteMessage() requirements

   To delete a message, Azure requires both the messageId and the popReceipt which proves you received the message.

2. Step 2: Identify missing parameter in code

   The code only passes messageId but misses popReceipt, causing failure.

3. Final Answer:

   You need to provide the message's popReceipt along with messageId to delete -> Option C

4. Quick Check:

   Delete needs messageId + popReceipt [OK]

Hint: Delete message requires popReceipt with messageId [OK]

Common Mistakes:

• Passing only messageId to deleteMessage()
• Using wrong method name like removeMessage()
• Assuming sendMessage() is needed before delete

5. You want to build a system where multiple workers process messages from an Azure queue without processing the same message twice. Which approach best achieves this?

hard

A. Workers use peekMessages() to read messages and delete them immediately

B. Workers read messages but never delete them, so messages stay in the queue

C. Workers delete messages before processing to avoid duplicates

D. Each worker calls receiveMessages(), processes the message, then deletes it using messageId and popReceipt

Solution

1. Step 1: Understand message processing with Azure queues

   To avoid duplicate processing, workers must receive messages, process them, then delete them to remove from the queue.

2. Step 2: Evaluate each option

   Each worker calls receiveMessages(), processes the message, then deletes it using messageId and popReceipt correctly describes the receive-process-delete cycle with required parameters. Workers read messages but never delete them, so messages stay in the queue leaves messages undeleted causing duplicates. Workers delete messages before processing to avoid duplicates deletes before processing risking lost messages. Workers use peekMessages() to read messages and delete them immediately uses peekMessages() which does not lock or remove messages, so duplicates occur.

3. Final Answer:

   Each worker calls receiveMessages(), processes the message, then deletes it using messageId and popReceipt -> Option D

4. Quick Check:

   Receive, process, then delete to avoid duplicates [OK]

Hint: Process then delete messages to prevent duplicates [OK]

Common Mistakes:

• Deleting messages before processing
• Using peekMessages() for processing
• Not deleting messages after processing