- A
Set automountServiceAccountToken to false on the pods
Why wrong: This prevents token mounting but does not address existing permissions.
- B
Add a second ClusterRoleBinding to a more restrictive role
Why wrong: Adding another binding does not remove the cluster-admin binding.
- C
Delete the ServiceAccount
Why wrong: Deleting the account may break applications; better to restrict permissions.
- D
Create a new ClusterRoleBinding with a limited role
This reduces privileges while maintaining functionality.
CKS Cluster Setup and Hardening Practice Question
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.
A security audit reveals that a ServiceAccount named 'monitor' has a ClusterRoleBinding to the cluster-admin role. What is the best remediation?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"best"Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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 new ClusterRoleBinding with a limited role
Option D is correct because the best practice is to replace an overly permissive ClusterRoleBinding (like cluster-admin) with a new binding that grants only the specific permissions the 'monitor' ServiceAccount needs, following the principle of least privilege. Deleting the ServiceAccount (C) might break dependent workloads, while merely adding a second binding (B) doesn't remove the dangerous cluster-admin binding. Setting automountServiceAccountToken to false (A) prevents token mounting but doesn't revoke the existing RBAC permissions, leaving the account still capable of escalating privileges if the token is obtained elsewhere.
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.
- ✗
Set automountServiceAccountToken to false on the pods
Why it's wrong here
This prevents token mounting but does not address existing permissions.
- ✗
Add a second ClusterRoleBinding to a more restrictive role
Why it's wrong here
Adding another binding does not remove the cluster-admin binding.
- ✗
Delete the ServiceAccount
Why it's wrong here
Deleting the account may break applications; better to restrict permissions.
- ✓
Create a new ClusterRoleBinding with a limited role
Why this is correct
This reduces privileges while maintaining functionality.
Clue confirmation
The clue word "best" in the question point toward this answer.
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 simply adding a restrictive binding or disabling token mounting is sufficient to limit permissions, when in reality RBAC permissions are cumulative and the original dangerous binding must be explicitly removed.
Detailed technical explanation
How to think about this question
Kubernetes RBAC is additive: when a user or ServiceAccount has multiple ClusterRoleBindings, the effective permissions are the union of all roles. The cluster-admin role is defined by the system:ClusterRole 'cluster-admin', which grants access to all API resources and verbs. A proper remediation involves creating a custom ClusterRole with only the necessary verbs (e.g., get, list, watch) on specific resources (e.g., pods, nodes), then binding it via a new ClusterRoleBinding, and finally deleting the old cluster-admin binding. This ensures the 'monitor' account can only perform monitoring tasks, not administrative actions like deleting secrets or modifying RBAC.
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.
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 new ClusterRoleBinding with a limited role — Option D is correct because the best practice is to replace an overly permissive ClusterRoleBinding (like cluster-admin) with a new binding that grants only the specific permissions the 'monitor' ServiceAccount needs, following the principle of least privilege. Deleting the ServiceAccount (C) might break dependent workloads, while merely adding a second binding (B) doesn't remove the dangerous cluster-admin binding. Setting automountServiceAccountToken to false (A) prevents token mounting but doesn't revoke the existing RBAC permissions, leaving the account still capable of escalating privileges if the token is obtained elsewhere.
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.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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 →
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.