- A
Set the label 'pod-security.kubernetes.io/enforce=restricted' on the namespace
This label enforces the restricted profile for all pods in the namespace.
- B
Add a 'securityContext' field to the Pod template with 'runAsUser: 1000'
Why wrong: While this may be part of compliance, it is not a step for enforcement; it's a specific configuration.
- C
Set the label 'pod-security.kubernetes.io/enforce=baseline' on the namespace
Why wrong: Baseline is less restrictive than restricted.
- D
Set the label 'pod-security.kubernetes.io/warn=restricted' on the namespace
Why wrong: The warn label only warns but does not enforce.
- E
Configure Pods to meet the restricted profile requirements, such as setting runAsNonRoot and seccompProfile
Pods must comply with the restricted profile; otherwise they will be rejected.
CKAD Practice Question: Application Environment, Configuration and Security
This CKAD practice question tests your understanding of application environment, configuration and security. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 want to apply a Pod Security Admission (PSA) policy that enforces the 'restricted' profile in the 'dev' namespace, but only for Pods that are not exempt. Which TWO steps are required? (Select TWO)
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
Set the label 'pod-security.kubernetes.io/enforce=restricted' on the namespace
Option A is correct because setting the label 'pod-security.kubernetes.io/enforce=restricted' on the namespace instructs the Pod Security Admission controller to reject any Pod that does not meet the restricted profile, unless the Pod is exempt (e.g., system-critical Pods or those with specific exemptions). This label directly enforces the policy at admission time, ensuring only compliant Pods are created in the 'dev' namespace.
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.
- ✓
Set the label 'pod-security.kubernetes.io/enforce=restricted' on the namespace
Why this is correct
This label enforces the restricted profile for all pods in the namespace.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Add a 'securityContext' field to the Pod template with 'runAsUser: 1000'
Why it's wrong here
While this may be part of compliance, it is not a step for enforcement; it's a specific configuration.
- ✗
Set the label 'pod-security.kubernetes.io/enforce=baseline' on the namespace
Why it's wrong here
Baseline is less restrictive than restricted.
- ✗
Set the label 'pod-security.kubernetes.io/warn=restricted' on the namespace
Why it's wrong here
The warn label only warns but does not enforce.
- ✓
Configure Pods to meet the restricted profile requirements, such as setting runAsNonRoot and seccompProfile
Why this is correct
Pods must comply with the restricted profile; otherwise they will be rejected.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing the 'warn' mode with 'enforce' mode, as candidates often think a warning label is sufficient to block non-compliant Pods, but only the 'enforce' label actually rejects them at admission time.
Detailed technical explanation
How to think about this question
Pod Security Admission (PSA) is a built-in admission controller in Kubernetes 1.23+ that replaces PodSecurityPolicy. It uses three levels (privileged, baseline, restricted) and three modes (enforce, audit, warn) applied via namespace labels. The 'restricted' profile requires Pods to set 'runAsNonRoot: true', 'seccompProfile.type: RuntimeDefault', and drop all capabilities, among other constraints. Exemptions include namespaces with 'kube-system' or those with 'pod-security.kubernetes.io/enforce-version' labels, and system-critical Pods like those from DaemonSets managed by the control plane.
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 CKAD 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.
- →
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
Related CKAD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Application Design and Build practice questions
Practise CKAD questions linked to Application Design and Build.
Application Deployment practice questions
Practise CKAD questions linked to Application Deployment.
Application Environment, Configuration and Security practice questions
Practise CKAD questions linked to Application Environment, Configuration and Security.
Application Observability and Maintenance practice questions
Practise CKAD questions linked to Application Observability and Maintenance.
Services and Networking practice questions
Practise CKAD questions linked to Services and Networking.
CKAD fundamentals practice questions
Practise CKAD questions linked to CKAD fundamentals.
CKAD scenario practice questions
Practise CKAD questions linked to CKAD scenario.
CKAD troubleshooting practice questions
Practise CKAD questions linked to CKAD troubleshooting.
Practice this exam
Start a free CKAD 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 CKAD question test?
Application Environment, Configuration and Security — This question tests Application Environment, Configuration and Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Set the label 'pod-security.kubernetes.io/enforce=restricted' on the namespace — Option A is correct because setting the label 'pod-security.kubernetes.io/enforce=restricted' on the namespace instructs the Pod Security Admission controller to reject any Pod that does not meet the restricted profile, unless the Pod is exempt (e.g., system-critical Pods or those with specific exemptions). This label directly enforces the policy at admission time, ensuring only compliant Pods are created in the 'dev' namespace.
What should I do if I get this CKAD 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 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.