- A
Use an AppArmor profile to block setuid syscalls.
Why wrong: AppArmor is not a built-in Kubernetes mechanism for pod security standards.
- B
Apply the 'restricted' Pod Security Standard at the namespace level.
Restricted enforces runAsNonRoot and disallows privileged escalation.
- C
Set 'securityContext.runAsUser: 1000' on each pod spec.
Why wrong: Setting a non-root user does not prevent setuid binaries.
- D
Apply the 'baseline' Pod Security Standard with 'seccompProfile: RuntimeDefault'.
Why wrong: Baseline does not require runAsNonRoot.
CKS Monitoring Logging and Runtime Security Practice Question
This CKS practice question tests your understanding of monitoring logging and runtime 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.
An organization uses Kubernetes with multiple namespaces and wants to ensure that containers running as non-root cannot escalate to root via setuid binaries. Which combination of security contexts and Pod Security Standards achieves this?
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
Apply the 'restricted' Pod Security Standard at the namespace level.
The 'restricted' Pod Security Standard (PSS) enforces the strongest set of security constraints, including preventing containers from running as root and disallowing privilege escalation. Specifically, it requires `securityContext.allowPrivilegeEscalation: false` and prohibits running as root, which directly blocks escalation via setuid binaries. Applying this standard at the namespace level ensures all pods in that namespace inherit these controls, meeting the requirement.
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 an AppArmor profile to block setuid syscalls.
Why it's wrong here
AppArmor is not a built-in Kubernetes mechanism for pod security standards.
- ✓
Apply the 'restricted' Pod Security Standard at the namespace level.
Why this is correct
Restricted enforces runAsNonRoot and disallows privileged escalation.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Set 'securityContext.runAsUser: 1000' on each pod spec.
Why it's wrong here
Setting a non-root user does not prevent setuid binaries.
- ✗
Apply the 'baseline' Pod Security Standard with 'seccompProfile: RuntimeDefault'.
Why it's wrong here
Baseline does not require runAsNonRoot.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the misconception that simply running as a non-root user (e.g., `runAsUser: 1000`) is sufficient to prevent privilege escalation, but without `allowPrivilegeEscalation: false`, setuid binaries can still be exploited to gain root.
Detailed technical explanation
How to think about this question
The 'restricted' PSS enforces `securityContext.allowPrivilegeEscalation: false` and `securityContext.capabilities.drop: ['ALL']`, which together prevent any process from gaining additional privileges, including via setuid binaries. Under the hood, this sets the `NO_NEW_PRIVS` flag on the container's process, which causes the kernel to ignore setuid bits and file capabilities. In a real-world scenario, a container running as non-root with `runAsUser: 1000` but without `allowPrivilegeEscalation: false` could still execute a setuid binary owned by root, escalating to root; the 'restricted' PSS closes this gap.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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.
- →
Monitoring Logging and Runtime Security — study guide chapter
Learn the concepts, then practise the questions
- →
Monitoring Logging and Runtime 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?
Monitoring Logging and Runtime Security — This question tests Monitoring Logging and Runtime Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Apply the 'restricted' Pod Security Standard at the namespace level. — The 'restricted' Pod Security Standard (PSS) enforces the strongest set of security constraints, including preventing containers from running as root and disallowing privilege escalation. Specifically, it requires `securityContext.allowPrivilegeEscalation: false` and prohibits running as root, which directly blocks escalation via setuid binaries. Applying this standard at the namespace level ensures all pods in that namespace inherit these controls, meeting the requirement.
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 →
Last reviewed: Jun 30, 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.