Practise the standard verbs for writing Azure DevOps pipelines securely.
0 / 5 completed
1 / 5
Fill in: 'We ___ pipeline stages explicitly in YAML, rather than a classic UI pipeline nobody can actually review in a pull request.'
We 'define stages' — the standard, simple collocation for structuring a pipeline in YAML. The other options are less idiomatic here.
2 / 5
Fill in: 'Hardcoding a secret directly in pipeline YAML can ___ a credential exposed to anyone with actual repo read access.'
We say hardcoding a secret will 'leave' a credential exposed — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ variable groups for secrets consistently, rather than scattering values across files nobody can actually rotate cleanly.'
We 'use variable groups' — the standard, simple collocation for centralizing pipeline secrets. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every pipeline template against a linked schema, rather than merging YAML nobody's actually validated syntactically.'
We 'validate a template' — the standard, simple collocation for checking YAML against a schema. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ pipeline run history for flaky stages weekly, rather than re-running a failed job without actually investigating why.'
We 'review history' — the standard, simple collocation for checking pipeline runs for patterns. The other options aren't idiomatic here.