- A
securityContext: { privileged: false, capabilities: { drop: ["ALL"] } }
Why wrong: privileged: false alone does not prevent privilege escalation; the allowPrivilegeEscalation field is needed.
- B
securityContext: { allowPrivilegeEscalation: false, capabilities: { drop: ["ALL"] } }
Correctly sets both fields at the container security context level.
- C
securityContext: { allowPrivilegeEscalation: false, capabilities: { add: ["ALL"] } }
Why wrong: Adding ALL capabilities is the opposite of dropping them.
- D
spec: { allowPrivilegeEscalation: false, capabilities: { drop: ["ALL"] } }
Why wrong: These fields belong under securityContext, not directly under spec.
Question 951 of 997
Drop ALL Capabilities and Disable Privilege Escalation
This CKS practice question tests your understanding of minimize microservice vulnerabilities. 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.
An administrator wants to enforce a policy that all containers must drop ALL capabilities and not allow privilege escalation. Which YAML snippet correctly implements this requirement in a PodSecurityPolicy-like manner using a security context? (Note: PodSecurityPolicy is deprecated; consider using a ValidatingAdmissionPolicy or OPA/Gatekeeper, but for this question choose the correct security context fields.)
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
✓
securityContext: { allowPrivilegeEscalation: false, capabilities: { drop: ["ALL"] } }
Option B is correct because it sets `allowPrivilegeEscalation: false` to prevent privilege escalation (e.g., via setuid binaries) and `capabilities: { drop: ["ALL"] }` to remove all Linux capabilities from the container. This combination enforces the requirement that containers start with no extra privileges and cannot gain more, aligning with the principle of least privilege in PodSecurityPolicy-like enforcement.
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.
- ✗
securityContext: { privileged: false, capabilities: { drop: ["ALL"] } }
Why it's wrong here
privileged: false alone does not prevent privilege escalation; the allowPrivilegeEscalation field is needed.
- ✓
securityContext: { allowPrivilegeEscalation: false, capabilities: { drop: ["ALL"] } }
Why this is correct
Correctly sets both fields at the container security context level.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
securityContext: { allowPrivilegeEscalation: false, capabilities: { add: ["ALL"] } }
Why it's wrong here
Adding ALL capabilities is the opposite of dropping them.
- ✗
spec: { allowPrivilegeEscalation: false, capabilities: { drop: ["ALL"] } }
Why it's wrong here
These fields belong under securityContext, not directly under spec.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The exam often tests the distinction between `privileged: false` (which only disables privileged mode) and `allowPrivilegeEscalation: false` (which actively prevents privilege escalation), leading candidates to incorrectly choose option A.
Detailed technical explanation
How to think about this question
Under the hood, `allowPrivilegeEscalation` controls the `no_new_privs` Linux kernel flag; when set to false, it prevents processes from gaining privileges via `setuid` binaries or `capabilities`-based escalation. Dropping all capabilities with `drop: ["ALL"]` removes every capability from the container's bounding set, ensuring that even if a binary tries to use a capability, it fails. In a real-world scenario, this combination is critical for multi-tenant clusters where a compromised container must not be able to escalate to host-level access.
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.
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: securityContext: { allowPrivilegeEscalation: false, capabilities: { drop: ["ALL"] } } — Option B is correct because it sets `allowPrivilegeEscalation: false` to prevent privilege escalation (e.g., via setuid binaries) and `capabilities: { drop: ["ALL"] }` to remove all Linux capabilities from the container. This combination enforces the requirement that containers start with no extra privileges and cannot gain more, aligning with the principle of least privilege in PodSecurityPolicy-like enforcement.
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 →
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.