The answer is Role and RoleBinding. This is correct because a Role grants permissions within a specific namespace, and a RoleBinding binds that Role to a user or service account within the same namespace, making them the precise RBAC resources for namespace-specific permissions. When you need to restrict a user to creating and managing deployments only in the 'development' namespace, a Role scoped to that namespace combined with a RoleBinding ensures the user cannot affect resources in other namespaces. On the CKA exam, this concept tests your understanding of Kubernetes RBAC scoping—a common trap is confusing Role with ClusterRole, which would grant permissions cluster-wide. Remember the memory tip: "Role is local, ClusterRole is global"—if the intent is namespace-specific permissions, always pair a Role with a RoleBinding.
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.
You need to allow a specific user to create and manage deployments in the 'development' namespace only. Which RBAC resources should you create?
Why wrong: These would grant permissions cluster-wide, not limited to the 'development' namespace.
B
Role and ClusterRoleBinding
Why wrong: A Role is namespace-scoped, but a ClusterRoleBinding would grant it cluster-wide, which is not desired.
C
Role and RoleBinding
A Role defines permissions within a namespace, and a RoleBinding grants those permissions to a user in that namespace.
D
ClusterRole and RoleBinding
Why wrong: A ClusterRole can be used with a RoleBinding to scope it to a namespace, but the question asks for the simplest solution; Role and RoleBinding are sufficient.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Role and RoleBinding
Option C is correct because a Role grants permissions within a specific namespace, and a RoleBinding binds that Role to a user or service account within the same namespace. To restrict a user to creating and managing deployments only in the 'development' namespace, you need a Role (scoped to that namespace) and a RoleBinding (also scoped to that namespace). ClusterRole and ClusterRoleBinding are cluster-scoped and would grant permissions across all namespaces, which is not desired here.
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.
✗
ClusterRole and ClusterRoleBinding
Why it's wrong here
These would grant permissions cluster-wide, not limited to the 'development' namespace.
✗
Role and ClusterRoleBinding
Why it's wrong here
A Role is namespace-scoped, but a ClusterRoleBinding would grant it cluster-wide, which is not desired.
✓
Role and RoleBinding
Why this is correct
A Role defines permissions within a namespace, and a RoleBinding grants those permissions to a user in that namespace.
Related concept
Read the scenario before looking for a memorised answer.
✗
ClusterRole and RoleBinding
Why it's wrong here
A ClusterRole can be used with a RoleBinding to scope it to a namespace, but the question asks for the simplest solution; Role and RoleBinding are sufficient.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the distinction between namespace-scoped and cluster-scoped resources, and the trap here is that candidates mistakenly think a ClusterRole is required for any 'management' task, or they confuse the scope of RoleBinding vs ClusterRoleBinding, leading them to pick options that grant permissions beyond the intended namespace.
Detailed technical explanation
How to think about this question
Under the hood, Kubernetes RBAC evaluates permissions by checking if the verb (e.g., create, get, list) on a resource (e.g., deployments) is allowed by any Role or ClusterRole bound to the user. A RoleBinding can only reference a Role in the same namespace or a ClusterRole (which then applies only to that namespace), but a ClusterRoleBinding binds a ClusterRole cluster-wide. The Kubernetes API server uses the SubjectAccessReview API to evaluate these bindings, and the scope is determined by the binding type, not the role type alone. In practice, using a ClusterRole with a RoleBinding is a common pattern for sharing common permissions across namespaces, but for a single namespace, a Role is more precise and avoids accidental over-permissioning.
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 practitioner preparing for the CKA 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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKA question in full detail.
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: Role and RoleBinding — Option C is correct because a Role grants permissions within a specific namespace, and a RoleBinding binds that Role to a user or service account within the same namespace. To restrict a user to creating and managing deployments only in the 'development' namespace, you need a Role (scoped to that namespace) and a RoleBinding (also scoped to that namespace). ClusterRole and ClusterRoleBinding are cluster-scoped and would grant permissions across all namespaces, which is not desired here.
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 →
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 have a ClusterRole named 'deployer' that allows creating Deployments and Services. You want to grant a ServiceAccount 'ci-cd' in namespace 'app' the permissions defined in this ClusterRole. Which TWO resources are needed? (Choose TWO.)
medium
✓ A.The existing ClusterRole 'deployer'
B.Create a new ClusterRole with the same rules
✓ C.RoleBinding in namespace 'app' referencing ClusterRole 'deployer' and ServiceAccount 'ci-cd'
D.ClusterRoleBinding with subject ServiceAccount 'ci-cd' in namespace 'app'
E.A Secret for the ServiceAccount
Why A: Option A is correct because the ClusterRole 'deployer' already contains the necessary rules to allow creating Deployments and Services. You do not need to create a new ClusterRole; you can reuse the existing one. Option C is correct because a RoleBinding in namespace 'app' can reference a ClusterRole and bind it to a ServiceAccount within that namespace, granting the permissions only in that namespace. This is the standard method to grant cluster-scoped permissions to a namespaced subject.
Last reviewed: Jun 30, 2026
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.
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.