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.
Which of the following is a recommended practice for securing Kubernetes Dashboard?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Deploy Dashboard with minimal RBAC permissions and access it via kubectl proxy.
Option A is correct because deploying the Kubernetes Dashboard with minimal RBAC permissions and accessing it via `kubectl proxy` follows the principle of least privilege and avoids exposing the Dashboard to the network. `kubectl proxy` creates a local HTTP proxy to the Kubernetes API server, which authenticates the user's kubeconfig credentials, ensuring that only authorized users can reach the Dashboard and that the Dashboard itself has no direct network exposure.
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.
✓
Deploy Dashboard with minimal RBAC permissions and access it via kubectl proxy.
Why this is correct
Minimal permissions and kubectl proxy provide secure access without public exposure.
Related concept
Read the scenario before looking for a memorised answer.
✗
Expose Dashboard using a NodePort service with a ClusterRole binding to cluster-admin.
Why it's wrong here
Cluster-admin grants full cluster access and NodePort exposes externally; this is insecure.
✗
Use a LoadBalancer service without authentication.
Why it's wrong here
This exposes Dashboard publicly without authentication, which is insecure.
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think exposing the Dashboard via NodePort or LoadBalancer is acceptable for convenience, but the CKS exam emphasizes that any direct network exposure of the Dashboard without strong authentication and TLS is a critical security violation.
Detailed technical explanation
How to think about this question
`kubectl proxy` binds to localhost (127.0.0.1) by default and uses the kubeconfig's bearer token or client certificate to authenticate with the API server, which then enforces RBAC. The Dashboard pod itself should have a dedicated ServiceAccount with only the permissions needed for its monitoring or management tasks, not `cluster-admin`. In a real-world scenario, an attacker scanning for open NodePorts could discover the Dashboard and exploit the elevated privileges to compromise the entire cluster.
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 CKS question in full detail.
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: Deploy Dashboard with minimal RBAC permissions and access it via kubectl proxy. — Option A is correct because deploying the Kubernetes Dashboard with minimal RBAC permissions and accessing it via `kubectl proxy` follows the principle of least privilege and avoids exposing the Dashboard to the network. `kubectl proxy` creates a local HTTP proxy to the Kubernetes API server, which authenticates the user's kubeconfig credentials, ensuring that only authorized users can reach the Dashboard and that the Dashboard itself has no direct network exposure.
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 →
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 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.