Hotspot Question You have an Azure subscription that contains a user named User1 and a storage account named storage1. The storage1 account contains the resources shown in the following table. In…

Submitted by hans_de· Mar 6, 2026Implement and manage storage security in Azure - specifically configuring and managing Shared Access Signatures (SAS) and understanding how storage account keys affect SAS validity and resource-level access permissions.

Question

Hotspot Question You have an Azure subscription that contains a user named User1 and a storage account named storage1. The storage1 account contains the resources shown in the following table. In storage1, you create a shared access signature (SAS) named SAS1 as shown in the following exhibit. To which resources can User1 write on July 1, 2022 by using SAS1 and key1? To answer select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibits

Explanation

This question involves a Shared Access Signature (SAS) with specific permissions tied to an account key (key1). A SAS token is valid only within its defined date range and for the resource types/services specified. If SAS1 was created with key1 and key1 is rotated or regenerated after the SAS is created but before July 1, 2022, the SAS becomes immediately invalid regardless of its expiry date. The write access is limited to the specific services (Blob, File, Queue, Table) and resource types (Service, Container/Share, Object) that were checked during SAS creation.

Topics

#Shared Access Signature (SAS)#Azure Storage Security#Storage Account Keys#Blob Storage Access Control

Community Discussion

No community discussion yet for this question.

Full AZ-500 Practice