This CKS practice question tests your understanding of cluster hardening. 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.
A developer created a ClusterRole 'pod-reader' with rules to get, list, and watch pods. They bound it to a user via ClusterRoleBinding. The user reports they cannot list pods in namespace 'test'. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
The ClusterRole must be bound with a RoleBinding
Why wrong: ClusterRoleBinding is correct for cluster-wide access.
The user needs a ServiceAccount
Why wrong: Users authenticate via certificates, not ServiceAccounts.
The ClusterRoleBinding might have a namespace set
If namespace is set, it becomes namespace-scoped, breaking access.
The pod-reader ClusterRole is missing 'list' verb
Why wrong: The stem says it includes list.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The ClusterRoleBinding might have a namespace set
Option C is correct because a ClusterRoleBinding is cluster-scoped and does not have a namespace field, but if a RoleBinding is used instead, it can restrict permissions to a specific namespace. The most likely cause is that the user inadvertently created a RoleBinding in the 'test' namespace (or the ClusterRoleBinding was misconfigured with a namespace selector), which would limit the binding's effect to that namespace. Since the user cannot list pods in 'test', the binding likely has a namespace constraint, preventing the cluster-wide permissions from applying.
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.
The ClusterRole must be bound with a RoleBinding
Why it's wrong here
ClusterRoleBinding is correct for cluster-wide access.
The user needs a ServiceAccount
Why it's wrong here
Users authenticate via certificates, not ServiceAccounts.
The ClusterRoleBinding might have a namespace set
Why this is correct
If namespace is set, it becomes namespace-scoped, breaking access.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
The pod-reader ClusterRole is missing 'list' verb
Why it's wrong here
The stem says it includes list.
Common exam traps
CNCF often tests the distinction between ClusterRoleBinding (cluster-wide) and RoleBinding (namespace-scoped), and the trap here is that candidates assume a ClusterRole always grants cluster-wide access, forgetting that the binding type (RoleBinding) can restrict it to a specific namespace.
Detailed technical explanation
In Kubernetes, ClusterRoleBindings are cluster-scoped and cannot have a namespace set, but RoleBindings are namespace-scoped and can restrict a ClusterRole's permissions to a specific namespace. If a user creates a RoleBinding in the 'test' namespace referencing the 'pod-reader' ClusterRole, the user will only have permissions in that namespace, but if the binding is missing or misconfigured, the user may lack access. A common real-world scenario is when an admin uses a RoleBinding instead of a ClusterRoleBinding, inadvertently scoping permissions to a single namespace, causing failures in other namespaces.
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 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.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Cluster Hardening — study guide chapter
Learn the concepts, then practise the questions
Cluster 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Practise CKS questions linked to Cluster Setup and Hardening.
Practise CKS questions linked to System Hardening.
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Practise CKS questions linked to Supply Chain Security.
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Practise CKS questions linked to Cluster Setup.
Practise CKS questions linked to Cluster Hardening.
Practise CKS questions linked to CKS fundamentals.
Practise CKS questions linked to CKS scenario.
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Cluster Hardening — This question tests Cluster Hardening — Read the scenario before looking for a memorised answer..
The correct answer is: The ClusterRoleBinding might have a namespace set — Option C is correct because a ClusterRoleBinding is cluster-scoped and does not have a namespace field, but if a RoleBinding is used instead, it can restrict permissions to a specific namespace. The most likely cause is that the user inadvertently created a RoleBinding in the 'test' namespace (or the ClusterRoleBinding was misconfigured with a namespace selector), which would limit the binding's effect to that namespace. Since the user cannot list pods in 'test', the binding likely has a namespace constraint, preventing the cluster-wide permissions from applying.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.