Quick Answer
The correct answer is `seccompProfile`, the dedicated field within a Pod or container `SecurityContext` that specifies the seccomp profile type, such as `RuntimeDefault`, `Localhost`, or `Unconfined`. This field, introduced in Kubernetes v1.19, directly controls which system calls a container can make, replacing the older annotation-based approach and providing a cleaner, more explicit configuration. On the CKAD exam, this tests your ability to secure workloads by restricting syscalls at the container level, often appearing in multi-part questions where you must edit a YAML manifest to enforce a specific profile. A common trap is confusing the `seccompProfile` field with the deprecated `seccomp.security.alpha.kubernetes.io/pod` annotation, but the exam now expects the native field. Memory tip: think "seccompProfile" as the direct path to lock down syscalls—just like a security guard checking a list of allowed actions at the container door.
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 pod must run with a seccomp profile that only allows specific syscalls. Which SecurityContext field is used to specify the seccomp profile type?
appArmorProfile
Why wrong: AppArmor is a separate LSM; seccomp is not configured via appArmorProfile.
seLinuxOptions
Why wrong: SELinux options are for SELinux, not seccomp.
seccomp
Why wrong: There is no seccomp field; the correct field is seccompProfile.
seccompProfile
The seccompProfile field in securityContext specifies the seccomp profile to use.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
seccompProfile
Option D is correct because `seccompProfile` is the field within the Pod or container `SecurityContext` that specifies the seccomp profile type (e.g., `RuntimeDefault`, `Localhost`, or `Unconfined`). This field was introduced in Kubernetes v1.19 (beta) and replaces the older annotation-based seccomp configuration, allowing you to define the profile type directly in the pod spec.
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.
appArmorProfile
Why it's wrong here
AppArmor is a separate LSM; seccomp is not configured via appArmorProfile.
seLinuxOptions
Why it's wrong here
SELinux options are for SELinux, not seccomp.
seccomp
Why it's wrong here
There is no seccomp field; the correct field is seccompProfile.
seccompProfile
Why this is correct
The seccompProfile field in securityContext specifies the seccomp profile to use.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates confuse the older annotation-based approach (`seccomp.security.alpha.kubernetes.io/pod`) with the newer native `seccompProfile` field, or they mistakenly think the field is simply named `seccomp` instead of `seccompProfile`.
Detailed technical explanation
The `seccompProfile.type` field accepts values like `RuntimeDefault` (uses the container runtime's default seccomp profile), `Localhost` (loads a profile from a file on the node), or `Unconfined` (disables seccomp). Under the hood, Kubernetes translates this field into a seccomp filter applied to the container's syscalls via the OCI runtime spec (e.g., runc). A real-world scenario is enforcing a strict profile that blocks `unshare` or `mount` syscalls to prevent container breakout attempts.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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: seccompProfile — Option D is correct because `seccompProfile` is the field within the Pod or container `SecurityContext` that specifies the seccomp profile type (e.g., `RuntimeDefault`, `Localhost`, or `Unconfined`). This field was introduced in Kubernetes v1.19 (beta) and replaces the older annotation-based seccomp configuration, allowing you to define the profile type directly in the pod spec.
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 →
Keep practising
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.