- A
Use a public registry to store the credentials.
Why wrong: Public registry exposes secrets.
- B
Hardcode the credentials in the docker-compose.yml under environment.
Why wrong: Hardcoding exposes secrets in the file.
- C
Use an .env file and add it to .gitignore, then reference it with env_file in the service.
.env file with env_file keeps secrets out of version control.
- D
Define the variables in the environment block of docker-compose.yml, with values from shell variables using ${VAR} syntax.
This allows passing secrets at runtime without hardcoding.
- E
Store the credentials in the Docker image during build.
Why wrong: Embedding in image is insecure and not easily changeable.
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 deploying a containerized application with Docker Compose. The application requires environment variables for database credentials that should not be hardcoded in the docker-compose.yml file. Which two methods securely provide these credentials? (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
Use an .env file and add it to .gitignore, then reference it with env_file in the service.
Option C is correct because using an `.env` file allows you to externalize sensitive environment variables (like database credentials) from the `docker-compose.yml` file. By adding the `.env` file to `.gitignore`, you prevent it from being committed to version control, thus keeping credentials secure. The `env_file` directive in the service definition loads these variables at runtime without exposing them in the compose file.
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.
- ✗
Use a public registry to store the credentials.
Why it's wrong here
Public registry exposes secrets.
- ✗
Hardcode the credentials in the docker-compose.yml under environment.
Why it's wrong here
Hardcoding exposes secrets in the file.
- ✓
Use an .env file and add it to .gitignore, then reference it with env_file in the service.
Why this is correct
.env file with env_file keeps secrets out of version control.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Define the variables in the environment block of docker-compose.yml, with values from shell variables using ${VAR} syntax.
Why this is correct
This allows passing secrets at runtime without hardcoding.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store the credentials in the Docker image during build.
Why it's wrong here
Embedding in image is insecure and not easily changeable.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between compile-time (build) and runtime injection of secrets, and the trap here is that candidates may think storing credentials in the Docker image (Option E) is acceptable, not realizing that image layers are persistent and can be inspected by anyone with access to the image.
Detailed technical explanation
How to think about this question
Docker Compose supports variable substitution using `${VAR}` syntax in the `environment` block, where the values are resolved from the shell environment at runtime. This method avoids storing secrets in the compose file but requires the variables to be set securely in the shell (e.g., via a CI/CD pipeline or a secrets manager). The `.env` file approach is convenient for local development but must be carefully excluded from version control; for production, tools like Docker Secrets or external vaults (e.g., HashiCorp Vault) are recommended for stronger security.
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 practitioner preparing for the 200-901 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
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: Use an .env file and add it to .gitignore, then reference it with env_file in the service. — Option C is correct because using an `.env` file allows you to externalize sensitive environment variables (like database credentials) from the `docker-compose.yml` file. By adding the `.env` file to `.gitignore`, you prevent it from being committed to version control, thus keeping credentials secure. The `env_file` directive in the service definition loads these variables at runtime without exposing them in the compose file.
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.
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.