Examkin

Question

Difficulty: MediumImplement Azure Queue Storage Solutions

You are designing an integration solution that uses Azure Queue Storage to process order messages. The application client must occasionally submit order details that exceed 64 KB64\text{ KB} up to a maximum of 1 MB1\text{ MB}. Additionally, the client requires temporary access to add messages to the queue, and this access must expire after 15 minutes15\text{ minutes}.

Which two actions should you perform? (Select TWO.)

  1. Store payloads that exceed 64 KB64\text{ KB} in Azure Blob Storage, and write the blob reference URL to the queue message.Answer
  2. Generate a service-level Shared Access Signature (SAS) token configured with only the Add permission and an expiration time of 15 minutes15\text{ minutes}.Answer
  3. C
    Configure the queue properties in the Azure portal to allow a maximum message size of 1 MB1\text{ MB}.
  4. D
    Generate an account-level Shared Access Signature (SAS) token configured with Read, Write, and Delete permissions and no expiration time.
  5. E
    Assign a system-assigned managed identity to the client and grant it the Owner role on the storage account resource.

Answer

Store payloads that exceed 64 KB64\text{ KB} in Azure Blob Storage, writing the blob reference URL to the queue message, and generate a service-level SAS token configured with only the Add permission and an expiration time of 15 minutes15\text{ minutes}.
To handle message sizes larger than 64 KB64\text{ KB} (such as the 1 MB1\text{ MB} payloads), you must use the Claim Check pattern: save the payload to Azure Blob Storage and write the corresponding blob URL to the queue message. To provide the client application with secure, temporary, and limited access to write messages to the queue, you should generate a service-level SAS token configured with the Add permission only, expiring after 15 minutes15\text{ minutes}.

Step-by-Step Solution

1
Evaluate the message size requirement.
Identify that because some payloads are up to 1 MB1\text{ MB} (which exceeds the Azure Queue Storage limit of 64 KB64\text{ KB}), a workaround is required.
Azure Queue Storage cannot directly store messages larger than 64 KB64\text{ KB}.
2
Implement the Claim Check pattern.
Store the larger payload in Azure Blob Storage, and put its reference URL in the queue message.
This allows referencing large datasets while staying within the 64 KB64\text{ KB} queue message size limit.
3
Determine the authentication mechanism for temporary write-only client access.
Create a service-level SAS token targeting the specific queue with the Add permission and an expiration window of 15 minutes15\text{ minutes}.
This implements the principle of least privilege (only write access to the queue) and enforces the temporal constraint.

Key Concept

Handling large queue messages using the Claim Check pattern and securing queue access using least-privilege SAS tokens.
Rate this question

Topics

Implement Azure Queue Storage Solutions