- A
kubectl patch deployment <deploy> -p '{"spec":{"template":{"spec":{"containers":[{"name":"app","volumeMounts":[{"name":"secret","mountPath":"/etc/secret"}]}],"volumes":[{"name":"secret","secret":{"secretName":"mysecret"}}]}}}}'
Correct. `kubectl patch` directly modifies the deployment template to add volume mounts and volumes, triggering a rolling update.
- B
kubectl set env deployment <deploy> --from=secret/mysecret
Why wrong: Incorrect. `kubectl set env` only injects environment variables from a secret; it does not mount volumes.
- C
kubectl edit deployment <deploy>
Why wrong: Incorrect. While `kubectl edit` can achieve the result, it requires manual editing and is not a single-purpose command like `patch`.
- D
kubectl set volume deployment/<deploy> --add --name=secret --mount-path=/etc/secret --secret-name=mysecret
Why wrong: Incorrect. `kubectl set volume` is not a valid kubectl command. The correct approach is to use `kubectl patch` or `kubectl edit`.
Updating a Deployment to Mount Secrets as Volumes Using kubectl patch
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. A key principle to apply: rolling Update. 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.
You have an existing deployment that uses environment variables for secrets. Which kubectl command can be used to update the deployment to mount secrets as volumes without recreating the pods?
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
kubectl patch deployment <deploy> -p '{"spec":{"template":{"spec":{"containers":[{"name":"app","volumeMounts":[{"name":"secret","mountPath":"/etc/secret"}]}],"volumes":[{"name":"secret","secret":{"secretName":"mysecret"}}]}}}}'
Option A is correct because `kubectl patch` directly updates the deployment's pod template spec to add a volume and volumeMount for the secret. This triggers a rolling update, applying the change without manually recreating pods. Option B only sets environment variables, not volume mounts. Option C (`kubectl edit`) requires manual editing and is less direct. Option D is invalid as `kubectl set volume` is not a real kubectl command.
Key principle: Rolling Update
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
kubectl patch deployment <deploy> -p '{"spec":{"template":{"spec":{"containers":[{"name":"app","volumeMounts":[{"name":"secret","mountPath":"/etc/secret"}]}],"volumes":[{"name":"secret","secret":{"secretName":"mysecret"}}]}}}}'
Why this is correct
Correct. `kubectl patch` directly modifies the deployment template to add volume mounts and volumes, triggering a rolling update.
Related concept
Rolling Update
- ✗
kubectl set env deployment <deploy> --from=secret/mysecret
Why it's wrong here
Incorrect. `kubectl set env` only injects environment variables from a secret; it does not mount volumes.
- ✗
kubectl edit deployment <deploy>
Why it's wrong here
Incorrect. While `kubectl edit` can achieve the result, it requires manual editing and is not a single-purpose command like `patch`.
- ✗
kubectl set volume deployment/<deploy> --add --name=secret --mount-path=/etc/secret --secret-name=mysecret
Why it's wrong here
Incorrect. `kubectl set volume` is not a valid kubectl command. The correct approach is to use `kubectl patch` or `kubectl edit`.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Candidates may incorrectly believe `kubectl set volume` is a valid command, but it does not exist. The correct commands are `kubectl patch` or `kubectl edit` to modify the deployment spec.
Trap categories for this question
Command / output trap
Incorrect. While `kubectl edit` can achieve the result, it requires manual editing and is not a single-purpose command like `patch`.
Detailed technical explanation
How to think about this question
Under the hood, `kubectl set volume` modifies the deployment's pod template spec by injecting a volume definition (e.g., `secret` type) and a corresponding `volumeMount` in the container spec. The deployment controller detects the template change and initiates a rolling update, creating new pods with the volume mounted and terminating old ones, ensuring zero downtime. In real-world scenarios, this is critical for rotating secrets without service disruption, as environment variables are static and require pod restart, while volume mounts allow live updates via projected secrets or subPath.
KKey Concepts to Remember
- Rolling Update
- kubectl patch
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
Rolling Update
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. Rolling Update 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.
Review rolling Update, then practise related CKS questions on the same topic to reinforce the concept.
- →
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 — Rolling Update.
What is the correct answer to this question?
The correct answer is: kubectl patch deployment <deploy> -p '{"spec":{"template":{"spec":{"containers":[{"name":"app","volumeMounts":[{"name":"secret","mountPath":"/etc/secret"}]}],"volumes":[{"name":"secret","secret":{"secretName":"mysecret"}}]}}}}' — Option A is correct because `kubectl patch` directly updates the deployment's pod template spec to add a volume and volumeMount for the secret. This triggers a rolling update, applying the change without manually recreating pods. Option B only sets environment variables, not volume mounts. Option C (`kubectl edit`) requires manual editing and is less direct. Option D is invalid as `kubectl set volume` is not a real kubectl command.
What should I do if I get this CKS question wrong?
Review rolling Update, then practise related CKS questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Rolling Update
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 →
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.