A knapweed survey hands out service SAS URIs whose expiry is baked into each URI, and the team cannot revoke one class of tokens without chasing every link. What should the developer do?
Select an answer to reveal the explanation.
Short Explanation
Ad hoc SAS stamps expiry into every URI—painful to revoke. Hang a service SAS off a stored access policy and you can change the clock in one spot.
Full Explanation
A service SAS may be ad hoc or associated with a stored access policy on the container (or appropriate resource). Policy-based signatures allow updating expiry or permissions centrally and support revocation by modifying or deleting the policy. Officially, user-delegation and account SAS are ad hoc only and do not use stored access policies.