Practise the standard verbs for rolling out an API key rotation safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a new API key alongside the old one first, so every consumer has a working overlap window instead of a single hard cutover moment.'
We 'roll out a key' — the standard, simple collocation for introducing a new credential gradually. The other options are less idiomatic here.
2 / 5
Fill in: 'Rotating a key with no overlap window and no advance notice can ___ every downstream integration failing at once the instant the old key stops working.'
We say an abrupt rotation will 'leave' integrations failing simultaneously — the standard, natural collocation for the resulting outage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the old key only after usage metrics confirm every known consumer has actually switched over, not just after the calendar date we originally announced.'
We 'revoke a key' — the standard, established collocation for permanently disabling an old credential. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ the rotation across consumer groups in stages, rather than switching every integration over on the exact same day regardless of size or risk.'
We 'stagger a rotation' — the standard, simple collocation for spreading a key change across time to limit blast radius. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ every affected consumer well ahead of the deadline, with a specific date and a specific action required, rather than burying the change in a general release note.'
We 'notify a consumer' — the standard, simple collocation for directly informing affected parties of an upcoming change. The other options aren't idiomatic here.