The answer is to set `securityContext.runAsUser: 0` at the container level. This setting overrides the pod-level user ID of 1000, forcing the specific container to run as root (UID 0), which satisfies the binary’s requirement for root privileges without altering the pod’s overall security context. On the Certified Kubernetes Application Developer CKAD exam, this tests your understanding of how SecurityContext fields can be applied at both the pod and container levels, and how container-level settings take precedence. A common trap is assuming you must change the pod-level `runAsUser` or add capabilities, but the correct approach is to target only the container that needs root access. Memory tip: think of it as “container override” — the container’s `runAsUser: 0` acts like a local override that lets a single process run as root while the rest of the pod stays non-root.
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 runs as user ID 1000. The container image includes a binary that expects to run as root. Which SecurityContext setting can allow the binary to run with root-like privileges while still running the container as non-root?
Add the SYS_ADMIN capability under securityContext.capabilities.add
Why wrong: Capabilities grant specific administrative privileges but do not change the user ID.
B
Set securityContext.privileged: true
Why wrong: This makes the container run as privileged, which includes running as root, but it is a broader and less secure approach; setting runAsUser:0 is more specific.
C
Set securityContext.runAsUser: 0
Setting runAsUser to 0 makes the container run as root, fulfilling the binary's requirement.
D
Set securityContext.allowPrivilegeEscalation: true
Why wrong: This allows processes to gain more privileges than their parent, but the container still runs as user 1000 unless runAsUser is changed.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set securityContext.runAsUser: 0
Option C is correct because setting `securityContext.runAsUser: 0` overrides the pod's user ID (1000) for this specific container, making it run as root (UID 0). This allows the binary that expects root privileges to execute without changing the pod-level security context or granting unnecessary capabilities.
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.
✗
Add the SYS_ADMIN capability under securityContext.capabilities.add
Why it's wrong here
Capabilities grant specific administrative privileges but do not change the user ID.
✗
Set securityContext.privileged: true
Why it's wrong here
This makes the container run as privileged, which includes running as root, but it is a broader and less secure approach; setting runAsUser:0 is more specific.
✓
Set securityContext.runAsUser: 0
Why this is correct
Setting runAsUser to 0 makes the container run as root, fulfilling the binary's requirement.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set securityContext.allowPrivilegeEscalation: true
Why it's wrong here
This allows processes to gain more privileges than their parent, but the container still runs as user 1000 unless runAsUser is changed.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse `runAsUser: 0` with a security risk, when in fact it is a precise way to run a specific container as root without elevating the entire pod or using privileged mode.
Detailed technical explanation
How to think about this question
Under the hood, `runAsUser: 0` sets the container's effective UID to 0, which is the root user in Linux. This is a container-level override that takes precedence over the pod-level `runAsUser` setting. In real-world scenarios, this is useful when a container image has a binary that requires root (e.g., to bind to privileged ports below 1024) but the overall pod security policy mandates non-root for other containers.
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 junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.
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: Set securityContext.runAsUser: 0 — Option C is correct because setting `securityContext.runAsUser: 0` overrides the pod's user ID (1000) for this specific container, making it run as root (UID 0). This allows the binary that expects root privileges to execute without changing the pod-level security context or granting unnecessary capabilities.
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.