Question 204 of 997
Monitoring Logging and Runtime SecurityhardMultiple SelectObjective-mapped

CKS Monitoring Logging and Runtime Security Practice Question

This CKS practice question tests your understanding of monitoring logging and runtime security. 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.

Network Topology
$ kube-hunterreport jsonlog warnRefer to the exhibit.Exhibit:```"vulnerability": "CVE-2020-8558","component": "kubelet","severity": "medium",},"vulnerability": "CVE-2019-11245","severity": "high",

A security engineer runs kube-hunter against a production cluster and receives the above output. The cluster uses kubeadm with default settings. Which two actions should the engineer take to remediate the vulnerabilities?

Question 1hardmulti select
Full question →
Network Topology
$ kube-hunterreport jsonlog warnRefer to the exhibit.Exhibit:```"vulnerability": "CVE-2020-8558","component": "kubelet","severity": "medium",},"vulnerability": "CVE-2019-11245","severity": "high",

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

Upgrade the cluster to Kubernetes 1.14 or later to fix CVE-2019-11245

Option A is correct because CVE-2019-11245 affects kubelet container runtime exec probes in Kubernetes versions prior to 1.14, where containers could restart unexpectedly due to a race condition. Upgrading to 1.14 or later patches this vulnerability. Option C is correct because setting --anonymous-auth=false on the kubelet disables unauthenticated access to the kubelet API, which is a common finding from kube-hunter when default kubeadm settings leave anonymous authentication enabled.

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.

  • Upgrade the cluster to Kubernetes 1.14 or later to fix CVE-2019-11245

    Why this is correct

    The vulnerability is fixed in kubelet versions 1.13.9+, 1.14.5+, and 1.15.2+.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Set the kubelet flag --authentication-token-webhook=true

    Why it's wrong here

    This enables token review but does not disable anonymous access.

  • Configure the kubelet to set --anonymous-auth=false and restart the kubelet service

    Why this is correct

    This stops the kubelet from allowing unauthenticated requests.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Enable the NodeRestriction admission controller

    Why it's wrong here

    NodeRestriction limits node self-updates to the API server, but does not secure the kubelet API.

  • Modify the kube-apiserver manifest to set --anonymous-auth=false

    Why it's wrong here

    This affects the API server, not the kubelet's anonymous access.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse the kubelet's anonymous-auth flag with the API server's anonymous-auth flag, or think that enabling webhook authentication alone (Option B) disables anonymous access, when in fact anonymous auth must be explicitly disabled on the kubelet.

Detailed technical explanation

How to think about this question

Kube-hunter scans for kubelet anonymous authentication by default because kubeadm clusters often leave the kubelet's --anonymous-auth flag set to true, allowing any unauthenticated user to access the kubelet API on port 10250. CVE-2019-11245 specifically exploits a race condition in the kubelet's exec probe handler that could cause container restarts; upgrading to 1.14+ introduces a fix that serializes exec probe operations. In practice, a kube-hunter finding for anonymous auth is often combined with the ability to run arbitrary commands on nodes, making it a critical security gap.

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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.

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?

Monitoring Logging and Runtime Security — This question tests Monitoring Logging and Runtime Security — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Upgrade the cluster to Kubernetes 1.14 or later to fix CVE-2019-11245 — Option A is correct because CVE-2019-11245 affects kubelet container runtime exec probes in Kubernetes versions prior to 1.14, where containers could restart unexpectedly due to a race condition. Upgrading to 1.14 or later patches this vulnerability. Option C is correct because setting --anonymous-auth=false on the kubelet disables unauthenticated access to the kubelet API, which is a common finding from kube-hunter when default kubeadm settings leave anonymous authentication enabled.

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

Last reviewed: Jun 11, 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.