The answer is the `seccompProfile` field with `type: RuntimeDefault` under the Pod’s `securityContext`. This is correct because Kubernetes delegates seccomp profile enforcement to the container runtime, and setting `type: RuntimeDefault` instructs the runtime—such as containerd or CRI-O—to apply its own secure baseline, which blocks roughly 44 dangerous system calls while permitting essential ones like `read`, `write`, and `exit`. On the CKAD exam, this tests your understanding of Pod-level security contexts and the shift from the deprecated `seccomp.security.alpha.kubernetes.io/pod` annotation to the native `seccompProfile` field, which became GA in Kubernetes 1.22. A common trap is confusing this with the `securityContext` at the container level; remember that the Pod-level setting applies to all containers unless overridden. Memory tip: think “RuntimeDefault” as the runtime’s own safe list—it’s the default for a reason, not a custom profile.
CKAD Practice Question: Application Environment, Configuration and Security
This CKAD practice question tests your understanding of application environment, configuration and security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
A container image requires a seccomp profile that is not the default. The cluster supports the RuntimeDefault seccomp profile. Which Pod securityContext field should be configured to use the RuntimeDefault seccomp profile?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
seccompProfile:
type: RuntimeDefault
Option A is correct because the `seccompProfile` field under the Pod's `securityContext` is the proper way to specify a seccomp profile in Kubernetes. Setting `type: RuntimeDefault` tells the container runtime (e.g., containerd or CRI-O) to use the default seccomp profile provided by the runtime, which is a secure baseline that blocks around 44 system calls while allowing common ones like `read`, `write`, and `exit`. This field was introduced in Kubernetes 1.19 (GA in 1.22) and is the standard approach for configuring seccomp at the Pod or container level.
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.
✓
seccompProfile:
type: RuntimeDefault
Why this is correct
Correct. This sets the seccomp profile to the runtime default.
Related concept
Read the scenario before looking for a memorised answer.
✗
seccomp:
type: RuntimeDefault
Why it's wrong here
Incorrect. The correct field is 'seccompProfile', not 'seccomp'.
✗
capabilities:
add: [SECCOMP]
Why it's wrong here
Incorrect. There is no SECCOMP capability. Seccomp is configured via seccompProfile, not capabilities.
✗
securityContext:
seccomp:
type: Unconfined
Why it's wrong here
Incorrect. The field name is 'seccompProfile' and 'Unconfined' disables seccomp, which may not be desired.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the old alpha annotation `seccomp.security.alpha.kubernetes.io/pod` (deprecated in 1.19) with the current `seccompProfile` field, or they mistakenly think `capabilities` can set the seccomp profile, when in fact capabilities only grant permission to use seccomp syscalls, not apply a profile.
Detailed technical explanation
How to think about this question
Under the hood, when `type: RuntimeDefault` is set, the kubelet passes the seccomp profile path (e.g., `/proc/self/exe` for containerd's default) to the container runtime via the OCI runtime spec. The runtime then loads a precompiled BPF (Berkeley Packet Filter) program that intercepts system calls; if a blocked syscall is attempted, the process receives a `SIGKILL` or `SIGSYS` signal. In a real-world scenario, using `RuntimeDefault` is critical for security-sensitive workloads like web servers or databases, as it prevents dangerous syscalls like `clone` with certain flags or `mount` without compromising functionality.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKAD question in full detail.
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: seccompProfile:
type: RuntimeDefault — Option A is correct because the `seccompProfile` field under the Pod's `securityContext` is the proper way to specify a seccomp profile in Kubernetes. Setting `type: RuntimeDefault` tells the container runtime (e.g., containerd or CRI-O) to use the default seccomp profile provided by the runtime, which is a secure baseline that blocks around 44 system calls while allowing common ones like `read`, `write`, and `exit`. This field was introduced in Kubernetes 1.19 (GA in 1.22) and is the standard approach for configuring seccomp at the Pod or container level.
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 →
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.
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.