KCNA Container Orchestration Practice Question
You are designing a microservices application that requires each service to be independently deployable and scalable. The services communicate over HTTP and need service discovery. Which orchestration feature BEST addresses the need for service discovery?
⚠ Common exam trap
A common trap in CNCF exams is confusing the Horizontal Pod Autoscaler (HPA), which scales pods, with the Kubernetes Service, which provides stable network endpoints for service discovery. Remember: HPA handles scaling, Service handles discovery.
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
✓
Kubernetes Service
Kubernetes Service is the correct choice because it provides a stable network endpoint (IP address and DNS name) for a set of pods, enabling service discovery via DNS or environment variables. This allows microservices to locate and communicate with each other over HTTP without hardcoding IP addresses, which is essential for independent deployability and scalability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Kubernetes Service
Why this is correct
A Kubernetes Service assigns a stable DNS name and virtual IP that load-balances across the backing pods, so services locate each other without tracking ephemeral pod IPs. This directly satisfies the HTTP service-discovery requirement while keeping each deployment independently scalable.
- ✗
Horizontal Pod Autoscaler
Why it's wrong here
Horizontal Pod Autoscaler adjusts replica counts from CPU or custom metrics; it neither registers service endpoints nor resolves names, so discovery remains unaddressed. It is tempting because independent scalability is named in the stem, and HPA is correct when traffic-driven replica scaling, not discovery, is the requirement.
- ✗
ConfigMap
Why it's wrong here
ConfigMap injects non-confidential configuration data as environment variables or mounted files; it maintains no dynamic endpoint registry, so services cannot locate each other. It is tempting because service configuration often lives in ConfigMaps, and this is correct when externalising settings such as log levels or feature flags.
- ✗
PersistentVolume
Why it's wrong here
PersistentVolume supplies durable block or file storage to pods; it holds no registry mapping service names to cluster IPs, so HTTP callers cannot resolve peers. It is tempting because stateful microservices need persistent storage, and a PersistentVolume is the right choice when a database pod must retain data across restarts.
Go deeper
Related to this question
Learn chapter
Container Orchestration Essentials
Key term
ReplicaSet and Replication
A ReplicaSet ensures a specified number of identical pod instances are running at all times in Kubernetes, using replication to maintain availability and stability.
Key term
Kubernetes API Primitives
Kubernetes API Primitives are the basic building blocks that the Kubernetes API uses to represent and manage the state of a cluster, such as Pods, Services, Deployments, and Namespaces.
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 →
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.