Question

Difficulty: HardShared Access Signatures and Token-based Storage Security

An organization has a web application that provides temporary write access to an Azure Blob Storage container named `uploads` for external clients. You must meet the following requirements:
- Enable the security team to revoke access tokens immediately without impacting other clients or rotating the storage account keys.
- Limit the lifetime of individual client tokens to a maximum of 30 minutes.
- Enforce the use of secure connections only.

Which two actions should you perform to meet these requirements?

  1. Create a stored access policy on the container and specify the policy identifier when generating a service-level SAS token.Answer
  2. Set the allowed protocols on the stored access policy or the generated SAS token to HTTPS only.Answer
  3. C
    Create a stored access policy at the storage account level and associate it with an account-level SAS token.
  4. D
    Generate a SAS token signed with Microsoft Entra ID credentials and associate it with a stored access policy.

Answer

Create a stored access policy on the container and specify the policy identifier when generating a service-level SAS token, and set the allowed protocols on the stored access policy or the generated SAS token to HTTPS only.
The correct actions are to create a stored access policy on the container and reference it when generating a service-level SAS, and to enforce HTTPS only on the policy or token. A stored access policy allows for immediate revocation of the associated SAS tokens by modifying or deleting the policy. Restricting the protocol to HTTPS ensures all transit is encrypted.

Step-by-Step Solution

1
Analyze the requirement for immediate token revocation without rotating the storage account keys.
Identify that a stored access policy on the container is required because deleting or modifying the policy immediately revokes any associated service-level SAS tokens.
This satisfies the revocation requirement without impacting other clients or requiring a key rotation.
2
Analyze the requirement for secure connections.
Configure the SAS token or stored access policy to enforce HTTPS only.
This blocks any unencrypted HTTP requests from clients.
3
Evaluate the options against account-level and user-delegated SAS tokens.
Recognize that account-level SAS tokens and SAS tokens signed with Microsoft Entra ID (user delegation) do not support stored access policies.
This rules out the incorrect configurations.

Key Concept

Implementing container-level stored access policies to manage and revoke Service Shared Access Signatures (SAS) with protocol constraints.
Rate this question