CV0-004 Deployment Practice Question
A company is deploying a new version of a microservice on Amazon EKS. The deployment must ensure that new pods are created and become healthy before old pods are terminated. The current deployment uses a ReplicaSet. Which Kubernetes resource and strategy should be used?
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
✓
Deployment with RollingUpdate strategy
A Deployment manages ReplicaSets and supports a RollingUpdate strategy that creates new pods and waits for them to become ready before terminating old ones.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
ReplicaSet with RollingUpdate strategy
Why it's wrong here
A bare ReplicaSet has no update strategy field; RollingUpdate is a Deployment-level strategy, so this combination cannot be configured. It is tempting because ReplicaSet already manages the running pods and RollingUpdate describes exactly the desired behaviour, but the resource lacks that capability. A Deployment wrapping the ReplicaSet provides maxSurge and maxUnavailable control.
- ✗
DaemonSet with RollingUpdate
Why it's wrong here
DaemonSet schedules one pod per node for cluster-wide agents such as log collectors or CNI plugins; it does not maintain a fixed replica count for a service. It is tempting because it supports RollingUpdate, but that strategy replaces node-bound pods, not service replicas. A Deployment with RollingUpdate creates healthy new pods before terminating old ones.
- ✓
Deployment with RollingUpdate strategy
Why this is correct
RollingUpdate replaces pods incrementally, honouring maxSurge and maxUnavailable so new pods reach readiness before old ones terminate. A bare ReplicaSet cannot orchestrate this ordering during updates, so the Deployment controller is required to satisfy the zero-downtime constraint.
- ✗
StatefulSet with OnDelete strategy
Why it's wrong here
StatefulSet provides stable network identities and ordered, sequential pod management for stateful workloads; OnDelete leaves old pods running until manually removed, so no automatic health-gated replacement occurs. It is tempting because StatefulSet offers controlled rollout ordering, but that ordering suits databases and clustered state, not stateless microservices needing zero-downtime replacement.
Go deeper
Related to this question
About these practice questions
This CV0-004 question is part of Courseiva's 834-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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 CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.