A sedge-meadow hydrology team wants one container-side place to revise expiry for several service SAS tokens without regenerating each signature string from scratch. What should the developer define?
Select an answer to reveal the explanation.
Short Explanation
A stored access policy is the master checklist pinned on the container: change expiry once, and service SAS tokens that point at that policy follow along (up to five policies). User-delegation and account SAS do not ride that container policy the same way.
Full Explanation
Stored access policies are defined on the blob container and can be referenced by service SAS tokens so permissions and validity can be updated centrally (maximum five per container). Official guidance: user-delegation SAS and account SAS do not use container stored access policies. Cosmos TTL is unrelated.