- A
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app
A Role in namespace 'app' grants permissions only in that namespace. The RoleBinding binds the Role to the ServiceAccount 'monitor' in the same namespace.
- B
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["read"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor
Why wrong: The verb 'read' is invalid; Kubernetes uses verbs like 'get', 'list', 'watch'. Also, the subjects list does not specify the namespace for the ServiceAccount, which may default to the binding's namespace but it's better to include it.
- C
apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: pod-reader rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: monitor-binding roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app
Why wrong: This uses ClusterRole and ClusterRoleBinding, which grants permissions across all namespaces. The requirement is only for the 'app' namespace, so a Role and RoleBinding scoped to that namespace are appropriate.
- D
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app
This is the same as Option B and is correct.
Quick Answer
The correct answer is the YAML snippet that defines a Role named 'pod-reader' in the 'app' namespace with `get` and `list` verbs on the `pods` resource, paired with a RoleBinding named 'monitor-binding' that binds that Role to the ServiceAccount 'monitor'. This is correct because RBAC in Kubernetes requires a Role to define permissions within a specific namespace, and a RoleBinding to link those permissions to a subject like a ServiceAccount; using `apiGroups: [""]` targets core API resources like pods, and the `get` and `list` verbs together grant the ability to both retrieve individual pod details and enumerate all pods. On the CKAD exam, this scenario tests your understanding of namespace-scoped RBAC, a frequent task where candidates often mistakenly use a ClusterRole or forget to include the `list` verb alongside `get`. A common trap is omitting the `namespace` field in either the Role or RoleBinding, which would cause the binding to fail. Memory tip: think "Role for the namespace, RoleBinding for the subject" — and always pair `get` with `list` when you need to see all resources.
CKAD Practice Question: Application Environment, Configuration and Security
This CKAD practice question tests your understanding of application environment, configuration and security. 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.
You need to create a Role and RoleBinding to allow a ServiceAccount 'monitor' in namespace 'app' to list pods in that namespace. Which YAML snippet correctly achieves this?
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-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app
Option A is correct because it defines a Role in the 'app' namespace with rules allowing 'get' and 'list' verbs on 'pods', and binds that Role to the 'monitor' ServiceAccount using a RoleBinding in the same namespace. This grants the ServiceAccount the exact permissions needed to list pods within the namespace, following the principle of least privilege.
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: Role metadata: name: pod-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app
Why this is correct
A Role in namespace 'app' grants permissions only in that namespace. The RoleBinding binds the Role to the ServiceAccount 'monitor' in the same namespace.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["read"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor
Why it's wrong here
The verb 'read' is invalid; Kubernetes uses verbs like 'get', 'list', 'watch'. Also, the subjects list does not specify the namespace for the ServiceAccount, which may default to the binding's namespace but it's better to include it.
- ✗
apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: pod-reader rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: monitor-binding roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app
Why it's wrong here
This uses ClusterRole and ClusterRoleBinding, which grants permissions across all namespaces. The requirement is only for the 'app' namespace, so a Role and RoleBinding scoped to that namespace are appropriate.
- ✓
apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: pod-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app
Why this is correct
This is the same as Option B and is correct.
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 may confuse 'read' with the valid verbs 'get' and 'list', or mistakenly use a ClusterRole/ClusterRoleBinding when a namespace-scoped Role/RoleBinding is required, leading to overly broad permissions.
Detailed technical explanation
How to think about this question
Kubernetes RBAC verbs are strictly defined (e.g., 'get', 'list', 'watch', 'create', 'update', 'patch', 'delete') and must match the API operations; using an invalid verb like 'read' results in a no-op rule. RoleBindings bind a Role to subjects within the same namespace, while ClusterRoleBindings grant permissions cluster-wide, making them inappropriate for namespace-scoped access control. The 'apiGroups' field with an empty string ('[""]') targets core API resources like pods, which belong to the 'v1' API group.
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.
- →
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
Related CKAD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Application Design and Build practice questions
Practise CKAD questions linked to Application Design and Build.
Application Deployment practice questions
Practise CKAD questions linked to Application Deployment.
Application Environment, Configuration and Security practice questions
Practise CKAD questions linked to Application Environment, Configuration and Security.
Application Observability and Maintenance practice questions
Practise CKAD questions linked to Application Observability and Maintenance.
Services and Networking practice questions
Practise CKAD questions linked to Services and Networking.
CKAD fundamentals practice questions
Practise CKAD questions linked to CKAD fundamentals.
CKAD scenario practice questions
Practise CKAD questions linked to CKAD scenario.
CKAD troubleshooting practice questions
Practise CKAD questions linked to CKAD troubleshooting.
Practice this exam
Start a free CKAD 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 CKAD question test?
Application Environment, Configuration and Security — This question tests Application Environment, Configuration and Security — 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-reader namespace: app rules: - apiGroups: [""] resources: ["pods"] verbs: ["get", "list"] --- apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: monitor-binding namespace: app roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: pod-reader subjects: - kind: ServiceAccount name: monitor namespace: app — Option A is correct because it defines a Role in the 'app' namespace with rules allowing 'get' and 'list' verbs on 'pods', and binds that Role to the 'monitor' ServiceAccount using a RoleBinding in the same namespace. This grants the ServiceAccount the exact permissions needed to list pods within the namespace, following the principle of least privilege.
What should I do if I get this CKAD 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 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.