Practise the standard verbs for rotating Kubernetes secrets safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ Kubernetes secrets on a fixed schedule, rather than a credential that sits unchanged for years nobody actually tracks.'
We 'rotate secrets' — the standard, simple collocation for periodically replacing Kubernetes credentials. The other options are less idiomatic here.
2 / 5
Fill in: 'Rotating a secret without updating dependent pods can ___ services crash-looping on a credential that's actually already stale.'
We say a mismatched rotation will 'leave' services crash-looping — the standard, natural collocation for the resulting outage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a new secret version alongside the old one during rotation, rather than a cutover nobody's actually staged safely.'
We 'stage a version' — the standard, simple collocation for rolling out a new secret gradually. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every pod's mounted secret against the latest version, rather than assuming a restart nobody's actually confirmed picked it up.'
We 'verify a mounted secret' — the standard, simple collocation for confirming pods loaded the rotated credential. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ old secret versions after a grace period, rather than leaving a stale credential valid nobody's actually revoked.'
We 'revoke a version' — the standard, simple collocation for invalidating an old secret after rotation. The other options aren't idiomatic here.