Question 64 of 997
Cluster Setup and HardeningeasyMultiple ChoiceObjective-mapped

Can You Disable Anonymous Auth on API Server with kubectl?

This CKS practice question tests your understanding of cluster setup and hardening. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 kubectl command will disable anonymous authentication on a kube-apiserver?

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

kubectl edit pod kube-apiserver -n kube-system and add --anonymous-auth=false

None of the provided kubectl commands will disable anonymous authentication on the kube-apiserver because the kube-apiserver runs as a static pod, and static pods are managed by the kubelet based on manifest files in /etc/kubernetes/manifests/. Editing the pod via `kubectl edit` creates a temporary change that the kubelet will revert to match the manifest. To disable anonymous authentication, you must directly edit the static pod manifest file (e.g., /etc/kubernetes/manifests/kube-apiserver.yaml) and add `--anonymous-auth=false`.

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 edit pod kube-apiserver -n kube-system and add --anonymous-auth=false

    Why this is correct

    Incorrect because the kube-apiserver is a static pod. While `kubectl edit` can temporarily add the flag, the kubelet will revert the change to match the manifest file, so the change does not persist.

    Related concept

    Read the scenario before looking for a memorised answer.

  • kubectl run --image=k8s.gcr.io/kube-apiserver --env=ANONYMOUS_AUTH=false

    Why it's wrong here

    Incorrect. `kubectl run` does not modify the existing kube-apiserver; it creates a new pod. The kube-apiserver does not read environment variables for authentication settings.

  • kubectl patch node <nodename> -p '{"spec":{"anonymousAuth":false}}'

    Why it's wrong here

    Incorrect. `kubectl patch node` modifies the node object, not the kube-apiserver pod. The `anonymousAuth` field does not exist on nodes.

  • kubectl set env deployment/kube-apiserver -n kube-system ANONYMOUS_AUTH=false

    Why it's wrong here

    Incorrect. The kube-apiserver is not a Deployment, and `kubectl set env` does not affect static pods. Environment variables are not used for this configuration.

Common exam traps

Common exam trap: answer the scenario, not the keyword

CNCF often tests the misconception that the kube-apiserver can be configured via environment variables or that it runs as a Deployment, when in fact it is a static pod configured solely through command-line arguments in its manifest file. Additionally, editing a static pod with `kubectl edit` does not persist changes.

Detailed technical explanation

How to think about this question

The kube-apiserver's `--anonymous-auth` flag controls whether requests without authentication credentials are allowed; when set to `false`, the apiserver returns HTTP 401 Unauthorized for unauthenticated requests, which is critical for enforcing RBAC and preventing anonymous access to cluster resources. Static pods are managed directly by the kubelet from manifest files in `/etc/kubernetes/manifests/`, so editing the pod object via kubectl actually modifies the underlying manifest, triggering an automatic restart of the apiserver container. In a real-world scenario, disabling anonymous authentication is a key hardening step recommended by the CIS Kubernetes Benchmark, as it prevents potential information disclosure or privilege escalation via anonymous API calls.

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.

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.

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.

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: kubectl edit pod kube-apiserver -n kube-system and add --anonymous-auth=false — None of the provided kubectl commands will disable anonymous authentication on the kube-apiserver because the kube-apiserver runs as a static pod, and static pods are managed by the kubelet based on manifest files in /etc/kubernetes/manifests/. Editing the pod via `kubectl edit` creates a temporary change that the kubelet will revert to match the manifest. To disable anonymous authentication, you must directly edit the static pod manifest file (e.g., /etc/kubernetes/manifests/kube-apiserver.yaml) and add `--anonymous-auth=false`.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More CKS practice questions

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

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.