AZ-400 Pipeline Variables and Templates 3

Question 1

You want to reuse a YAML template stored in a different Azure DevOps repository. What must you configure first?

Accepted Answer

A resources.repositories reference with the repository alias

Answer

Cross-repository templates require declaring the source repo under `resources.repositories` with a `ref` and `type` before you can reference its templates.

Question 2

What is the syntax to reference a variable set in a previous stage named 'Build' from job 'CompileJob' within a subsequent stage?

Accepted Answer

$[stageDependencies.Build.CompileJob.outputs['stepName.outputVar']]

Answer

Cross-stage output variable references use `$[stageDependencies.StageName.JobName.outputs['stepName.varName']]` runtime expression syntax.

Question 3

Which template parameter type allows passing a sequence of arbitrary values such as a list of environment names?

Accepted Answer

object

Answer

The `object` parameter type accepts YAML sequences and mappings, making it suitable for passing lists or dictionaries to templates.

Question 4

A developer sets `variables: [{name: API_URL, value: https://dev.api.com}]` at the pipeline level and also sets the same variable at the job level to a production URL. Which value is used during job execution?

Accepted Answer

The job-level value because job scope overrides pipeline scope

Answer

Job-level variable definitions override pipeline-level definitions because narrower scopes take higher precedence in Azure Pipelines.

Question 5

Which Azure CLI command updates a pipeline variable to be secret after the pipeline has already been created?

Accepted Answer

az pipelines variable update --name VAR --secret true

Answer

The `az pipelines variable update --name VAR --secret true` command converts an existing pipeline variable to a secret type.

AZ-400 Practice Test

AZ-400 Practice Test

AZ-400 Pipeline Variables and Templates 3