Azure Key Vault Secret Rotation Language Collocations
Practise the standard verbs for rotating secrets in Azure Key Vault.
0 / 5 completed
1 / 5
Fill in: 'We ___ every stored secret on a fixed schedule in Key Vault so a credential leaked months ago quietly stops being valid before anyone even reports it.'
We 'rotate a secret' — the standard, established collocation for periodically replacing a credential's value. The other options aren't the recognised term here.
2 / 5
Fill in: 'Rotating a secret without updating every dependent service's reference can ___ half the fleet still authenticating with a value that's just been invalidated.'
We say an uncoordinated rotation will 'leave' some services broken — the standard, natural collocation for the resulting outage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a rotation schedule per secret type rather than a single blanket interval, since a database password and a short-lived API token don't share the same risk profile.'
We 'schedule a rotation' — the standard, simple collocation for planning when a secret gets refreshed. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ access logs for every secret in the vault periodically, so an application reading a secret it was never granted no longer goes unnoticed.'
We 'audit' access logs — the standard, simple collocation for periodically reviewing who read what. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the previous secret version immediately once every consumer confirms the new one works, rather than leaving a valid old credential sitting around indefinitely.'
We 'revoke a version' — the standard, established collocation for invalidating an old credential once it's no longer needed. The other options aren't the recognised term here.