AZ-400 Pipeline Variables and Templates 5

Question 1

Which YAML pipeline feature lets you define a reusable set of steps in one file and include them in multiple jobs across different pipelines?

Accepted Answer

Step templates referenced with `- template:` inside a `steps:` block

Answer

Step templates are YAML files containing a `steps:` list that can be included in any job using `- template: path/to/steps.yml`.

Question 2

What is a key security benefit of using `templateContext` when passing data to a required template?

Accepted Answer

It allows the template to validate and restrict what the extending pipeline can configure

Answer

The `templateContext` property lets the required template inspect and validate properties passed by the consuming pipeline, enforcing security constraints.

Question 3

A pipeline uses a variable group named 'Production-Secrets' that requires approval. At which point in the run is the approval gate triggered?

Accepted Answer

When the stage or job that references the variable group is about to execute

Answer

Approval gates on protected variable groups are triggered when the stage or job referencing the group is about to begin execution.

Question 4

You need a pipeline parameter that accepts only 'dev', 'staging', or 'prod'. Which parameter definition enforces this constraint?

Accepted Answer

type: string with `values: [dev, staging, prod]`

Answer

Azure DevOps YAML pipeline parameters support a `values:` list under a `type: string` parameter to restrict accepted inputs to a predefined set.

Question 5

How do you make an output variable from a matrix job available to a downstream job?

Accepted Answer

Reference it using `$[dependencies.JobName.MatrixLeg.outputs['stepName.varName']]`

Answer

Matrix job outputs are referenced downstream using `$[dependencies.JobName.MatrixLegName.outputs['stepName.varName']]`, where the matrix leg name is the strategy key.

AZ-400 Practice Test

AZ-400 Practice Test

AZ-400 Pipeline Variables and Templates 5