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.
You apply a Pod Security Admission label 'pod-security.kubernetes.io/enforce: restricted' to a namespace. A pod with the following securityContext is created: securityContext: runAsUser: 1000 runAsNonRoot: true capabilities: drop: ["ALL"] seccompProfile: type: RuntimeDefault allowPrivilegeEscalation: false readOnlyRootFilesystem: true Will the pod be admitted?
Yes, the pod satisfies all restricted profile requirements
All required fields are set correctly.
No, because runAsUser must not be set
Why wrong: runAsUser is allowed as long as it is not 0.
No, because seccompProfile type must be 'Localhost'
Why wrong: RuntimeDefault is acceptable.
No, because the pod must not set capabilities at all
Why wrong: Dropping all capabilities is required.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Yes, the pod satisfies all restricted profile requirements
The Pod Security Admission (PSA) restricted profile requires that pods drop all capabilities, set `runAsNonRoot: true`, set `seccompProfile.type` to `RuntimeDefault` or `Localhost`, set `allowPrivilegeEscalation: false`, and restrict `runAsUser` to a non-root user (which is satisfied by `runAsUser: 1000`). The provided pod meets all these requirements, so it will be admitted. The `runAsUser` field is allowed as long as the user ID is not 0 (root), and the `seccompProfile.type` is correctly set to `RuntimeDefault`, which is one of the permitted values.
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.
Yes, the pod satisfies all restricted profile requirements
Why this is correct
All required fields are set correctly.
Related concept
Read the scenario before looking for a memorised answer.
No, because runAsUser must not be set
Why it's wrong here
runAsUser is allowed as long as it is not 0.
No, because seccompProfile type must be 'Localhost'
Why it's wrong here
RuntimeDefault is acceptable.
No, because the pod must not set capabilities at all
Why it's wrong here
Dropping all capabilities is required.
Common exam traps
The trap here is that candidates often think the restricted profile forbids setting `runAsUser` entirely or requires `seccompProfile.type` to be `Localhost`, but the actual requirement is that `runAsUser` must not be root and `seccompProfile.type` can be either `RuntimeDefault` or `Localhost`.
Detailed technical explanation
Pod Security Admission evaluates pods against predefined profiles (privileged, baseline, restricted) by checking the pod's security context against a set of required fields. The restricted profile, defined in the Kubernetes Pod Security Standards, mandates that `seccompProfile.type` must be `RuntimeDefault` or `Localhost` because it ensures the container uses the runtime's default seccomp filter, which blocks dangerous syscalls. The `runAsUser` field is allowed as long as the UID is not 0, and the `capabilities` field must explicitly drop all capabilities via `drop: ["ALL"]`; setting an empty `capabilities` block or omitting it would fail the check because the pod would inherit default capabilities.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
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: Yes, the pod satisfies all restricted profile requirements — The Pod Security Admission (PSA) restricted profile requires that pods drop all capabilities, set `runAsNonRoot: true`, set `seccompProfile.type` to `RuntimeDefault` or `Localhost`, set `allowPrivilegeEscalation: false`, and restrict `runAsUser` to a non-root user (which is satisfied by `runAsUser: 1000`). The provided pod meets all these requirements, so it will be admitted. The `runAsUser` field is allowed as long as the user ID is not 0 (root), and the `seccompProfile.type` is correctly set to `RuntimeDefault`, which is one of the permitted values.
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.