- A
Use Pod Security Admission with the 'restricted' profile
The restricted profile enforces must-run-as-non-root.
- B
Set the container's entrypoint to 'sudo'
Why wrong: This would still run as root or require privilege escalation.
- C
Use OPA/Gatekeeper with a constraint that requires runAsNonRoot: true
Gatekeeper can enforce custom policies.
- D
Use a Seccomp profile that blocks root system calls
Why wrong: Seccomp restricts syscalls, not the user; a container can still run as root.
- E
Use Kyverno with a policy that validates runAsNonRoot
Kyverno can validate pod security contexts.
Question 433 of 997
Valid Approaches to Prevent Root Containers in Kubernetes
This CKS practice question tests your understanding of supply chain 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 of the following are valid approaches to prevent containers from running as root in a Kubernetes cluster?
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
✓
Use Pod Security Admission with the 'restricted' profile
Option A is correct because Pod Security Admission (PSA) is a built-in Kubernetes admission controller that enforces Pod Security Standards (PSS). The 'restricted' profile, as defined in the Kubernetes documentation, requires that containers run with `runAsNonRoot: true`, preventing root execution at the admission level without needing external tools.
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.
- ✓
Use Pod Security Admission with the 'restricted' profile
Why this is correct
The restricted profile enforces must-run-as-non-root.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Set the container's entrypoint to 'sudo'
Why it's wrong here
This would still run as root or require privilege escalation.
- ✓
Use OPA/Gatekeeper with a constraint that requires runAsNonRoot: true
Why this is correct
Gatekeeper can enforce custom policies.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use a Seccomp profile that blocks root system calls
Why it's wrong here
Seccomp restricts syscalls, not the user; a container can still run as root.
- ✓
Use Kyverno with a policy that validates runAsNonRoot
Why this is correct
Kyverno can validate pod security contexts.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The CKS exam often tests the distinction between preventing root execution (via `runAsNonRoot` or user ID constraints) and limiting kernel capabilities (via Seccomp or AppArmor), leading candidates to mistakenly choose Seccomp as a root-prevention mechanism.
Detailed technical explanation
How to think about this question
Pod Security Admission works by evaluating pods against the Pod Security Standards (Privileged, Baseline, Restricted) at admission time; the 'restricted' profile enforces `runAsNonRoot: true`, `runAsUser: MustRunAsNonRoot`, and prevents privileged escalation. OPA/Gatekeeper and Kyverno are external admission controllers that can validate `runAsNonRoot: true` via custom policies, but they require installation and configuration, whereas PSA is native to Kubernetes 1.23+. A real-world scenario is a multi-tenant cluster where a developer accidentally sets `securityContext.runAsUser: 0`; PSA with the 'restricted' profile would reject the pod, while OPA/Gatekeeper or Kyverno would catch it only if the policy is correctly defined and enforced.
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 CKS 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.
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.
- →
Supply Chain Security — study guide chapter
Learn the concepts, then practise the questions
- →
Supply Chain Security 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?
Supply Chain Security — This question tests Supply Chain Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Pod Security Admission with the 'restricted' profile — Option A is correct because Pod Security Admission (PSA) is a built-in Kubernetes admission controller that enforces Pod Security Standards (PSS). The 'restricted' profile, as defined in the Kubernetes documentation, requires that containers run with `runAsNonRoot: true`, preventing root execution at the admission level without needing external tools.
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.