- A
Use an external secrets operator (e.g., AWS Secrets Manager, HashiCorp Vault) to inject secrets at runtime
External secrets operators fetch secrets from external stores and create Kubernetes Secrets without exposing them in the chart.
- B
Store secrets in a separate Git repository with restricted access
Why wrong: Even with restricted access, storing secrets in a Git repository is risky because Git history can expose them, and it does not provide encryption at rest.
- C
Use a tool like sealed-secrets to encrypt the secrets before committing them to the chart
Sealed-secrets allows you to encrypt secrets so they can be stored safely in a public repository. The sealed-secrets controller decrypts them inside the cluster.
- D
Store secrets as Kubernetes Secrets and reference them in the chart values
Why wrong: Kubernetes Secrets are only base64 encoded, not encrypted, and storing them in the chart values would expose them in plaintext in the repository.
- E
Use Helm's built-in encryption for values files
Why wrong: Helm does not have built-in encryption for values files. Third-party tools are needed.
KCNA Cloud Native Application Delivery Practice Question
This KCNA practice question tests your understanding of cloud native application delivery. 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.
A DevOps team uses Helm to manage Kubernetes applications. They want to ensure that sensitive data (e.g., database passwords) is not stored in plaintext in the Helm chart or in the cluster's ConfigMaps/Secrets. Which TWO practices should they adopt? (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 external secrets operator (e.g., AWS Secrets Manager, HashiCorp Vault) to inject secrets at runtime
Option A is correct because using an external secrets operator (e.g., AWS Secrets Manager, HashiCorp Vault) allows secrets to be injected directly into Pods at runtime without ever storing them in the Helm chart or as Kubernetes Secrets in plaintext. This approach leverages the Kubernetes CSI (Container Storage Interface) or a sidecar pattern to mount secrets from an external store, ensuring sensitive data never resides in the cluster's etcd or version control.
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 an external secrets operator (e.g., AWS Secrets Manager, HashiCorp Vault) to inject secrets at runtime
Why this is correct
External secrets operators fetch secrets from external stores and create Kubernetes Secrets without exposing them in the chart.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store secrets in a separate Git repository with restricted access
Why it's wrong here
Even with restricted access, storing secrets in a Git repository is risky because Git history can expose them, and it does not provide encryption at rest.
- ✓
Use a tool like sealed-secrets to encrypt the secrets before committing them to the chart
Why this is correct
Sealed-secrets allows you to encrypt secrets so they can be stored safely in a public repository. The sealed-secrets controller decrypts them inside the cluster.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store secrets as Kubernetes Secrets and reference them in the chart values
Why it's wrong here
Kubernetes Secrets are only base64 encoded, not encrypted, and storing them in the chart values would expose them in plaintext in the repository.
- ✗
Use Helm's built-in encryption for values files
Why it's wrong here
Helm does not have built-in encryption for values files. Third-party tools are needed.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the misconception that base64 encoding in Kubernetes Secrets is equivalent to encryption, leading candidates to incorrectly select Option D as secure, when in fact base64 is merely an encoding and provides no confidentiality.
Detailed technical explanation
How to think about this question
Under the hood, external secrets operators like the Secrets Store CSI Driver mount secrets as volumes or environment variables without writing them to etcd, using provider-specific APIs (e.g., AWS Secrets Manager's GetSecretValue API). Sealed-secrets works by encrypting a Secret resource into a SealedSecret custom resource using a public key stored in the cluster, which can only be decrypted by the sealed-secrets controller's private key, allowing safe storage in Git. A real-world scenario where this matters is a multi-tenant cluster where etcd access is not fully isolated, making plaintext Secrets a compliance risk.
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.
- →
Cloud Native Application Delivery — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Native Application Delivery practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA 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 KCNA question test?
Cloud Native Application Delivery — This question tests Cloud Native Application Delivery — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use an external secrets operator (e.g., AWS Secrets Manager, HashiCorp Vault) to inject secrets at runtime — Option A is correct because using an external secrets operator (e.g., AWS Secrets Manager, HashiCorp Vault) allows secrets to be injected directly into Pods at runtime without ever storing them in the Helm chart or as Kubernetes Secrets in plaintext. This approach leverages the Kubernetes CSI (Container Storage Interface) or a sidecar pattern to mount secrets from an external store, ensuring sensitive data never resides in the cluster's etcd or version control.
What should I do if I get this KCNA 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: Jun 30, 2026
This KCNA practice question is part of Courseiva's free CNCF 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 KCNA 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.