CV0-004 Deployment Practice Question
A cloud engineer is deploying a new version of a web application to a Kubernetes cluster. The application must remain available during the update, and the team wants to minimize the risk of exposing users to a faulty version. They decide to use a deployment strategy that gradually shifts traffic to the new version while monitoring for errors. Which Kubernetes resource should they configure to achieve this?
⚠ Common exam trap
It's easy for candidates to confuse a Service's traffic distribution with a Deployment's rollout control; a Service balances traffic but does not manage version updates.
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
✓
A Deployment with a RollingUpdate strategy and maxSurge/maxUnavailable parameters.
A Deployment with a RollingUpdate strategy is the native Kubernetes mechanism for gradually updating application instances while preserving availability. By configuring maxSurge and maxUnavailable, the engineer can control how many extra pods are created and how many old pods are taken down at once. This enables monitoring and, if necessary, pausing or rolling back the update to avoid exposing users to a faulty version.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A Deployment with a RollingUpdate strategy and maxSurge/maxUnavailable parameters.
Why this is correct
A Deployment with RollingUpdate strategy gradually replaces old pods with new ones while maintaining availability. By setting maxSurge and maxUnavailable, the engineer controls the pace of the rollout. This allows monitoring and, if needed, pausing or rolling back the deployment. It is the standard way to achieve zero-downtime updates in Kubernetes without additional tools.
- ✗
A StatefulSet with ordered pod management.
Why it's wrong here
StatefulSets are designed for stateful applications that require stable network identities and persistent storage. They update pods in a sequential, ordered manner, which can cause downtime if not carefully managed. They do not provide the fine-grained traffic shifting and surge control needed for a stateless web application rollout.
- ✗
A Service of type LoadBalancer with session affinity enabled.
Why it's wrong here
A Service of type LoadBalancer distributes traffic to pods but does not control the rollout of a new version. Session affinity only ensures that a client sticks to the same pod, which can actually prolong exposure to a faulty version if the client is routed to a bad pod. It does not provide gradual traffic shifting or automated rollback based on health checks.
- ✗
A DaemonSet that runs a pod on every node.
Why it's wrong here
A DaemonSet ensures that a copy of a pod runs on all (or some) nodes, typically for cluster-wide services like log collectors or monitoring agents. It is not used for deploying application versions with gradual traffic shifting. Updating a DaemonSet replaces pods node-by-node but does not manage user traffic or provide rollout controls like maxSurge.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CV0-004 question from scratch — 834 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.