- A
The pod does not specify resource limits
Why wrong: While important, this is not the main security concern related to service accounts.
- B
The container runs as root
Why wrong: The YAML does not specify securityContext, but the concern is about service account token.
- C
The service account token is automatically mounted, potentially providing excessive permissions
Automounting the default service account token can be a security risk if the token has broad permissions.
- D
The pod uses the 'default' namespace
Why wrong: Using the default namespace is not a security concern per se.
CKS Cluster Setup and Hardening Practice Question
This CKS practice question tests your understanding of cluster setup and hardening. 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 developer creates a pod with the following YAML: apiVersion: v1 kind: Pod metadata: name: mypod spec: serviceAccountName: default automountServiceAccountToken: true containers: - name: app image: nginx
What is the security concern with this configuration?
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
The service account token is automatically mounted, potentially providing excessive permissions
Option C is correct because setting `automountServiceAccountToken: true` (or omitting it, as it defaults to true) causes the pod to automatically mount the service account token of the `default` service account into the container. This token can grant excessive permissions if the default service account has been bound to roles with broad access, such as cluster-admin or other privileged RBAC bindings, which is a common misconfiguration. An attacker who compromises the container can then use this token to authenticate to the Kubernetes API server and perform unauthorized actions within the cluster.
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.
- ✗
The pod does not specify resource limits
Why it's wrong here
While important, this is not the main security concern related to service accounts.
- ✗
The container runs as root
Why it's wrong here
The YAML does not specify securityContext, but the concern is about service account token.
- ✓
The service account token is automatically mounted, potentially providing excessive permissions
Why this is correct
Automounting the default service account token can be a security risk if the token has broad permissions.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The pod uses the 'default' namespace
Why it's wrong here
Using the default namespace is not a security concern per se.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the misconception that the `default` service account is always safe or that the namespace choice is the primary risk, when in fact the automatic mounting of the service account token—especially when combined with overly permissive RBAC bindings—is the direct security concern.
Detailed technical explanation
How to think about this question
The `automountServiceAccountToken` field controls whether the pod mounts the projected service account token (a JWT) into the container filesystem at `/var/run/secrets/kubernetes.io/serviceaccount/token`. This token is used by the kubelet to authenticate to the Kubernetes API server and is scoped to the service account's RBAC permissions. In real-world scenarios, the default service account is often left with minimal permissions, but if an administrator has inadvertently bound it to a ClusterRole with broad access (e.g., via a RoleBinding or ClusterRoleBinding), the mounted token becomes a critical attack vector. The CKS exam emphasizes disabling this automatic mount for workloads that do not need API access, using `automountServiceAccountToken: false` at the pod or service account level.
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.
- →
Cluster Setup and Hardening — study guide chapter
Learn the concepts, then practise the questions
- →
Cluster Setup and 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?
Cluster Setup and Hardening — This question tests Cluster Setup and Hardening — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The service account token is automatically mounted, potentially providing excessive permissions — Option C is correct because setting `automountServiceAccountToken: true` (or omitting it, as it defaults to true) causes the pod to automatically mount the service account token of the `default` service account into the container. This token can grant excessive permissions if the default service account has been bound to roles with broad access, such as cluster-admin or other privileged RBAC bindings, which is a common misconfiguration. An attacker who compromises the container can then use this token to authenticate to the Kubernetes API server and perform unauthorized actions within the cluster.
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 →
Last reviewed: Jun 30, 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.