This KCNA practice question tests your understanding of container orchestration. 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 pod uses a ServiceAccount that has a RoleBinding to a Role with 'get', 'list', 'watch' on 'pods'. The pod tries to list pods in the same namespace. Will the request succeed?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Yes, because the Role grants 'list' on pods
Option A is correct. In Kubernetes RBAC, permissions are additive. The Role grants get, list, watch on pods. Listing pods requires 'list' permission, which is granted. Option B is incorrect because there is no deny rule; RBAC is deny by default, but the RoleBinding grants the permission. Option C is incorrect because the ServiceAccount is bound to a Role, which is for a single namespace. Option D is incorrect; pod listing does not require a ClusterRole.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
No, because there is a deny rule for pods
Why it's wrong here
Kubernetes RBAC does not have explicit deny rules; deny by default is overridden by the Role.
✓
Yes, because the Role grants 'list' on pods
Why this is correct
The Role includes 'list' permission, and the binding applies to the same namespace.
Related concept
Standard ACLs match source addresses.
✗
No, because ServiceAccount cannot list pods
Why it's wrong here
ServiceAccount can list pods if granted the permission.
✗
Yes, but only if the ServiceAccount also has a ClusterRoleBinding
Why it's wrong here
A RoleBinding is sufficient for namespace-scoped resources like pods.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
Standard ACLs match source addresses.
Extended ACLs can match source, destination, protocol and ports.
The first matching ACL entry is used.
There is usually an implicit deny at the end.
TExam Day Tips
→Check inbound versus outbound direction.
→Read the ACL from top to bottom.
→Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Real-world example
How this comes up in practice
A security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this KCNA question in full detail.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related KCNA ACL questions on filtering logic and placement.
Container Orchestration — This question tests Container Orchestration — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: Yes, because the Role grants 'list' on pods — Option A is correct. In Kubernetes RBAC, permissions are additive. The Role grants get, list, watch on pods. Listing pods requires 'list' permission, which is granted. Option B is incorrect because there is no deny rule; RBAC is deny by default, but the RoleBinding grants the permission. Option C is incorrect because the ServiceAccount is bound to a Role, which is for a single namespace. Option D is incorrect; pod listing does not require a ClusterRole.
What should I do if I get this KCNA question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related KCNA ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
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 →
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.
This KCNA 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 KCNA 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.