This AZ-400 practice question tests your understanding of design and implement build and release pipelines. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
```yaml
- task: AzureKeyVault@2
inputs:
azureSubscription: 'MyServiceConnection'
KeyVaultName: 'mykv'
SecretsFilter: '*'
RunAsPreJob: false
```
You have the above YAML task in a pipeline. The task runs but no secrets are available in subsequent tasks. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Exhibit
Refer to the exhibit.
```yaml
- task: AzureKeyVault@2
inputs:
azureSubscription: 'MyServiceConnection'
KeyVaultName: 'mykv'
SecretsFilter: '*'
RunAsPreJob: false
```
A
The secrets are not automatically mapped to environment variables; you must reference them using $(secretName).
With RunAsPreJob: false, secrets are not injected as environment variables; they must be explicitly referenced.
B
The SecretsFilter is set to '*' which is invalid.
Why wrong: '*' is a valid filter to fetch all secrets.
C
The service principal does not have 'Get' permission on the key vault.
Why wrong: If permissions were missing, the task would fail.
D
The key vault name 'mykv' does not exist.
Why wrong: The task would fail if the vault didn't exist.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The secrets are not automatically mapped to environment variables; you must reference them using $(secretName).
By default, secrets downloaded from Azure Key Vault in a pipeline task are not automatically mapped to environment variables for subsequent tasks. You must explicitly reference them using the macro syntax `$(secretName)` or map them as environment variables with the `env` keyword. Without this explicit mapping, the secret values remain inaccessible to later tasks, even though the download task succeeds.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The secrets are not automatically mapped to environment variables; you must reference them using $(secretName).
Why this is correct
With RunAsPreJob: false, secrets are not injected as environment variables; they must be explicitly referenced.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The SecretsFilter is set to '*' which is invalid.
Why it's wrong here
'*' is a valid filter to fetch all secrets.
✗
The service principal does not have 'Get' permission on the key vault.
Why it's wrong here
If permissions were missing, the task would fail.
✗
The key vault name 'mykv' does not exist.
Why it's wrong here
The task would fail if the vault didn't exist.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume downloading secrets automatically makes them available as environment variables in all subsequent tasks, but Azure DevOps requires explicit mapping via `$(secretName)` or the `env` keyword to prevent accidental leakage.
Detailed technical explanation
How to think about this question
Under the hood, the Azure Key Vault task uses the Azure Resource Manager REST API to fetch secrets and stores them as pipeline variables with the `secret` type. However, these variables are only injected into the task that explicitly references them via `$(secretName)` or through the `env` mapping. In YAML pipelines, secrets are not automatically exported as environment variables to protect against accidental exposure in logs or downstream tasks. A common real-world scenario is when a subsequent script task tries to access a secret via `$SECRET_NAME` (Linux) or `%SECRET_NAME%` (Windows) without mapping, resulting in an empty value.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-400 question in full detail.
Design and implement build and release pipelines — This question tests Design and implement build and release pipelines — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The secrets are not automatically mapped to environment variables; you must reference them using $(secretName). — By default, secrets downloaded from Azure Key Vault in a pipeline task are not automatically mapped to environment variables for subsequent tasks. You must explicitly reference them using the macro syntax `$(secretName)` or map them as environment variables with the `env` keyword. Without this explicit mapping, the secret values remain inaccessible to later tasks, even though the download task succeeds.
What should I do if I get this AZ-400 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.