This KCNA practice question tests your understanding of kubernetes fundamentals. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A Deployment manages ReplicaSets. What is the primary benefit of using a Deployment over directly managing ReplicaSets?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "primary"
Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
Deployments can expose services externally
Why wrong: Services handle networking, not Deployments.
Deployments support rolling updates and rollbacks
Deployments enable controlled updates with revision history.
Deployments automatically configure DNS
Why wrong: DNS is managed by CoreDNS and Services.
Deployments provide persistent storage
Why wrong: Persistent storage is handled by PersistentVolumeClaims.
Answer choices
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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
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
Services handle networking, not Deployments.
Deployments support rolling updates and rollbacks
Why this is correct
Deployments enable controlled updates with revision history.
Clue confirmation
The clue word "primary" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Deployments automatically configure DNS
Why it's wrong here
DNS is managed by CoreDNS and Services.
Deployments provide persistent storage
Why it's wrong here
Persistent storage is handled by PersistentVolumeClaims.
Common exam traps
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.
Detailed technical explanation
Under the hood, a Deployment creates a ReplicaSet with a unique hash label (pod-template-hash) and manages the rollout by gradually scaling up the new ReplicaSet while scaling down the old one, using a configurable strategy (RollingUpdate or Recreate). The Deployment controller stores revision history in the .metadata.annotations (deployment.kubernetes.io/revision), allowing rollbacks to any previous revision via kubectl rollout undo. In a real-world scenario, if a misconfigured image causes Pods to crash, the Deployment's rolling update can be paused or rolled back automatically based on a progress deadline (default 10 minutes), preventing full downtime.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the KCNA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Kubernetes Fundamentals — study guide chapter
Learn the concepts, then practise the questions
Kubernetes Fundamentals practice questions
Targeted practice on this topic area only
All KCNA questions
997 questions across all exam domains
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise KCNA questions linked to Kubernetes Fundamentals.
Practise KCNA questions linked to Container Orchestration.
Practise KCNA questions linked to Cloud Native Architecture.
Practise KCNA questions linked to Cloud Native Observability.
Practise KCNA questions linked to Cloud Native Application Delivery.
Practise KCNA questions linked to KCNA fundamentals.
Practise KCNA questions linked to KCNA scenario.
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Kubernetes Fundamentals — This question tests Kubernetes Fundamentals — Read the scenario before looking for a memorised answer..
The correct answer is: 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "primary". Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
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 →
Last reviewed: Jun 30, 2026
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.
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.
Sign in to join the discussion.