- A
Use 'pod-security.kubernetes.io/audit=restricted' to log violations without enforcement.
Why wrong: Audit mode does not enforce; it only logs.
- B
Enable the PodSecurity feature gate on the API server and kubelet.
PSA is enabled by default in v1.23+, but for older clusters you may need to enable it.
- C
Create a ServiceAccount for exempted pods and label it with 'pod-security.kubernetes.io/enforce=privileged'.
This overrides the namespace policy for pods using that ServiceAccount.
- D
Install a custom container runtime that supports privilege escalation.
Why wrong: PSA does not require a custom runtime.
- E
Set the namespace label 'pod-security.kubernetes.io/enforce=restricted' on the 'secure' namespace.
This enforces the restricted policy on the namespace.
Quick Answer
The answer is to set the namespace label 'pod-security.kubernetes.io/enforce=restricted' on the 'secure' namespace, then apply the exemption label 'pod-security.kubernetes.io/exempt' to the specific pods that require privileged containers, and finally ensure the PodSecurity feature gate is enabled on the API server. This is correct because Pod Security Admission (PSA) uses namespace-level labels to define enforcement modes, and the exemption label allows certain pods to bypass the enforced policy without altering the namespace-wide restriction. On the CKAD exam, this tests your understanding of how PSA integrates with Kubernetes RBAC and admission control, often appearing as a scenario where you must balance security with operational flexibility. A common trap is forgetting that the feature gate must be active for any labels to take effect, or confusing exemption labels with namespace-level audit or warn modes. Memory tip: think of the namespace as a locked door (enforce=restricted) and the exemption label as a special key for specific pods to enter.
CKAD Practice Question: Application Environment, Configuration and Security
This CKAD practice question tests your understanding of application environment, configuration and 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 administrator wants to implement Pod Security Admission (PSA) to enforce the 'restricted' policy for pods in the 'secure' namespace, but allow certain pods to use privileged containers by applying an exemption label. Which three steps are required? (Choose three.)
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
Enable the PodSecurity feature gate on the API server and kubelet.
Option B is correct because Pod Security Admission (PSA) is a built-in admission controller that requires the PodSecurity feature gate to be enabled on the API server (and, for enforcement, the kubelet must also support it) to activate the admission webhook. Without this feature gate, the PSA labels on namespaces are ignored, and the restricted policy cannot be enforced.
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.kubernetes.io/audit=restricted' to log violations without enforcement.
Why it's wrong here
Audit mode does not enforce; it only logs.
- ✓
Enable the PodSecurity feature gate on the API server and kubelet.
Why this is correct
PSA is enabled by default in v1.23+, but for older clusters you may need to enable it.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Create a ServiceAccount for exempted pods and label it with 'pod-security.kubernetes.io/enforce=privileged'.
Why this is correct
This overrides the namespace policy for pods using that ServiceAccount.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Install a custom container runtime that supports privilege escalation.
Why it's wrong here
PSA does not require a custom runtime.
- ✓
Set the namespace label 'pod-security.kubernetes.io/enforce=restricted' on the 'secure' namespace.
Why this is correct
This enforces the restricted policy on the namespace.
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 that candidates often confuse 'audit' mode (which only logs) with 'enforce' mode (which blocks violations), and may incorrectly think that a custom runtime is needed for privilege escalation, when PSA handles this via security context validation at the admission level.
Detailed technical explanation
How to think about this question
Pod Security Admission (PSA) is implemented as a validating admission webhook that evaluates pods against the 'restricted' policy defined in the Kubernetes Pod Security Standards (PSS). The 'restricted' policy disallows privileged containers, host namespaces, and many capabilities; exemptions are achieved by labeling a ServiceAccount with 'pod-security.kubernetes.io/enforce=privileged', which overrides the namespace-level enforcement for pods using that ServiceAccount. This mechanism works because the admission controller checks the ServiceAccount's label before the namespace label, allowing fine-grained exceptions.
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 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
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: Enable the PodSecurity feature gate on the API server and kubelet. — Option B is correct because Pod Security Admission (PSA) is a built-in admission controller that requires the PodSecurity feature gate to be enabled on the API server (and, for enforcement, the kubelet must also support it) to activate the admission webhook. Without this feature gate, the PSA labels on namespaces are ignored, and the restricted policy cannot be enforced.
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 →
Same concept, more angles
1 more ways this is tested on CKAD
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A cluster administrator wants to enforce that all pods in a namespace run with the 'restricted' Pod Security Standard. Which of the following is the correct way to label the namespace?
hard- ✓ A.pod-security.kubernetes.io/enforce: restricted
- B.pod-security.kubernetes.io/warn: restricted
- C.pod-security.kubernetes.io/audit: restricted
- ✓ D.pod-security.kubernetes.io/enforce: restricted
Why A: The 'restricted' Pod Security Standard is enforced by applying the label `pod-security.kubernetes.io/enforce: restricted` to the namespace. This label causes the Pod Security Admission controller to reject any pod that violates the restricted policy, ensuring compliance. The other labels (`warn` and `audit`) only generate warnings or audit annotations without blocking non-compliant pods.
Keep practising
More CKAD practice questions
- Match each Kubernetes concept to its definition.
- Arrange the steps to create a multi-container Pod with a shared volume.
- A pod has been scheduled on a node but is stuck in 'ContainerCreating' state. The team suspects a missing storage class.…
- A developer is creating a Deployment with 4 replicas. The application requires a rolling update with zero downtime. Whic…
- A developer creates a Deployment with 3 replicas that uses a ConfigMap mounted as a volume. After updating the ConfigMap…
- Which TWO statements about Kustomize are true?
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.