The answer is to use a secure secret store like HashiCorp Vault and retrieve secrets at runtime via API. This approach is correct because it decouples sensitive data—such as database credentials—from application code and container images, following the core principle of secret management for Docker containers. By authenticating to Vault’s REST API at runtime, microservices can fetch dynamic, encrypted secrets without ever embedding them in a Dockerfile or environment variable, which eliminates the risk of exposure in image layers or version control. On the Cisco DevNet Associate 200-901 exam, this tests your understanding of secure application deployment patterns within containerized environments on UCS, often appearing as a scenario where a team must avoid hardcoded credentials. A common trap is selecting “environment variables at container start,” which still leaves secrets visible in process listings or logs. Memory tip: think “Vault decouples, runtime retrieves”—the secret never sleeps in the image.
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 DevOps team is deploying a microservices application on Cisco UCS using Docker containers. They need to ensure that secrets such as database credentials are securely managed without hardcoding them in the application code or container images. Which approach should they use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a secure secret store like HashiCorp Vault and retrieve secrets at runtime via API.
Option C is correct because it follows the principle of secret management by decoupling sensitive data from application code and container images. HashiCorp Vault provides a centralized, encrypted secret store with dynamic secrets, access policies, and audit logging, allowing the microservices to authenticate and retrieve credentials at runtime via its REST API, eliminating the need to hardcode secrets.
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.
✗
Embed secrets directly in the container image using COPY instructions.
Why it's wrong here
Embedding secrets in the image makes them accessible to anyone with image access and violates principle of least privilege.
✗
Pass secrets as build arguments in the Docker build command.
Why it's wrong here
Build arguments are stored in image layers and can be retrieved using docker history.
✓
Use a secure secret store like HashiCorp Vault and retrieve secrets at runtime via API.
Why this is correct
A secret store provides dynamic, audited, and encrypted access to secrets without embedding them in code or images.
Related concept
Read the scenario before looking for a memorised answer.
✗
Store secrets as environment variables in the Docker Compose file.
Why it's wrong here
Environment variables in Docker Compose can be read during container inspection and may be leaked in logs.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that environment variables in Docker Compose or build arguments are secure enough for secrets, but the trap here is that these methods leave secrets exposed in plaintext within the image layers, logs, or runtime environment, whereas a dedicated secret store like Vault provides encryption, rotation, and access control.
Detailed technical explanation
How to think about this question
Under the hood, HashiCorp Vault uses a secure backend (e.g., Consul, integrated storage) to store secrets encrypted at rest with a master key, and it supports dynamic secrets (e.g., short-lived database credentials) that expire after use, reducing the risk of credential leakage. The microservice typically authenticates to Vault using a token, Kubernetes service account, or TLS certificate, then retrieves secrets via the Vault API (e.g., `GET /v1/secret/data/myapp`), often with a sidecar like Vault Agent to handle token renewal and secret injection. In a real-world scenario, this approach is critical for compliance with standards like PCI-DSS or SOC 2, where secrets must never appear in logs, images, or source code.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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 — 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 a secure secret store like HashiCorp Vault and retrieve secrets at runtime via API. — Option C is correct because it follows the principle of secret management by decoupling sensitive data from application code and container images. HashiCorp Vault provides a centralized, encrypted secret store with dynamic secrets, access policies, and audit logging, allowing the microservices to authenticate and retrieve credentials at runtime via its REST API, eliminating the need to hardcode secrets.
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 →
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. During a security audit, an engineer discovers that a CI/CD pipeline is storing API keys in plain text in environment variables. Which best practice should be implemented to mitigate this risk?
medium
A.Store secrets in a .env file and add it to the repository with restricted access.
B.Encrypt the environment variables using a tool like openssl and store the key elsewhere.
✓ C.Use a dedicated secrets management service like HashiCorp Vault or AWS Secrets Manager and retrieve secrets at runtime.
D.Remove the API keys from the pipeline and require manual entry each time a build runs.
Why C: Option C is correct because dedicated secrets management services like HashiCorp Vault or AWS Secrets Manager provide secure storage, access control, and audit logging for sensitive data. They allow the CI/CD pipeline to retrieve API keys at runtime via authenticated API calls, ensuring secrets are never stored in plain text in environment variables or configuration files. This approach aligns with the principle of least privilege and eliminates the risk of exposure through source code or build logs.
Last reviewed: Jun 11, 2026
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.
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.