Practise the standard verbs for promoting build artifacts safely through environments.
0 / 5 completed
1 / 5
Fill in: 'We ___ the exact same build artifact through staging and production so what's tested is byte-for-byte what ships.'
We 'promote an artifact' — the standard, established CI/CD collocation for moving a build through environments without rebuilding. The other options aren't the recognised term here.
2 / 5
Fill in: 'Rebuilding from source at each stage instead of promoting one artifact can ___ subtle differences between what was tested and what deploys.'
We say rebuilding will 'cause' drift between environments — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every artifact with its commit hash and build number so a specific production deploy can always be traced back.'
We 'tag an artifact' — the standard, established collocation for labelling a build with identifying metadata. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ manual approval before promoting an artifact to production so a deploy always has a named, accountable approver.'
We 'require' approval — the standard, established collocation for mandating a gate before an action proceeds. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ old artifacts from the registry after a retention period so storage doesn't fill with builds nobody will ever deploy.'
We 'purge' artifacts — the standard, established collocation for removing old or unused build outputs. The other options aren't the recognised term here.