AZ-400 Pipeline Variables and Templates 2

Question 1

Which syntax do you use to reference a variable group linked to an Azure Key Vault in a YAML pipeline?

Accepted Answer

$(variableName)

Answer

Variables from Key Vault-linked variable groups are accessed using the macro syntax $(variableName) at runtime.

Question 2

What is the purpose of the `extends` keyword in an Azure DevOps YAML pipeline?

Accepted Answer

To inherit from a base template and enforce organizational standards

Answer

The `extends` keyword allows a pipeline to inherit from a base template, enabling organizations to enforce mandatory steps and policies.

Question 3

A pipeline template parameter is defined as `type: boolean`. What happens if you pass the string 'true' instead of the boolean true?

Accepted Answer

Azure DevOps automatically coerces the string to boolean true

Answer

Azure DevOps YAML performs automatic type coercion for boolean template parameters, so the string 'true' is treated as boolean true.

Question 4

Which variable scope takes the lowest precedence when the same variable is defined at multiple levels in Azure Pipelines?

Accepted Answer

Pipeline root level

Answer

Variables defined at the pipeline root level have the lowest precedence and are overridden by stage, job, or step-level definitions.

Question 5

How do you pass a secret variable from a parent pipeline to a template file without exposing it as plaintext?

Accepted Answer

Use the env: block in a step to map the secret to an environment variable

Answer

Secrets should be passed to template steps via the `env:` mapping, which prevents the value from appearing in logs.

AZ-400 Practice Test