AZ-400 Pipeline Variables and Templates 4

Question 1

An organization wants to mandate that all pipelines include a security scanning job. Which Azure DevOps feature best enforces this?

Accepted Answer

Required pipeline templates via the `extends` keyword and protected template resources

Answer

Required templates configured with `extends` and protected as a resource force every consuming pipeline to include the mandated jobs.

Question 2

What is the correct way to iterate over an `object` parameter (a list) inside a YAML template using `each`?

Accepted Answer

${{ each item in parameters.list }}:

Answer

The `${{ each item in parameters.list }}:` template expression iterates over an object parameter list to generate repeated YAML blocks.

Question 3

A YAML pipeline sets a variable with `isReadonly: true`. What is the effect?

Accepted Answer

The variable cannot be overridden at queue time by users

Answer

Setting `isReadonly: true` on a variable prevents users from overriding its value when manually triggering a pipeline run.

Question 4

Which approach correctly maps an output variable from job A to job B within the same stage?

Accepted Answer

In job B's variables section: `$[dependencies.JobA.outputs['stepA.myVar']]`

Answer

Within the same stage, cross-job output variables are referenced using `$[dependencies.JobName.outputs['stepName.varName']]`.

Question 5

What happens when you link a variable group to a pipeline but the Azure Key Vault secret has been deleted?

Accepted Answer

The pipeline run fails when it attempts to fetch the deleted secret

Answer

If a Key Vault secret is deleted, the pipeline fails at runtime when Azure DevOps attempts to retrieve the missing secret value.

AZ-400 Practice Test