A developer is designing an integration solution that buffers messages using Azure Queue Storage. The developer expects some message payloads to occasionally exceed the standard size limit of a single queue message.
What is the maximum message size supported for a single message in Azure Queue Storage, and how should payloads exceeding this limit be handled?
- ; store the payload in Azure Blob Storage and place the blob reference URI in the queue message.Answer
- B; store the payload in Azure Service Bus and place the Service Bus message ID in the queue message.
- C; split the payload across multiple queue messages and use a correlation ID to reassemble them.
- D; generate a Shared Access Signature (SAS) token with write permissions to temporarily bypass the limit.
Answer
The maximum message size limit for Azure Queue Storage is . Payloads exceeding this limit should be stored in Azure Blob Storage, and the reference URI to the blob should be placed in the queue message.
The correct answer specifies that the maximum message size limit for Azure Queue Storage is . To handle payloads exceeding this limit, the developer should implement the claim-check pattern. This involves uploading the large payload to Azure Blob Storage and storing only the resulting blob URI in the queue message. The consumer can then read the URI from the queue and download the payload directly from Blob Storage.
Step-by-Step Solution
Key Concept
Azure Queue Storage message size limit and the claim-check pattern using Azure Blob Storage.