- A
Store secrets in environment variables on the agent machine.
Why wrong: Environment variables on the agent can be read by other processes.
- B
Define secrets as pipeline secret variables and reference them as $(secretName).
Secret variables are encrypted and masked in logs.
- C
Store secrets in a YAML file and include the file in the repository.
Why wrong: Storing secrets in the repository is insecure.
- D
Use plain text variables in the pipeline and mask them using the 'Logging Command' feature.
Why wrong: Plain text variables are still exposed in the pipeline definition.
- E
Use Azure Key Vault to store secrets and reference them via variable groups linked to Key Vault.
Key Vault provides secure storage and access control.
How to Secure Secrets in Azure Pipelines with Key Vault and Secret Variables
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.
Which TWO actions should you take to protect sensitive information (e.g., API keys, passwords) in Azure Pipelines? (Choose two.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Define secrets as pipeline secret variables and reference them as $(secretName).
Option B is correct because Azure Pipelines allows you to define secret variables in the pipeline UI or YAML, which are encrypted at rest and never exposed in logs. Referencing them as $(secretName) ensures they are securely injected at runtime without being stored in plaintext. Option E is correct because Azure Key Vault provides a centralized, audited, and encrypted store for secrets, and variable groups linked to Key Vault allow pipelines to fetch secrets dynamically without embedding them in pipeline definitions.
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.
- ✗
Store secrets in environment variables on the agent machine.
Why it's wrong here
Environment variables on the agent can be read by other processes.
- ✓
Define secrets as pipeline secret variables and reference them as $(secretName).
Why this is correct
Secret variables are encrypted and masked in logs.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store secrets in a YAML file and include the file in the repository.
Why it's wrong here
Storing secrets in the repository is insecure.
- ✗
Use plain text variables in the pipeline and mask them using the 'Logging Command' feature.
Why it's wrong here
Plain text variables are still exposed in the pipeline definition.
- ✓
Use Azure Key Vault to store secrets and reference them via variable groups linked to Key Vault.
Why this is correct
Key Vault provides secure storage and access control.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think masking secrets in logs (Option D) is sufficient, but masking does not protect the secret from being stored in plaintext in the pipeline definition or from being exposed in other output channels.
Detailed technical explanation
How to think about this question
Azure Pipelines secret variables are encrypted using the Azure DevOps encryption key and are only decrypted at runtime for the specific pipeline run. When using Azure Key Vault, the pipeline uses a managed identity or service principal to authenticate and fetch secrets via the Key Vault REST API, ensuring secrets never appear in pipeline artifacts or logs. A subtle behavior: secret variables cannot be accessed in the YAML 'variables' block directly; they must be mapped via a variable group or explicitly passed as environment variables to tasks.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design and implement build and release pipelines — study guide chapter
Learn the concepts, then practise the questions
- →
Design and implement build and release pipelines practice questions
Targeted practice on this topic area only
- →
All AZ-400 questions
928 questions across all exam domains
- →
Microsoft Azure DevOps Engineer Expert AZ-400 study guide
Full concept coverage aligned to exam objectives
- →
AZ-400 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-400 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configure processes and communications practice questions
Practise AZ-400 questions linked to Configure processes and communications.
Design and implement source control practice questions
Practise AZ-400 questions linked to Design and implement source control.
Design and implement build and release pipelines practice questions
Practise AZ-400 questions linked to Design and implement build and release pipelines.
Develop a security and compliance plan practice questions
Practise AZ-400 questions linked to Develop a security and compliance plan.
Implement an instrumentation strategy practice questions
Practise AZ-400 questions linked to Implement an instrumentation strategy.
Design and implement a DevOps infrastructure practice questions
Practise AZ-400 questions linked to Design and implement a DevOps infrastructure.
Design and implement a source control strategy practice questions
Practise AZ-400 questions linked to Design and implement a source control strategy.
AZ-400 fundamentals practice questions
Practise AZ-400 questions linked to AZ-400 fundamentals.
AZ-400 scenario practice questions
Practise AZ-400 questions linked to AZ-400 scenario.
AZ-400 troubleshooting practice questions
Practise AZ-400 questions linked to AZ-400 troubleshooting.
Practice this exam
Start a free AZ-400 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-400 question test?
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: Define secrets as pipeline secret variables and reference them as $(secretName). — Option B is correct because Azure Pipelines allows you to define secret variables in the pipeline UI or YAML, which are encrypted at rest and never exposed in logs. Referencing them as $(secretName) ensures they are securely injected at runtime without being stored in plaintext. Option E is correct because Azure Key Vault provides a centralized, audited, and encrypted store for secrets, and variable groups linked to Key Vault allow pipelines to fetch secrets dynamically without embedding them in pipeline definitions.
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.
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 →
Same concept, more angles
1 more ways this is tested on AZ-400
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your build pipeline uses a hosted agent. You need to securely pass a connection string to a deployment task. The connection string contains a password. What is the recommended approach to store and use this secret in Azure Pipelines?
easy- A.Define the connection string as a plain variable in the YAML pipeline.
- B.Hardcode the connection string in the deployment script and set the file as read-only.
- ✓ C.Define the connection string as a secret variable in the pipeline's variable group or in the pipeline settings UI, and reference it as `$(connectionString)`.
- D.Store the connection string in Azure Key Vault and use the 'Azure Key Vault' task to retrieve it at runtime.
Why C: The recommended approach is to define the connection string as a secret variable in the pipeline's variable group or in the pipeline settings UI, and reference it as $(connectionString). Secret variables are encrypted at rest and never exposed in logs or to other tasks. Option A is incorrect because plain variables are visible in logs and YAML. Option B is incorrect because hardcoding secrets in scripts is insecure and violates best practices. Option D, while secure, is overkill for a simple secret and requires additional configuration and permissions, making it less recommended for this scenario.
Keep practising
More AZ-400 practice questions
- You are configuring a release pipeline that deploys to multiple environments. You want to automate the deployment to the…
- You have a multi-stage YAML pipeline that deploys to a Linux-based Azure App Service. The pipeline uses a 'Deploy to Azu…
- Your Azure DevOps pipeline deploys a web app to Azure App Service using a YAML pipeline. The deployment fails intermitte…
- A team is migrating from TFVC to Git. They have a large codebase with many branches. What is the recommended approach to…
- A development team is transitioning from a centralized version control system to Git in Azure Repos. The team lead wants…
- A team uses Azure Boards to manage work items. They want to automatically update the state of a work item when a related…
Last reviewed: Jul 4, 2026
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.