The answer is that the pod runs successfully as user 1000 with group 2000. This happens because the pod-level securityContext fields, including runAsUser and runAsNonRoot, always override the USER directive set in the Dockerfile. When runAsNonRoot is set to true, Kubernetes verifies that the effective user is not root; since runAsUser: 1000 explicitly sets a non-root user, the check passes and the container starts normally. On the CKAD exam, this scenario tests your understanding of the precedence between image-level and pod-level user settings—a common trap is assuming runAsNonRoot alone will fail if the Dockerfile says USER root, but the explicit runAsUser override resolves the conflict. Remember the hierarchy: pod securityContext > container securityContext > Dockerfile USER. A useful mnemonic is "Pod trumps image"—the pod’s runtime security settings always win over the image’s build-time defaults.
CKAD Practice Question: Application Environment, Configuration and Security
This CKAD practice question tests your understanding of application environment, configuration 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 pod is running with 'securityContext: { runAsUser: 1000, fsGroup: 2000, runAsNonRoot: true }'. The container image has USER root set in Dockerfile. What happens when the pod is created?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The pod runs successfully as user 1000 with group 2000
Option B is correct because the pod's securityContext settings override the USER directive in the container image. The runAsUser: 1000 sets the container process to run as user 1000, and fsGroup: 2000 sets the group ownership of any mounted volumes to group 2000. The runAsNonRoot: true ensures the container does not run as root, but since the securityContext explicitly sets a non-root user, the check passes and the pod runs successfully.
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.
✗
The pod runs as user 1000 but group remains root
Why it's wrong here
fsGroup: 2000 sets the group to 2000.
✓
The pod runs successfully as user 1000 with group 2000
Why this is correct
The securityContext sets runAsUser: 1000, which overrides the image's USER, and fsGroup sets the group. runAsNonRoot is satisfied.
Related concept
Read the scenario before looking for a memorised answer.
✗
The pod runs as root because the image's USER directive takes precedence
Why it's wrong here
The pod-level securityContext overrides the image's USER.
✗
The pod fails with 'container has runAsNonRoot and image will run as root'
Why it's wrong here
Although the image has USER root, the securityContext overrides it to runAsUser 1000, so the container runs as non-root.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume the image's USER directive is immutable or that runAsNonRoot checks the image's USER before securityContext is applied, when in fact Kubernetes applies the securityContext first and then validates runAsNonRoot against the resulting effective user.
Detailed technical explanation
How to think about this question
Under the hood, Kubernetes uses the securityContext to set the container's user and group via the Linux syscalls setuid and setgid, which override the image's USER directive at container start. The fsGroup is applied to any volume mounts using chown to ensure the group matches, which is critical for shared storage like NFS or PersistentVolumeClaims. A real-world scenario is when a hardened container image defaults to root but the cluster policy requires non-root execution; the securityContext ensures compliance without rebuilding the image.
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 CKAD 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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKAD question in full detail.
Application Environment, Configuration and Security — This question tests Application Environment, Configuration and Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The pod runs successfully as user 1000 with group 2000 — Option B is correct because the pod's securityContext settings override the USER directive in the container image. The runAsUser: 1000 sets the container process to run as user 1000, and fsGroup: 2000 sets the group ownership of any mounted volumes to group 2000. The runAsNonRoot: true ensures the container does not run as root, but since the securityContext explicitly sets a non-root user, the check passes and the pod runs successfully.
What should I do if I get this CKAD 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 →
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 CKAD 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 CKAD 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.