CKA Practice Question: Cluster Architecture, Installation and Configuration
This CKA practice question tests your understanding of cluster architecture, installation and configuration. 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.
An administrator is setting up RBAC to allow a CI/CD pipeline to create and delete pods only in the 'ci' namespace. Which combination of resources should be created?
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
A Role and RoleBinding are the correct combination because the CI/CD pipeline needs to create and delete pods only within the 'ci' namespace. A Role defines permissions scoped to a specific namespace, and a RoleBinding grants those permissions to a user or service account within that same namespace. This ensures the pipeline cannot affect resources in other namespaces.
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.
✓
Role and RoleBinding
Why this is correct
Role is namespace-scoped, and RoleBinding binds it to the user within that namespace.
Related concept
Read the scenario before looking for a memorised answer.
✗
ClusterRole and RoleBinding
Why it's wrong here
Although possible, using a ClusterRole for namespace-scoped access is not minimal; a Role is more appropriate.
✗
ClusterRole and ClusterRoleBinding
Why it's wrong here
ClusterRole/ClusterRoleBinding are cluster-scoped; they would grant access across all namespaces.
✗
Role and ClusterRoleBinding
Why it's wrong here
A RoleBinding is needed to bind a Role to a user; ClusterRoleBinding binds cluster-scoped roles.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume a ClusterRole is always needed for any pipeline or service account, but for namespace-scoped resources, a Role and RoleBinding are sufficient and more secure, and the exam tests understanding of scope versus permissions.
Detailed technical explanation
How to think about this question
Under the hood, RBAC in Kubernetes uses the RBAC API (rbac.authorization.k8s.io/v1) where Role and ClusterRole define rules with apiGroups, resources, and verbs. A RoleBinding binds a Role to a subject (user, group, or service account) within a specific namespace, while a ClusterRoleBinding binds a ClusterRole cluster-wide. For namespace-scoped resources like pods, using a Role with a RoleBinding is the most secure and precise method to enforce least privilege, as it prevents the subject from accessing resources in other namespaces even if the Role has broad permissions.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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 — A Role and RoleBinding are the correct combination because the CI/CD pipeline needs to create and delete pods only within the 'ci' namespace. A Role defines permissions scoped to a specific namespace, and a RoleBinding grants those permissions to a user or service account within that same namespace. This ensures the pipeline cannot affect resources in other namespaces.
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 →
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.