Quick Answer
The answer is SYS_ADMIN, along with NET_RAW and SYS_MODULE, as the three capabilities commonly dropped to meet restricted pod security standards. This is because the restricted profile in Kubernetes enforces a strict drop-all-then-add-back approach, requiring you to explicitly drop highly privileged capabilities like SYS_ADMIN, which grants broad system-level access such as mounting filesystems or performing privileged syscalls, and NET_RAW, which allows raw socket creation and packet manipulation. On the CKAD exam, this concept tests your understanding of Pod Security Standards (PSS) and how to configure securityContext fields under the restricted policy—a common trap is assuming you only need to drop a few capabilities rather than starting from ALL. A useful memory tip is to think of the acronym SAN: SYS_ADMIN, SYS_MODULE, and NET_RAW are the three you must always drop for restricted compliance.
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.
Which THREE capabilities are commonly dropped in a pod's securityContext to adhere to restricted pod security standards?
ALL
Why wrong: ALL is not a capability; it's used to drop all capabilities.
SYS_ADMIN
SYS_ADMIN is a powerful capability often dropped.
SETUID
Dropping SETUID prevents setuid binaries.
NET_RAW
Dropping NET_RAW prevents raw socket creation.
CHOWN
Why wrong: CHOWN is typically allowed in restricted profiles.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
SYS_ADMIN
Option B (SYS_ADMIN) is correct because the restricted pod security standard (PSS) requires dropping all capabilities via `ALL` and then adding back only those needed. However, `SYS_ADMIN` is a highly privileged capability that grants broad system administration access, such as mounting filesystems and performing privileged syscalls, and is explicitly forbidden in restricted profiles. Dropping it is mandatory to comply with restricted PSS.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
ALL
Why it's wrong here
ALL is not a capability; it's used to drop all capabilities.
SYS_ADMIN
Why this is correct
SYS_ADMIN is a powerful capability often dropped.
Related concept
Read the scenario before looking for a memorised answer.
SETUID
Why this is correct
Dropping SETUID prevents setuid binaries.
Related concept
Read the scenario before looking for a memorised answer.
NET_RAW
Why this is correct
Dropping NET_RAW prevents raw socket creation.
Related concept
Read the scenario before looking for a memorised answer.
CHOWN
Why it's wrong here
CHOWN is typically allowed in restricted profiles.
Common exam traps
The trap here is that candidates confuse the wildcard `ALL` (used to drop all capabilities) with a specific capability, or they assume `CHOWN` is dangerous because it relates to ownership, when in fact it is permitted under restricted PSS.
Detailed technical explanation
Under the hood, Linux capabilities are implemented as bits in the task's `cap_effective` and `cap_permitted` masks. Dropping `SYS_ADMIN` removes the ability to call syscalls like `mount()`, `swapon()`, and `setdomainname()`, which are often exploited in container escape attacks. In practice, a pod running with `SYS_ADMIN` can bypass namespace isolation, making it a primary target for security hardening in restricted environments.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Application Environment, Configuration and Security — study guide chapter
Learn the concepts, then practise the questions
Application Environment, Configuration and Security practice questions
Targeted practice on this topic area only
All CKAD questions
991 questions across all exam domains
Certified Kubernetes Application Developer CKAD study guide
Full concept coverage aligned to exam objectives
CKAD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CKAD questions linked to Application Design and Build.
Practise CKAD questions linked to Application Deployment.
Practise CKAD questions linked to Application Environment, Configuration and Security.
Practise CKAD questions linked to Application Observability and Maintenance.
Practise CKAD questions linked to Services and Networking.
Practise CKAD questions linked to CKAD fundamentals.
Practise CKAD questions linked to CKAD scenario.
Practise CKAD questions linked to CKAD troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Application Environment, Configuration and Security — This question tests Application Environment, Configuration and Security — Read the scenario before looking for a memorised answer..
The correct answer is: SYS_ADMIN — Option B (SYS_ADMIN) is correct because the restricted pod security standard (PSS) requires dropping all capabilities via `ALL` and then adding back only those needed. However, `SYS_ADMIN` is a highly privileged capability that grants broad system administration access, such as mounting filesystems and performing privileged syscalls, and is explicitly forbidden in restricted profiles. Dropping it is mandatory to comply with restricted PSS.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 25, 2026
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.