The correct answer is that the container runs with no extra capabilities and cannot gain privileges. This is because setting `allowPrivilegeEscalation: false` prevents any process inside the container from acquiring more privileges than its parent process—blocking attacks like setuid binaries or kernel exploits—while `capabilities: { drop: ["ALL"] }` removes every Linux capability from the container’s bounding set, leaving it with zero extra privileges even if the container runs as root. On the Certified Kubernetes Application Developer CKAD exam, this combination tests your understanding of container security context fundamentals, often appearing in multi-select or scenario-based questions where a pod must be hardened against privilege escalation. A common trap is assuming that dropping all capabilities alone prevents escalation, but without `allowPrivilegeEscalation: false`, a process could still gain privileges through other mechanisms. Remember the mnemonic: “Drop all caps, lock the escalator—no privileges, no elevator.”
CKAD Practice Question: Application Environment, Configuration and Security
This CKAD practice question tests your understanding of application environment, configuration and security. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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's securityContext has 'allowPrivilegeEscalation: false' and 'capabilities: { drop: ["ALL"] }'. Which statement is true?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The container runs with no extra capabilities and cannot gain privileges.
Option B is correct because setting 'allowPrivilegeEscalation: false' prevents processes from gaining more privileges than their parent (e.g., via setuid binaries or kernel exploits), and dropping all capabilities with 'capabilities: { drop: ["ALL"] }' removes every Linux capability from the container's bounding set. Together, these ensure the container runs with no extra capabilities and cannot escalate privileges, even if running as root.
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 container can still gain capabilities via setuid binaries.
Why it's wrong here
allowPrivilegeEscalation: false prevents gaining privileges via setuid.
✓
The container runs with no extra capabilities and cannot gain privileges.
Why this is correct
Correct interpretation.
Related concept
Read the scenario before looking for a memorised answer.
✗
The container runs as root with full privileges.
Why it's wrong here
Dropping all capabilities removes privileges even if root.
✗
The container runs with all Linux capabilities.
Why it's wrong here
Dropping all capabilities removes them.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume dropping all capabilities still allows privilege escalation via setuid binaries, but 'allowPrivilegeEscalation: false' specifically blocks that path, making the combination a hard security boundary.
Detailed technical explanation
How to think about this question
Under the hood, Linux capabilities are implemented as bitmasks in the kernel's task struct; dropping all capabilities sets the effective, permitted, and inheritable sets to zero, while 'allowPrivilegeEscalation: false' sets the 'no_new_privs' flag on the process, which prevents gaining new privileges via execve() of setuid binaries or file capabilities. In a real-world scenario, this combination is critical for running untrusted workloads in multi-tenant clusters, as it ensures even a compromised container cannot escalate to host-level privileges.
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: The container runs with no extra capabilities and cannot gain privileges. — Option B is correct because setting 'allowPrivilegeEscalation: false' prevents processes from gaining more privileges than their parent (e.g., via setuid binaries or kernel exploits), and dropping all capabilities with 'capabilities: { drop: ["ALL"] }' removes every Linux capability from the container's bounding set. Together, these ensure the container runs with no extra capabilities and cannot escalate privileges, even if running as root.
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.