An organization needs to grant a third-party audit application read-only access to an Azure Blob storage container for exactly 30 days. Security policies require that administrators must have the ability to immediately revoke this access at any time if a security compromise is suspected, without rotating the storage account keys or affecting other active integrations. Which access control strategy should you recommend?
- AGenerate an ad-hoc service Shared Access Signature (SAS) token with read permissions and a 30-day expiration directly using the storage account key.
- Create a Stored Access Policy on the container with read permissions and a 30-day expiration, then generate a SAS token associated with this policy.Cevap
- CAssign the Storage Blob Data Reader role directly to the partner application's service principal.
- DAdd the partner application's service principal to an Entra ID security group and assign the group a permanently active Storage Blob Data Reader role assignment.
Cevap
Create a Stored Access Policy on the container with read permissions and a 30-day expiration, then generate a SAS token associated with this policy.
The correct option outlines using a Stored Access Policy on the blob container to control the SAS token's permissions and lifetime. By linking the SAS token to a Stored Access Policy, administrators can revoke the access instantly by deleting or changing the policy, without impacting any other integrations or rotating account access keys.
Adım Adım Çözüm
Anahtar Kavram
Stored Access Policies provide a way to group Shared Access Signatures (SAS) and place additional constraints on them, enabling revocation of the SAS tokens by modifying or deleting the policy rather than rotating storage keys.