This CKS practice question tests your understanding of cluster hardening. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 company uses kube-bench to scan their cluster. The report shows a warning: 'Ensure that the --authorization-mode argument is set to Node,RBAC'. What is the best way to fix this?
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.
Add --authorization-mode=AlwaysDeny to the API server
Why wrong: AlwaysDeny is not a valid mode; it should be Node,RBAC.
Restart the API server with --authorization-webhook-config-file
Why wrong: Webhook is additional, not a replacement.
Set --authorization-mode=RBAC only
Why wrong: Missing Node mode.
Edit the kube-apiserver manifest to add --authorization-mode=Node,RBAC
Sets both Node and RBAC as required.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Edit the kube-apiserver manifest to add --authorization-mode=Node,RBAC
Option D is correct because kube-bench checks that the API server's `--authorization-mode` includes both `Node` and `RBAC` in that order. The `Node` authorizer must come first to handle node-specific requests efficiently, followed by `RBAC` for user and service account authorization. Editing the kube-apiserver manifest (typically `/etc/kubernetes/manifests/kube-apiserver.yaml`) to add `--authorization-mode=Node,RBAC` ensures the static pod is automatically restarted by the kubelet with the correct configuration.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Add --authorization-mode=AlwaysDeny to the API server
Why it's wrong here
AlwaysDeny is not a valid mode; it should be Node,RBAC.
Restart the API server with --authorization-webhook-config-file
Why it's wrong here
Webhook is additional, not a replacement.
Set --authorization-mode=RBAC only
Why it's wrong here
Missing Node mode.
Edit the kube-apiserver manifest to add --authorization-mode=Node,RBAC
Why this is correct
Sets both Node and RBAC as required.
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
The trap here is that candidates may think setting only `RBAC` is sufficient because it is the most common authorization mode, but the CKS exam specifically tests the requirement that `Node` must precede `RBAC` to handle node-level authorization correctly.
Detailed technical explanation
The `Node` authorizer is a special-purpose authorizer that grants permissions to kubelets based on their node identity, using the `system:nodes` group and a specific subject access review path. It must be placed before `RBAC` in the list because the API server evaluates authorizers in order; if `RBAC` were first, it would incorrectly deny or allow node requests that should be handled by the `Node` authorizer. In a real-world scenario, misordering or omitting the `Node` authorizer can cause kubelet bootstrap failures or node authorization errors that are difficult to debug.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Cluster Hardening — study guide chapter
Learn the concepts, then practise the questions
Cluster 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CKS questions linked to Monitoring Logging and Runtime Security.
Practise CKS questions linked to Cluster Setup and Hardening.
Practise CKS questions linked to System Hardening.
Practise CKS questions linked to Minimize Microservice Vulnerabilities.
Practise CKS questions linked to Supply Chain Security.
Practise CKS questions linked to Monitoring, Logging and Runtime Security.
Practise CKS questions linked to Cluster Setup.
Practise CKS questions linked to Cluster Hardening.
Practise CKS questions linked to CKS fundamentals.
Practise CKS questions linked to CKS scenario.
Practise CKS questions linked to CKS troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Cluster Hardening — This question tests Cluster Hardening — Read the scenario before looking for a memorised answer..
The correct answer is: Edit the kube-apiserver manifest to add --authorization-mode=Node,RBAC — Option D is correct because kube-bench checks that the API server's `--authorization-mode` includes both `Node` and `RBAC` in that order. The `Node` authorizer must come first to handle node-specific requests efficiently, followed by `RBAC` for user and service account authorization. Editing the kube-apiserver manifest (typically `/etc/kubernetes/manifests/kube-apiserver.yaml`) to add `--authorization-mode=Node,RBAC` ensures the static pod is automatically restarted by the kubelet with the correct configuration.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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.
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 11, 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.