- A
Store the API key in a Jenkins 'Secret text' credential and use the withCredentials step in the pipeline.
withCredentials masks the secret in logs.
- B
Hardcode the API key in the Jenkinsfile and use the sh step to echo it.
Why wrong: Hardcoding and echoing exposes the key in logs.
- C
Pass the API key as a command-line argument to the build script.
Why wrong: Command-line arguments may be visible in process listings or logs.
- D
Print the API key to the console for debugging.
Why wrong: Printing exposes the secret.
- E
Set the API key as an environment variable using the environment directive, referencing a Jenkins credential.
Using credentials in environment directive masks the value.
Question 758 of 1,000
200-901 Application Deployment and Security Practice Question
This 200-901 practice question tests your understanding of application deployment and security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
A developer is writing a CI/CD pipeline using Jenkins Declarative Pipeline. They want to ensure that sensitive credentials (e.g., API keys) are never exposed in console logs. Which two security practices should be implemented? (Choose two.)
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"never"Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
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
✓
Store the API key in a Jenkins 'Secret text' credential and use the withCredentials step in the pipeline.
Option A is correct because Jenkins' `withCredentials` step securely binds a 'Secret text' credential to a variable, masking the value in console logs and preventing exposure. This is the standard practice for handling sensitive data in Declarative Pipeline, as it integrates with Jenkins' credential store and automatically redacts the secret from output.
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 the API key in a Jenkins 'Secret text' credential and use the withCredentials step in the pipeline.
Why this is correct
withCredentials masks the secret in logs.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Hardcode the API key in the Jenkinsfile and use the sh step to echo it.
Why it's wrong here
Hardcoding and echoing exposes the key in logs.
- ✗
Pass the API key as a command-line argument to the build script.
Why it's wrong here
Command-line arguments may be visible in process listings or logs.
- ✗
Print the API key to the console for debugging.
Why it's wrong here
Printing exposes the secret.
- ✓
Set the API key as an environment variable using the environment directive, referencing a Jenkins credential.
Why this is correct
Using credentials in environment directive masks the value.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between using the `environment` directive with `credentials()` (which is secure) versus setting environment variables manually (which is not), and the trap here is that candidates may think any environment variable is safe, but only those sourced from Jenkins credentials are masked.
Trap categories for this question
Command / output trap
Command-line arguments may be visible in process listings or logs.
Detailed technical explanation
How to think about this question
Under the hood, Jenkins' `withCredentials` step uses the Credentials Binding plugin to inject secrets as environment variables or files, with automatic masking via a custom log filter that replaces the secret value with asterisks. In a real-world scenario, if a developer uses `sh 'echo $API_KEY'` without `withCredentials`, the secret is printed in plaintext, but with `withCredentials`, the output is redacted even if the variable is echoed. The `environment` directive with `credentials()` also masks the value, but it sets the variable for the entire stage, which can be less granular than `withCredentials`.
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 network engineer segments a warehouse floor into three subnets: 20 scanners, 5 printers, and 2 management hosts. Picking the wrong mask wastes addresses or leaves too few usable hosts. Exam questions test whether you can apply CIDR notation, calculate block size, and identify the correct usable-host range for a given prefix.
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.
- →
Application Deployment and Security — study guide chapter
Learn the concepts, then practise the questions
- →
Application Deployment and Security practice questions
Targeted practice on this topic area only
- →
All 200-901 questions
1,000 questions across all exam domains
- →
Cisco DevNet Associate 200-901 study guide
Full concept coverage aligned to exam objectives
- →
200-901 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related 200-901 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Software Development and Design practice questions
Practise 200-901 questions linked to Software Development and Design.
Understanding and Using APIs practice questions
Practise 200-901 questions linked to Understanding and Using APIs.
Application Deployment and Security practice questions
Practise 200-901 questions linked to Application Deployment and Security.
Cisco Platforms and Development practice questions
Practise 200-901 questions linked to Cisco Platforms and Development.
Network Fundamentals practice questions
Practise 200-901 questions linked to Network Fundamentals.
Infrastructure and Automation practice questions
Practise 200-901 questions linked to Infrastructure and Automation.
200-901 fundamentals practice questions
Practise 200-901 questions linked to 200-901 fundamentals.
200-901 scenario practice questions
Practise 200-901 questions linked to 200-901 scenario.
200-901 troubleshooting practice questions
Practise 200-901 questions linked to 200-901 troubleshooting.
Practice this exam
Start a free 200-901 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 200-901 question test?
Application Deployment and Security — This question tests Application Deployment and Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Store the API key in a Jenkins 'Secret text' credential and use the withCredentials step in the pipeline. — Option A is correct because Jenkins' `withCredentials` step securely binds a 'Secret text' credential to a variable, masking the value in console logs and preventing exposure. This is the standard practice for handling sensitive data in Declarative Pipeline, as it integrates with Jenkins' credential store and automatically redacts the secret from output.
What should I do if I get this 200-901 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: "never". Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
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 →
Last reviewed: Jul 4, 2026
This 200-901 practice question is part of Courseiva's free Cisco 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 200-901 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.