Question 219 of 1,005

Quick Answer

The answer is to create a ClusterRole and a ClusterRoleBinding. This is correct because a ServiceAccount named 'jenkins' in the 'ci' namespace needs cross-namespace ServiceAccount permissions to list pods in the 'production' namespace. A ClusterRole grants permissions cluster-wide, not limited to a single namespace, while a ClusterRoleBinding binds that ClusterRole to the ServiceAccount regardless of which namespace the ServiceAccount resides in. In contrast, a Role and RoleBinding are namespace-scoped and cannot grant access across namespaces. On the Certified Kubernetes Administrator CKA exam, this scenario tests your understanding of how RBAC resources handle namespace boundaries—a common trap is reaching for a RoleBinding, which would fail because it cannot cross namespaces. A useful memory tip: think of ClusterRole and ClusterRoleBinding as the "global passport" for a ServiceAccount, allowing it to operate in any namespace, whereas Role and RoleBinding are like a "local ID card" valid only within one namespace.

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.

You need to grant a ServiceAccount named 'jenkins' in the 'ci' namespace the ability to list pods in the 'production' namespace. Which RBAC resources should you create?

Question 1hardmultiple choice
Full question →

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

Create a ClusterRole and a ClusterRoleBinding binding the ServiceAccount to the ClusterRole.

Option D is correct because a ServiceAccount in one namespace ('ci') needs to list pods in another namespace ('production'). A ClusterRole grants permissions cluster-wide (or across namespaces), and a ClusterRoleBinding binds it to the ServiceAccount, allowing cross-namespace access. Roles and RoleBindings are namespace-scoped and cannot grant permissions across 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.

  • Create a ClusterRole in the 'production' namespace and a RoleBinding in the 'ci' namespace.

    Why it's wrong here

    ClusterRoles are not namespaced; you cannot create a ClusterRole inside a namespace. Also RoleBinding cannot bind a ClusterRole to grant permissions in a different namespace.

  • Create a Role in the 'production' namespace and a RoleBinding in the 'ci' namespace referencing the Role.

    Why it's wrong here

    A RoleBinding cannot reference a Role in a different namespace; RoleBindings are namespaced and must reference a Role in the same namespace.

  • Create a Role in the 'ci' namespace and a RoleBinding binding the ServiceAccount to the Role.

    Why it's wrong here

    A Role is namespaced to 'ci' and cannot grant permissions in 'production'.

  • Create a ClusterRole and a ClusterRoleBinding binding the ServiceAccount to the ClusterRole.

    Why this is correct

    A ClusterRole can define permissions for pods in any namespace, and a ClusterRoleBinding grants those permissions cluster-wide, including to the ServiceAccount.

    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 often think a RoleBinding can bind a Role from another namespace, but RoleBindings are namespace-scoped and can only reference Roles in the same namespace, making a ClusterRole and ClusterRoleBinding necessary for cross-namespace access.

Detailed technical explanation

How to think about this question

Under the hood, Kubernetes RBAC evaluates permissions by checking the Role or ClusterRole referenced by the binding. A ClusterRoleBinding grants all permissions defined in the ClusterRole to the subjects across all namespaces, while a RoleBinding with a ClusterRole grants permissions only in the RoleBinding's namespace. The 'list pods' verb requires get, list, and watch permissions on the 'pods' resource, which must be explicitly defined in the ClusterRole.

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.

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.

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.

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: Create a ClusterRole and a ClusterRoleBinding binding the ServiceAccount to the ClusterRole. — Option D is correct because a ServiceAccount in one namespace ('ci') needs to list pods in another namespace ('production'). A ClusterRole grants permissions cluster-wide (or across namespaces), and a ClusterRoleBinding binds it to the ServiceAccount, allowing cross-namespace access. Roles and RoleBindings are namespace-scoped and cannot grant permissions across 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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

2 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 need to grant a ServiceAccount named 'monitor-sa' in namespace 'monitoring' the ability to read Pods and Services across all namespaces. Which TWO resources are needed? (Choose TWO.)

hard
  • A.ClusterRoleBinding binding the ClusterRole to the ServiceAccount
  • B.ServiceAccount token secret
  • C.ClusterRole with rules for pods and services
  • D.RoleBinding in each namespace
  • E.Role in the 'monitoring' namespace

Why A: A is correct because a ClusterRoleBinding grants cluster-scoped permissions to a subject (like a ServiceAccount) across all namespaces. Since the ServiceAccount 'monitor-sa' needs to read Pods and Services in every namespace, a ClusterRoleBinding is the appropriate resource to bind a ClusterRole to the ServiceAccount, avoiding the need for per-namespace RoleBindings.

Variation 2. An administrator needs to allow a service account 'monitor-sa' in namespace 'monitoring' to read pods across all namespaces. Which RBAC resources should be created?

medium
  • A.Create a ClusterRole with pod read permissions and a ClusterRoleBinding to monitor-sa
  • B.Create a ClusterRole with pod read permissions and a RoleBinding in each namespace
  • C.Create a Role in the monitoring namespace and a RoleBinding to monitor-sa
  • D.Create a Role with pod read permissions and a ClusterRoleBinding to monitor-sa

Why A: A ClusterRole is required because the service account needs to read pods across all namespaces, which is a cluster-scoped permission. A ClusterRoleBinding binds that ClusterRole to the service account 'monitor-sa', granting the permissions cluster-wide. This is the correct approach for cross-namespace access.

Last reviewed: Jun 24, 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.

Loading comments…

Sign in to join the discussion.

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.