A payments team is designing a producer that pushes JSON order events onto a basic Azure Storage queue. An engineer proposes sending payloads of roughly 100 KB per event. What is the largest encoded size a single queue entry can have for current API versions?
Show answer and explanation
Answer: C
A message on an Azure Storage queue can be up to 64 KiB after encoding when using API version 2011-08-18 or later. Older API versions capped entries at 8 KiB. A 100 KB order event would therefore exceed the ceiling, so the producer should write the full JSON to Blob Storage and enqueue only a small reference such as the container and blob name. Base64 or other encoding counts toward the 64 KiB limit, which reduces the usable payload further.
Why the other options are wrong
- A. 16 KiB is below the current queue entry ceiling. Modern API versions accept entries four times larger than this, so the figure understates what the service allows.
- B. 32 KiB is not the documented maximum for a queue entry. The limit for current API versions is 64 KiB, which is double this value.
- D. 128 KiB is above what a queue entry can hold. Payloads that large must be offloaded to Blob Storage, or split, with the queue carrying only a pointer.