A nimbus-radar hut leaks a service SAS that referenced stored access policy field. How should the developer revoke access without breaking every other client?
Select an answer to reveal the explanation.
Short Explanation
If the leak rode on policy field, edit or delete that policy and those signatures go dark—without nuking the account keys and every other client.
Full Explanation
Revoking a service SAS associated with a stored access policy is done by altering or removing that policy, which invalidates signatures that reference it. Rotating account keys revokes all key-signed SAS and credentials and is a broader blunt instrument. User-delegation SAS revocation paths involve the user delegation key or RBAC changes and differ from policy-based service SAS revocation.