- A
apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: pod-lister rules: - apiGroups: [""] resources: ["pods"] verbs: ["list"]
Why wrong: ClusterRole is cluster-scoped; a Role should be used for namespace-scoped permissions.
- B
apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: pod-lister-binding namespace: dev subjects: - kind: User name: dev-user roleRef: kind: Role name: pod-lister apiGroup: rbac.authorization.k8s.io
Why wrong: This is a RoleBinding, not a Role.
- C
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-lister namespace: dev rules: - apiGroups: [""] resources: ["pods"] verbs: ["list"]
This defines a Role in the dev namespace with list pods permission.
- D
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-lister rules: - apiGroups: [""] resources: ["pods"] verbs: ["get"]
Why wrong: The verb 'list' is required, not 'get'.
Quick Answer
The correct answer is the YAML snippet that defines a Role with apiVersion: rbac.authorization.k8s.io/v1, kind: Role, metadata including namespace: dev, and rules specifying apiGroups: [""], resources: ["pods"], and verbs: ["list"]. This is correct because a Role in Kubernetes RBAC is namespace-scoped, meaning it only grants permissions within the namespace specified in its metadata, and the empty apiGroups string [""] targets the core API group where pods reside. On the CKA exam, this question tests your ability to distinguish between a Role and a ClusterRole—a common trap is using a ClusterRole when the requirement explicitly limits access to a single namespace. Remember that if the task says "in a specific namespace," you must use a Role, not a ClusterRole, and always include the namespace field. A helpful memory tip: "Role is for a single namespace, ClusterRole is for the whole cluster—when listing pods in dev, keep your Role confined."
CKA Practice Question: Cluster Architecture, Installation and Configuration
This CKA practice question tests your understanding of cluster architecture, installation and configuration. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 needs to create a Role that allows listing pods in the 'dev' namespace. Which YAML snippet correctly defines this Role?
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
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-lister namespace: dev rules: - apiGroups: [""] resources: ["pods"] verbs: ["list"]
Option C is correct because it defines a Role (not ClusterRole) scoped to the 'dev' namespace with the 'list' verb on 'pods', which matches the requirement exactly. In Kubernetes RBAC, a Role grants permissions within a specific namespace, and the empty apiGroups string [""] refers to the core API group where pods reside.
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.
- ✗
apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: pod-lister rules: - apiGroups: [""] resources: ["pods"] verbs: ["list"]
Why it's wrong here
ClusterRole is cluster-scoped; a Role should be used for namespace-scoped permissions.
- ✗
apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: pod-lister-binding namespace: dev subjects: - kind: User name: dev-user roleRef: kind: Role name: pod-lister apiGroup: rbac.authorization.k8s.io
Why it's wrong here
This is a RoleBinding, not a Role.
- ✓
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-lister namespace: dev rules: - apiGroups: [""] resources: ["pods"] verbs: ["list"]
Why this is correct
This defines a Role in the dev namespace with list pods permission.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-lister rules: - apiGroups: [""] resources: ["pods"] verbs: ["get"]
Why it's wrong here
The verb 'list' is required, not 'get'.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'get' with 'list' or choose a ClusterRole thinking it can be used for namespace-scoped access, but the CKA exam tests precise understanding that a Role must be namespace-scoped and use the correct verb for the intended operation.
Detailed technical explanation
How to think about this question
In Kubernetes RBAC, the 'list' verb allows retrieving a collection of resources (e.g., via 'kubectl get pods'), while 'get' only allows fetching a single resource by name. The Role resource must include the 'namespace' field in its metadata to be scoped to that namespace; omitting it would make the Role apply to the default namespace or cause an error depending on the context. This distinction is critical for least-privilege access control in multi-tenant clusters.
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 Architecture, Installation and Configuration — study guide chapter
Learn the concepts, then practise the questions
- →
Cluster Architecture, Installation and Configuration practice questions
Targeted practice on this topic area only
- →
All CKA questions
1,005 questions across all exam domains
- →
Certified Kubernetes Administrator CKA study guide
Full concept coverage aligned to exam objectives
- →
CKA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cluster Architecture, Installation and Configuration practice questions
Practise CKA questions linked to Cluster Architecture, Installation and Configuration.
Services and Networking practice questions
Practise CKA questions linked to Services and Networking.
Workloads and Scheduling practice questions
Practise CKA questions linked to Workloads and Scheduling.
Storage practice questions
Practise CKA questions linked to Storage.
Troubleshooting practice questions
Practise CKA questions linked to Troubleshooting.
Cluster Architecture, Installation & Configuration practice questions
Practise CKA questions linked to Cluster Architecture, Installation & Configuration.
Workloads & Scheduling practice questions
Practise CKA questions linked to Workloads & Scheduling.
Services & Networking practice questions
Practise CKA questions linked to Services & Networking.
CKA fundamentals practice questions
Practise CKA questions linked to CKA fundamentals.
CKA scenario practice questions
Practise CKA questions linked to CKA scenario.
CKA troubleshooting practice questions
Practise CKA questions linked to CKA troubleshooting.
Practice this exam
Start a free CKA 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 CKA question test?
Cluster Architecture, Installation and Configuration — This question tests Cluster Architecture, Installation and Configuration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-lister namespace: dev rules: - apiGroups: [""] resources: ["pods"] verbs: ["list"] — Option C is correct because it defines a Role (not ClusterRole) scoped to the 'dev' namespace with the 'list' verb on 'pods', which matches the requirement exactly. In Kubernetes RBAC, a Role grants permissions within a specific namespace, and the empty apiGroups string [""] refers to the core API group where pods reside.
What should I do if I get this CKA 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 →
Same concept, more angles
1 more ways this is tested on CKA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are applying the following RBAC manifest: --- apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: namespace: development name: pod-reader rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "watch", "list"] Which TWO statements are true about this Role? (Choose TWO.)
medium- A.It also grants access to secrets in the 'development' namespace
- ✓ B.It allows reading pod details in the 'development' namespace
- C.It grants permissions across all namespaces
- ✓ D.It grants permissions only within the 'development' namespace
- E.It allows creating pods in the 'development' namespace
Why B: Option B is correct because the Role explicitly defines rules for the 'pods' resource with verbs 'get', 'watch', and 'list' in the 'development' namespace. These verbs allow reading pod details such as their specifications, status, and metadata. The Role is scoped to the 'development' namespace, so it only grants these read permissions within that namespace.
Keep practising
More CKA practice questions
- Which TWO of the following are valid ways to ensure that a Pod runs on a node that has a GPU? (Choose TWO.)
- An administrator needs to upgrade the kube-apiserver on a control plane node from version 1.22.0 to 1.23.0. Which of the…
- A cluster is running on a cloud provider that supports load balancers. An administrator needs to expose a service extern…
- An administrator notices that traffic to a Service is not being forwarded to any pod. The Service has selector 'app: web…
- Which TWO of the following are valid commands to upgrade a kubeadm cluster from version 1.22.x to 1.23.x on the control…
- A user tries to create a pod with the YAML file that requests 2 CPUs as a limit. The cluster has a ResourceQuota named '…
Last reviewed: Jun 24, 2026
This CKA 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 CKA 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.