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.
Which TWO of the following are valid ways to create a Role in the 'default' namespace that grants get and list on pods?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
kubectl create role pod-reader --verb=get,list --resource=pods -n default
Option A is correct because `kubectl create role pod-reader --verb=get,list --resource=pods -n default` directly creates a Role in the default namespace with the specified verbs and resource. This command is a standard Kubernetes RBAC command that generates a Role with the correct apiGroups ("" for core resources) and the requested permissions.
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.
✓
kubectl create role pod-reader --verb=get,list --resource=pods -n default
Why this is correct
Imperative creation of Role with get and list on pods.
Related concept
Read the scenario before looking for a memorised answer.
✗
kubectl create role pod-reader --verb=discover --resource=pods -n default
Why it's wrong here
Discover is not a valid Kubernetes verb.
✗
kubectl create role pod-reader --verb=delete --resource=pods -n default
Why it's wrong here
Verb delete, not get/list.
✓
Apply a YAML with apiVersion: rbac.authorization.k8s.io/v1, kind: Role, rules: [apiGroups: [""], resources: ["pods"], verbs: ["get", "list"]]
Why this is correct
Declarative YAML for a Role.
Related concept
Read the scenario before looking for a memorised answer.
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse Role with ClusterRole, or assume that any verb like 'discover' is valid, or overlook that the question requires both 'get' and 'list' verbs specifically.
Detailed technical explanation
How to think about this question
Roles are namespace-scoped resources that define permissions within a single namespace, while ClusterRoles are cluster-scoped and can be used across all namespaces or for non-namespaced resources. The `kubectl create role` command automatically sets the apiGroups field to `[""]` for core resources like pods, which is equivalent to the `v1` API group. When using YAML, you must explicitly specify `apiGroups: [""]` to match the core group, as omitting it or using `apiGroups: ["v1"]` would be incorrect.
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.
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: kubectl create role pod-reader --verb=get,list --resource=pods -n default — Option A is correct because `kubectl create role pod-reader --verb=get,list --resource=pods -n default` directly creates a Role in the default namespace with the specified verbs and resource. This command is a standard Kubernetes RBAC command that generates a Role with the correct apiGroups ("" for core resources) and the requested permissions.
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.