- A
Create a ClusterRole with get and list on secrets, then a RoleBinding in 'production'
Why wrong: This combination is technically valid because a ClusterRole bound via a RoleBinding is scoped to the namespace of the RoleBinding. However, it is not the most direct approach; using a Role (which is inherently namespaced) avoids any confusion about scope and is the intended answer.
- B
Create a Role with get and list on secrets in namespace 'production', then a ClusterRoleBinding
Why wrong: This is incorrect. A Role is namespaced, but a ClusterRoleBinding binds to all namespaces, which would grant secret access cluster-wide instead of only in the 'production' namespace.
- C
Create a ClusterRole with get and list on secrets, then a ClusterRoleBinding to bind it to the user
Why wrong: This is incorrect. A ClusterRole with a ClusterRoleBinding grants permissions cluster-wide, not limited to the 'production' namespace.
- D
Create a Role with get and list on secrets in namespace 'production', then a RoleBinding in 'production'
This is correct. A Role is namespaced and grants permissions only within the specified namespace ('production'). A RoleBinding binds the Role to a user, group, or service account within the same namespace, ensuring the permissions are scoped exactly to 'production'.
Creating RBAC to Read Secrets in a Single Namespace
This CKS practice question tests your understanding of cluster setup and hardening. 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 create an RBAC role that allows reading secrets only in namespace 'production'. Which ClusterRole and RoleBinding combination is correct?
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 Role with get and list on secrets in namespace 'production', then a RoleBinding in 'production'
Option D is correct because a Role is namespaced and can only grant permissions within a specific namespace, which is 'production' in this case. A RoleBinding then binds that Role to a user, group, or service account within the same namespace, ensuring the permissions are scoped correctly. This combination restricts secret read access exclusively to the 'production' namespace, meeting the requirement precisely.
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 with get and list on secrets, then a RoleBinding in 'production'
Why it's wrong here
This combination is technically valid because a ClusterRole bound via a RoleBinding is scoped to the namespace of the RoleBinding. However, it is not the most direct approach; using a Role (which is inherently namespaced) avoids any confusion about scope and is the intended answer.
- ✗
Create a Role with get and list on secrets in namespace 'production', then a ClusterRoleBinding
Why it's wrong here
This is incorrect. A Role is namespaced, but a ClusterRoleBinding binds to all namespaces, which would grant secret access cluster-wide instead of only in the 'production' namespace.
- ✗
Create a ClusterRole with get and list on secrets, then a ClusterRoleBinding to bind it to the user
Why it's wrong here
This is incorrect. A ClusterRole with a ClusterRoleBinding grants permissions cluster-wide, not limited to the 'production' namespace.
- ✓
Create a Role with get and list on secrets in namespace 'production', then a RoleBinding in 'production'
Why this is correct
This is correct. A Role is namespaced and grants permissions only within the specified namespace ('production'). A RoleBinding binds the Role to a user, group, or service account within the same namespace, ensuring the permissions are scoped exactly to 'production'.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the misconception that ClusterRoles are always cluster-wide even when bound via a RoleBinding, but the trap here is that a ClusterRole bound with a RoleBinding actually scopes permissions to that namespace, yet the question's requirement for a Role (not ClusterRole) is the precise answer because a Role is inherently namespaced and avoids any ambiguity about scope.
Trap categories for this question
Similar concept trap
This combination is technically valid because a ClusterRole bound via a RoleBinding is scoped to the namespace of the RoleBinding. However, it is not the most direct approach; using a Role (which is inherently namespaced) avoids any confusion about scope and is the intended answer.
Detailed technical explanation
How to think about this question
Under the hood, Kubernetes RBAC uses Role and ClusterRole objects to define rules, and RoleBinding and ClusterRoleBinding to associate them with subjects. A RoleBinding can only reference a Role in the same namespace or a ClusterRole, but when referencing a ClusterRole, the permissions are still scoped to the RoleBinding's namespace, which is a subtle but critical distinction; however, the question explicitly requires a Role (not ClusterRole) to avoid any cluster-wide leakage. In real-world scenarios, this pattern is used to enforce least privilege, such as granting a CI/CD service account read-only access to secrets only in a specific production namespace, preventing accidental exposure across environments.
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 CKS 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.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
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.
- →
Cluster Setup and Hardening — study guide chapter
Learn the concepts, then practise the questions
- →
Cluster Setup and Hardening practice questions
Targeted practice on this topic area only
- →
All CKS questions
997 questions across all exam domains
- →
Certified Kubernetes Security Specialist CKS study guide
Full concept coverage aligned to exam objectives
- →
CKS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Cluster Setup and Hardening practice questions
Practise CKS questions linked to Cluster Setup and Hardening.
System Hardening practice questions
Practise CKS questions linked to System Hardening.
Minimize Microservice Vulnerabilities practice questions
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Supply Chain Security practice questions
Practise CKS questions linked to Supply Chain Security.
Monitoring, Logging and Runtime Security practice questions
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Cluster Setup practice questions
Practise CKS questions linked to Cluster Setup.
Cluster Hardening practice questions
Practise CKS questions linked to Cluster Hardening.
CKS fundamentals practice questions
Practise CKS questions linked to CKS fundamentals.
CKS scenario practice questions
Practise CKS questions linked to CKS scenario.
CKS troubleshooting practice questions
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Start a free CKS 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 CKS question test?
Cluster Setup and Hardening — This question tests Cluster Setup and Hardening — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a Role with get and list on secrets in namespace 'production', then a RoleBinding in 'production' — Option D is correct because a Role is namespaced and can only grant permissions within a specific namespace, which is 'production' in this case. A RoleBinding then binds that Role to a user, group, or service account within the same namespace, ensuring the permissions are scoped correctly. This combination restricts secret read access exclusively to the 'production' namespace, meeting the requirement precisely.
What should I do if I get this CKS 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 →
Keep practising
More CKS practice questions
- Which flag is used to restrict the kubelet's ability to modify node status and pods?
- A Falco rule has priority `WARNING` and output: `Sensitive file opened (user=%user.name command=%proc.cmdline file=%fd.n…
- Falco detects a shell being opened inside a container. Which Falco rule field is used to specify the syscall condition f…
- A security audit reveals that a ServiceAccount named 'monitor' has a ClusterRoleBinding to the cluster-admin role. What…
- Match each Kubernetes security component to its description.
- Match each Kubernetes certificate type to its usage.
Last reviewed: Jun 30, 2026
This CKS 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 CKS 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.