CV0-004 Deployment Practice Question
A cloud engineer is tasked with deploying a containerized application on Kubernetes. The application must handle varying loads, and the deployment should automatically replace failed containers. Which Kubernetes object should the engineer use to achieve self-healing and scalability?
⚠ Common exam trap
CompTIA Cloud+ often tests the misconception that a Pod alone provides self-healing, but in Kubernetes, a Pod is a non-self-healing atomic unit; only controllers like Deployment (or StatefulSet/DaemonSet) provide automatic replacement and scaling.
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
A Deployment is the correct Kubernetes object because it manages ReplicaSets to provide declarative updates, self-healing (automatic replacement of failed pods), and scalability (adjusting replica counts). Unlike a standalone Pod, a Deployment ensures the desired state is maintained, automatically rescheduling containers if they fail.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
ConfigMap
Why it's wrong here
A ConfigMap injects configuration data as environment variables or mounted files; it holds no pod replica count and cannot reschedule failed containers. It is tempting because it decouples configuration from images, but self-healing and load-driven scaling require a Deployment managing a ReplicaSet, which ConfigMaps do not provide.
- ✗
Service
Why it's wrong here
A Service provides a stable virtual IP and load-balances traffic across existing pods; it neither creates pods nor restarts failed ones. It is tempting because it distributes load, but that is connection-level balancing, not replica scaling, so a Deployment is required for self-healing and elasticity.
- ✓
Deployment
Why this is correct
A Deployment manages ReplicaSets, which maintain the desired pod count and automatically replace failed containers, satisfying the self-healing requirement. Its Horizontal Pod Autoscaler integration adjusts replica counts as load varies, delivering the scalability the stem demands. Bare pods or DaemonSets cannot reschedule failed replicas or scale dynamically in this manner.
- ✗
Pod
Why it's wrong here
A bare Pod runs a single container instance with no controller; if it fails or the node dies, nothing recreates it, and it cannot scale horizontally. It is tempting as the smallest deployable unit, but the scenario needs a Deployment, whose ReplicaSet maintains the desired replica count and replaces failed pods.
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.