- A
securityContext: seccompProfile: type: RuntimeDefault
Why wrong: Incorrect. `RuntimeDefault` applies the container runtime's default seccomp profile, not the custom profile.
- B
securityContext: seccompProfile: type: Localhost localhostProfile: "profiles/audit.json"
Why wrong: Incorrect. `localhostProfile: "profiles/audit.json"` would resolve to `/var/lib/kubelet/seccomp/profiles/audit.json`, which does not match the actual path `/var/lib/kubelet/seccomp/audit.json`.
- C
securityContext: seccomp: type: Localhost profile: "audit.json"
Why wrong: Incorrect. The `seccomp` field is deprecated and uses incorrect syntax; the current API is `seccompProfile`.
- D
securityContext: seccompProfile: type: Localhost localhostProfile: "audit.json"
Correct. It uses the current `seccompProfile` API with `type: Localhost` and `localhostProfile: "audit.json"`, which correctly points to the profile at `/var/lib/kubelet/seccomp/audit.json`.
Applying a Custom Seccomp Profile via YAML: localhostProfile Field
This CKS practice question tests your understanding of system hardening. 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 have built a custom seccomp profile at /var/lib/kubelet/seccomp/audit.json. Which YAML snippet correctly applies this profile to a container?
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
securityContext: seccompProfile: type: Localhost localhostProfile: "audit.json"
Option D is correct because the seccomp profile is stored at `/var/lib/kubelet/seccomp/audit.json`. The `localhostProfile` field expects a relative path from the base directory `/var/lib/kubelet/seccomp/`. Therefore, `audit.json` correctly resolves to the full path. The `seccompProfile` API with `type: Localhost` is the current method for applying custom profiles.
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.
- ✗
securityContext: seccompProfile: type: RuntimeDefault
Why it's wrong here
Incorrect. `RuntimeDefault` applies the container runtime's default seccomp profile, not the custom profile.
- ✗
securityContext: seccompProfile: type: Localhost localhostProfile: "profiles/audit.json"
Why it's wrong here
Incorrect. `localhostProfile: "profiles/audit.json"` would resolve to `/var/lib/kubelet/seccomp/profiles/audit.json`, which does not match the actual path `/var/lib/kubelet/seccomp/audit.json`.
- ✗
securityContext: seccomp: type: Localhost profile: "audit.json"
Why it's wrong here
Incorrect. The `seccomp` field is deprecated and uses incorrect syntax; the current API is `seccompProfile`.
- ✓
securityContext: seccompProfile: type: Localhost localhostProfile: "audit.json"
Why this is correct
Correct. It uses the current `seccompProfile` API with `type: Localhost` and `localhostProfile: "audit.json"`, which correctly points to the profile at `/var/lib/kubelet/seccomp/audit.json`.
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 confuse the deprecated `seccomp` field (used in older Kubernetes versions) with the current `seccompProfile` API, or they assume a bare filename like `audit.json` works without the required relative path prefix.
Detailed technical explanation
How to think about this question
When `type: Localhost` is used, the kubelet prepends the path `/var/lib/kubelet/seccomp` to the `localhostProfile` value, so `profiles/audit.json` becomes `/var/lib/kubelet/seccomp/profiles/audit.json`. The seccomp profile is loaded by the container runtime (e.g., containerd) and applied via the `prctl` syscall to restrict system calls for the container. In a real-world CKS scenario, you might audit a pod with a custom profile to detect malicious syscalls before enforcing it.
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 CKS 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.
Visual reference
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.
- →
System Hardening — study guide chapter
Learn the concepts, then practise the questions
- →
System Hardening practice questions
Targeted practice on this topic area only
- →
All CKS questions
997 questions across all exam domains
- →
Certified Kubernetes Security Specialist CKS study guide
Full concept coverage aligned to exam objectives
- →
CKS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Cluster Setup and Hardening practice questions
Practise CKS questions linked to Cluster Setup and Hardening.
System Hardening practice questions
Practise CKS questions linked to System Hardening.
Minimize Microservice Vulnerabilities practice questions
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Supply Chain Security practice questions
Practise CKS questions linked to Supply Chain Security.
Monitoring, Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Cluster Setup practice questions
Practise CKS questions linked to Cluster Setup.
Cluster Hardening practice questions
Practise CKS questions linked to Cluster Hardening.
CKS fundamentals practice questions
Practise CKS questions linked to CKS fundamentals.
CKS scenario practice questions
Practise CKS questions linked to CKS scenario.
CKS troubleshooting practice questions
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Start a free CKS 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 CKS question test?
System Hardening — This question tests System Hardening — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: securityContext: seccompProfile: type: Localhost localhostProfile: "audit.json" — Option D is correct because the seccomp profile is stored at `/var/lib/kubelet/seccomp/audit.json`. The `localhostProfile` field expects a relative path from the base directory `/var/lib/kubelet/seccomp/`. Therefore, `audit.json` correctly resolves to the full path. The `seccompProfile` API with `type: Localhost` is the current method for applying custom profiles.
What should I do if I get this CKS 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 →
Keep practising
More CKS practice questions
- Which flag is used to restrict the kubelet's ability to modify node status and pods?
- A Falco rule has priority `WARNING` and output: `Sensitive file opened (user=%user.name command=%proc.cmdline file=%fd.n…
- Falco detects a shell being opened inside a container. Which Falco rule field is used to specify the syscall condition f…
- A security audit reveals that a ServiceAccount named 'monitor' has a ClusterRoleBinding to the cluster-admin role. What…
- Match each Kubernetes security component to its description.
- Match each Kubernetes certificate type to its usage.
Last reviewed: Jul 4, 2026
This CKS 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 CKS 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.