Courseiva
Kubernetes Fundamentals →mediumMultiple Choice

KCNA Kubernetes Fundamentals Practice Question

What is the role of kube-scheduler in Kubernetes?

⚠ Common exam trap

A common misconception is that the scheduler also manages pod lifecycle or health checks, leading candidates to confuse the scheduler's static assignment role with the kubelet's dynamic runtime responsibilities.

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

✓

To assign pods to nodes

The kube-scheduler is responsible for selecting an optimal node for newly created pods that have not yet been assigned to a node. It evaluates constraints such as resource requirements, affinity/anti-affinity rules, and data locality, then binds the pod to the chosen node via the Kubernetes API. This makes option A correct because scheduling is the scheduler's primary and defining function.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    To assign pods to nodes

    Why this is correct

    The scheduler watches for newly created Pods with no assigned node and selects a suitable node based on resource requests, affinity rules, taints and tolerations. It writes that binding to the API server, satisfying the stem's constraint that pods must be placed onto nodes.

  • ✗

    To run container health checks

    Why it's wrong here

    Container health checks are executed by the kubelet on each node, using liveness, readiness and startup probes defined in the Pod spec; kube-scheduler only selects a node for unscheduled Pods. It is tempting because scheduling and probe handling are both node-level concerns, but the kubelet owns probe execution.

  • ✗

    To store cluster configuration

    Why it's wrong here

    Cluster configuration is persisted in etcd, the distributed key-value store that kube-apiserver reads and writes; kube-scheduler only binds Pods to nodes. It is tempting because the scheduler does read cluster state to make decisions, but it consumes that data from the API server rather than storing it.

  • ✗

    To provide network rules for services

    Why it's wrong here

    Network rules for Services are implemented by kube-proxy, which programs iptables or IPVS rules on each node; kube-scheduler only assigns Pods to nodes. It is tempting because Services do need cluster-wide traffic handling, but that responsibility sits with kube-proxy and the CNI, not the scheduler.

About these practice questions

One of 930 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This KCNA 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 KCNA exam.