Fabrikam created a stored access policy named policy1 on container1 in a storage account and issued a partner a service SAS associated with policy1. This SAS is the only SAS associated with policy1. The SAS has been leaked. You must invalidate this SAS without regenerating the storage account keys, and the other service SAS and account SAS tokens issued from the same account must keep working. What should you do?
Show answer and explanation
Answer: D
Explanation
You revoke a stored access policy by deleting it, changing its signed identifier, or changing its expiry time to a value in the past. Changing the expiry time to the past causes all signatures associated with that policy to expire.[1] A stored access policy lets you revoke permissions for a service SAS without regenerating the storage account keys.[2]
Regenerating the account keys is the method the requirements rule out.[2] A SAS expiration policy logs out-of-policy SAS by default, and its Block action denies requests made with out-of-policy SAS. However, the expiration action isn’t supported for a service SAS with a stored access policy, so it can’t invalidate the SAS associated with policy1.[4] Setting AllowSharedKeyAccess to false denies service SAS and account SAS requests for all Azure Storage services, so it also blocks the other SAS tokens that must keep working.[3]