KCNA Kubernetes Fundamentals Practice Question
A Deployment manages ReplicaSets. What is the primary benefit of using a Deployment over directly managing ReplicaSets?
⚠ Common exam trap
CNCF often tests the misconception that Deployments directly manage Pods, but the trap here is that candidates may confuse the Deployment's high-level features (like rolling updates) with other Kubernetes resources (Services, DNS, storage) that handle networking, naming, or data persistence, leading them to pick a wrong answer that describes a capability of a different resource.
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
✓
Deployments support rolling updates and rollbacks
The primary benefit of using a Deployment over directly managing ReplicaSets is that Deployments provide declarative updates for Pods and ReplicaSets, including built-in support for rolling updates and rollbacks. This allows you to update the desired state (e.g., a new container image version) and have the Deployment controller automatically orchestrate the transition, while also enabling you to revert to a previous revision if the update fails. Directly managing ReplicaSets would require manual steps to scale down old ReplicaSets and scale up new ones, and it lacks the automated revision history and rollback capabilities that Deployments offer.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deployments can expose services externally
Why it's wrong here
Exposing services externally is performed by a Service of type LoadBalancer or NodePort, not by a Deployment. It is tempting because Deployments and Services are commonly created together, but the Deployment's role is managing ReplicaSets and rolling updates, not external exposure.
- ✓
Deployments support rolling updates and rollbacks
Why this is correct
Deployments add a control layer above ReplicaSets, automatically creating a new ReplicaSet for each pod template change and shifting replicas gradually. This enables rolling updates and rollback to a previous revision, which direct ReplicaSet management does not provide.
- ✗
Deployments automatically configure DNS
Why it's wrong here
DNS configuration is handled by CoreDNS and Service records, not by a Deployment. It is tempting because Deployments are often paired with Services that receive DNS names, but the Deployment controller's actual function is managing ReplicaSets and rolling updates.
- ✗
Deployments provide persistent storage
Why it's wrong here
Persistent storage is provided by PersistentVolumes and PersistentVolumeClaims, not by a Deployment. It is tempting because Deployments can mount volumes in their pod template, but the Deployment controller itself only manages ReplicaSets and pod revisions, not storage provisioning.
Go deeper
Related to this question
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 →
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.