Practise the standard verbs for submitting changes through an advisory board process.
0 / 5 completed
1 / 5
Fill in: 'We ___ a high-risk change to the change advisory board before deploying, rather than a release nobody outside the team's actually reviewed.'
We 'submit a change' — the standard, simple collocation for bringing a risky deployment before a review board. The other options are less idiomatic here.
2 / 5
Fill in: 'Skipping the advisory board on a risky change can ___ a dependency conflict live in production nobody's actually flagged beforehand.'
We say a skipped review will 'leave' a conflict unflagged — the standard, natural collocation for the resulting production risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the rollback plan alongside every change request, rather than a deploy nobody's actually prepared a fallback for.'
We 'attach a plan' — the standard, simple collocation for including a rollback plan with a change submission. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every approved change against its scheduled maintenance window, rather than a deploy nobody's actually confirmed the timing of.'
We 'check a change' — the standard, simple collocation for confirming an approved change fits its window. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ board approval turnaround monthly to keep releases moving, rather than a queue nobody's actually noticed backing up.'
We 'review turnaround' — the standard, simple collocation for monitoring how fast the advisory board approves changes. The other options aren't idiomatic here.