Courseiva
Container Orchestration →easyMultiple Select

KCNA Container Orchestration Practice Question

Which TWO are benefits of using a container orchestration platform like Kubernetes? (Select TWO.)

⚠ Common exam trap

CNCF often tests the distinction between manual and automatic scaling; candidates may incorrectly select manual scaling as a benefit because they confuse it with the ability to scale, but the question asks for benefits of using the platform, which include automation, not manual effort.

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

✓

Automatic service discovery and load balancing

Option C is correct because Kubernetes provides built-in service discovery through Services and DNS (CoreDNS), automatically routing traffic to healthy Pods and distributing load across replicas via kube-proxy, eliminating manual endpoint configuration. Option D is correct because Kubernetes controllers such as the ReplicaSet and kubelet continuously reconcile desired state, automatically restarting or rescheduling failed containers to maintain the declared replica count. Option A is incorrect because orchestration platforms are designed to reduce operational complexity by abstracting infrastructure management, not increase application complexity. Option B is incorrect because Kubernetes runs containers via a container runtime (containerd, CRI-O) on shared nodes; it does not require a dedicated hypervisor per container. Option E is incorrect because Kubernetes supports automatic horizontal scaling through the Horizontal Pod Autoscaler (HPA) based on CPU, memory, or custom metrics, rather than requiring manual scaling.

Answer analysis

Option-by-option breakdown

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

  • ✗

    Increases application complexity

    Why it's wrong here

    "Increases application complexity" describes an outcome Kubernetes does not deliver as a benefit; orchestration abstracts scheduling, scaling and self-healing, reducing operational burden rather than adding it. It is tempting because Kubernetes does introduce control-plane components, manifests and networking layers, so complexity rises for teams adopting it — but that is a cost of implementation, not a listed benefit.

  • ✗

    Requires a dedicated hypervisor for each container

    Why it's wrong here

    Requiring a dedicated hypervisor per container describes virtual machines, not containers: each container shares the host OS kernel, so no hypervisor layer exists. It is tempting because hypervisors do provide strong isolation, making that architecture the right choice when hardware-level separation or running heterogeneous kernels is mandated.

  • ✓

    Automatic service discovery and load balancing

    Why this is correct

    Kubernetes assigns each Service a stable virtual IP and DNS name, then distributes traffic across matching healthy pods automatically. This removes the need for applications to track individual pod addresses, satisfying the requirement for built-in service discovery and load balancing.

  • ✓

    Self-healing (automatic restart of failed containers)

    Why this is correct

    Kubernetes continuously reconciles desired state against actual state: when a pod or its node fails, the ReplicaSet controller creates replacement pods to restore the declared replica count. This automatic remediation is the self-healing benefit the option describes.

  • ✗

    Manual scaling of applications

    Why it's wrong here

    Manual scaling requires an operator to adjust replica counts by hand, so it delivers none of the automated elasticity Kubernetes provides through its Horizontal Pod Autoscaler and declarative replica management. It is tempting because manual scaling is a genuine operational task, and would be the correct approach for a small, static workload where automation overhead is unjustified.

About these practice questions

Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.