- A
Use an external secret manager like HashiCorp Vault and inject secrets via sidecar or CSI driver.
External secret managers provide secure storage and dynamic secrets.
- B
Store secrets in environment variables directly in the Deployment YAML.
Why wrong: Hardcoding secrets in YAML is insecure; they should be stored in Secret objects.
- C
Use Kubernetes Secret objects mounted as volumes in pods.
Mounting secrets as volumes is a recommended practice.
- D
Encrypt Secret objects at rest using EncryptionConfiguration.
Encrypting secrets at rest is a security best practice.
- E
Store secrets in ConfigMaps and reference them in pods.
Why wrong: ConfigMaps are not designed for sensitive data; they are for non-sensitive configuration.
Question 684 of 997
How Should You Securely Manage Secrets in Kubernetes?
This CKS practice question tests your understanding of minimize microservice vulnerabilities. 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.
Which THREE of the following are valid ways to manage secrets in a Kubernetes environment? (Select THREE)
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 secret manager like HashiCorp Vault and inject secrets via sidecar or CSI driver.
Option A is correct because external secret managers like HashiCorp Vault can inject secrets into pods via a sidecar container (e.g., Vault Agent) or a CSI driver (e.g., Secrets Store CSI Driver). This approach avoids storing raw secrets in the cluster, reduces the attack surface, and enables dynamic secret rotation without pod restarts.
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 secret manager like HashiCorp Vault and inject secrets via sidecar or CSI driver.
Why this is correct
External secret managers provide secure storage and dynamic secrets.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store secrets in environment variables directly in the Deployment YAML.
Why it's wrong here
Hardcoding secrets in YAML is insecure; they should be stored in Secret objects.
- ✓
Use Kubernetes Secret objects mounted as volumes in pods.
Why this is correct
Mounting secrets as volumes is a recommended practice.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Encrypt Secret objects at rest using EncryptionConfiguration.
Why this is correct
Encrypting secrets at rest is a security best practice.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store secrets in ConfigMaps and reference them in pods.
Why it's wrong here
ConfigMaps are not designed for sensitive data; they are for non-sensitive configuration.
Common exam traps
Common exam trap: answer the scenario, not the keyword
A common misconception is that Kubernetes Secrets are inherently secure because they are base64-encoded, but the trap is that base64 is not encryption, and Secrets are stored in plaintext in etcd unless explicitly encrypted with EncryptionConfiguration.
Detailed technical explanation
How to think about this question
The Secrets Store CSI Driver mounts secrets from external providers (e.g., Vault, AWS Secrets Manager) as volumes, using a gRPC interface to the provider's plugin. This allows secrets to be rotated by updating the external store, and the driver can sync the mount without pod restart if configured with `rotationPollInterval`. In contrast, Kubernetes Secrets are base64-encoded, not encrypted, unless EncryptionConfiguration is applied at the etcd level.
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 CKS 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.
- →
Minimize Microservice Vulnerabilities — study guide chapter
Learn the concepts, then practise the questions
- →
Minimize Microservice Vulnerabilities practice questions
Targeted practice on this topic area only
- →
All CKS questions
997 questions across all exam domains
- →
Certified Kubernetes Security Specialist CKS study guide
Full concept coverage aligned to exam objectives
- →
CKS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Cluster Setup and Hardening practice questions
Practise CKS questions linked to Cluster Setup and Hardening.
System Hardening practice questions
Practise CKS questions linked to System Hardening.
Minimize Microservice Vulnerabilities practice questions
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Supply Chain Security practice questions
Practise CKS questions linked to Supply Chain Security.
Monitoring, Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Cluster Setup practice questions
Practise CKS questions linked to Cluster Setup.
Cluster Hardening practice questions
Practise CKS questions linked to Cluster Hardening.
CKS fundamentals practice questions
Practise CKS questions linked to CKS fundamentals.
CKS scenario practice questions
Practise CKS questions linked to CKS scenario.
CKS troubleshooting practice questions
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Start a free CKS 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 CKS question test?
Minimize Microservice Vulnerabilities — This question tests Minimize Microservice Vulnerabilities — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use an external secret manager like HashiCorp Vault and inject secrets via sidecar or CSI driver. — Option A is correct because external secret managers like HashiCorp Vault can inject secrets into pods via a sidecar container (e.g., Vault Agent) or a CSI driver (e.g., Secrets Store CSI Driver). This approach avoids storing raw secrets in the cluster, reduces the attack surface, and enables dynamic secret rotation without pod restarts.
What should I do if I get this CKS 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
4 more ways this is tested on CKS
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. Which TWO of the following are valid methods to securely manage secrets in Kubernetes?
easy- ✓ A.Use Kubernetes Secrets with encryption at rest enabled
- B.Store secrets in ConfigMaps and use them in pods
- C.Commit secrets to a private Git repository
- D.Store secrets directly in the application code
- ✓ E.Use an external secret manager like HashiCorp Vault with a sidecar or CSI driver
Why A: Option A is correct because Kubernetes Secrets can be encrypted at rest using a KMS provider (e.g., AWS KMS, Azure Key Vault, or GCP Cloud KMS) configured via the EncryptionConfiguration resource. This ensures that Secret data is encrypted in etcd, protecting it from unauthorized access if the etcd database is compromised. Encryption at rest is a critical security control for secrets in Kubernetes.
Variation 2. Which TWO of the following are valid methods to securely manage secrets in Kubernetes? (Select 2)
medium- ✓ A.Use an external secrets manager like HashiCorp Vault with a CSI driver or operator
- B.Store secrets directly in container images as files
- ✓ C.Mount secrets as volumes using projected volumes or secret volumes
- D.Store secrets in ConfigMaps
- E.Pass secrets as environment variables from a Secret resource
Why A: Option A is correct because using an external secrets manager like HashiCorp Vault with a CSI driver or operator allows secrets to be stored and managed outside the cluster, reducing the attack surface. The CSI driver mounts secrets as volumes directly into pods without storing them in etcd, and the operator can synchronize secrets from Vault to Kubernetes Secret objects securely. This approach follows the principle of least privilege and enables dynamic secret rotation without pod restarts.
Variation 3. Which TWO of the following are valid ways to securely manage secrets in Kubernetes? (Choose two.)
medium- ✓ A.Mount Kubernetes Secrets as volumes into the pod.
- B.Use environment variables from the pod spec referencing Secret keys.
- ✓ C.Use an external secrets manager like HashiCorp Vault integrated with the pod.
- D.Pass secrets as command-line arguments to the container.
- E.Store secrets in ConfigMaps with base64 encoded data.
Why A: Option A is correct because mounting Kubernetes Secrets as volumes into the pod ensures that secret data is stored in the pod's filesystem as files, which are created with in-memory tmpfs to avoid writing to disk. This approach leverages Kubernetes' native secret handling, where the secret data is base64-decoded and presented as plaintext files, and access can be controlled via RBAC and PodSecurityPolicies. It also supports automatic rotation when secrets are updated, provided the pod is restarted or the volume is remounted.
Variation 4. Which TWO of the following are secure practices for managing secrets in Kubernetes? (Select TWO.)
medium- A.Store secrets as environment variables
- ✓ B.Use a CSI driver to mount secrets as volumes
- C.Embed secrets in container images
- ✓ D.Use an external secrets manager like Vault with a sidecar
- E.Store secrets in a ConfigMap
Why B: Option B is correct because the CSI (Container Storage Interface) driver for secrets allows secrets to be mounted as volumes without storing them in etcd or exposing them in environment variables. This approach leverages the CSI driver's ability to fetch secrets from external providers (e.g., HashiCorp Vault) on-demand, ensuring secrets are never persisted in Kubernetes objects and reducing the attack surface. It also supports rotation without pod restarts, as the volume content can be updated dynamically.
Keep practising
More CKS practice questions
- Which flag is used to restrict the kubelet's ability to modify node status and pods?
- A Falco rule has priority `WARNING` and output: `Sensitive file opened (user=%user.name command=%proc.cmdline file=%fd.n…
- Falco detects a shell being opened inside a container. Which Falco rule field is used to specify the syscall condition f…
- A security audit reveals that a ServiceAccount named 'monitor' has a ClusterRoleBinding to the cluster-admin role. What…
- Match each Kubernetes security component to its description.
- Match each Kubernetes certificate type to its usage.
Last reviewed: Jul 4, 2026
This CKS 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 CKS 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.