Question 250
An application backend sends the storage account master key to customer devices so they can download files, and now security requires central revocation of those customers' temporary links. What should the backend change?
Explanation
Correct Answer
Shared account keys grant powerful storage capabilities and are unsuitable for customer devices. Keep account-key material on protected infrastructure when service SAS signing is used, distribute only short-lived resource-scoped SAS URLs, and associate eligible service SAS with stored access policies when central revocation is needed. If supported, Entra user delegation SAS avoids account-key signing but has a different revocation mechanism. Rotate compromised shared keys through a planned process and verify clients can no longer use them.
Incorrect Answers
Anonymous access removes the authenticated temporary link requirement and can expose private data to anyone with a URL. It cannot replace individual customer revocation. Keep containers private and use correctly scoped delegated tokens with a documented revocation design. It also contradicts the requirement to preserve private customer content.
Subscription Owner is vastly broader than temporary file downloads and provides administrative authority rather than centrally revocable customer SAS links. It may increase the attack surface without improving key control. Issue least-privilege tokens and protect signing credentials instead. The storage owner must control the temporary authorization boundary.
A stored access policy constrains eligible service SAS tokens that reference it, not the storage account's master key itself. A customer with an account key can bypass the intended link-level delegation pattern by signing other requests. Stop distributing shared keys and move to scoped delegated access.