CV0-004 Operations and Support Practice Question
A cloud operations team runs a Kubernetes cluster on Google Kubernetes Engine (GKE). They need to ensure that a critical payment microservice is automatically restarted if its container process fails, and that a new Pod is created if the node hosting it becomes unhealthy. Which Kubernetes object should they configure to meet these requirements?
⚠ Common exam trap
The trap here is assuming that a standalone Pod or DaemonSet provides the same self-healing and rescheduling guarantees as a Deployment-managed ReplicaSet.
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 ReplicaSet
A Deployment with a ReplicaSet is the correct Kubernetes controller for stateless, long-running microservices. The ReplicaSet ensures the desired number of Pod replicas are running, and the kubelet restarts failed containers. If a node becomes unhealthy, the ReplicaSet controller creates replacement Pods on healthy nodes. This provides both container-level and node-level self-healing, which the payment microservice requires.
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 standalone Pod
Why it's wrong here
A standalone Pod is not managed by a controller. If the node hosting it becomes unhealthy, the Pod is not rescheduled automatically. While the kubelet may restart a failed container within the Pod, the Pod itself has no self-healing mechanism for node failures. This makes it unsuitable for a critical payment microservice that requires high availability across node outages.
- ✗
A DaemonSet
Why it's wrong here
A DaemonSet ensures that a copy of a Pod runs on every node (or a subset of nodes) in the cluster. It is typically used for node-level agents like log collectors or monitoring daemons. While it does restart failed containers, it does not maintain a fixed replica count for a microservice and will not create a replacement Pod on a different node if one node fails, so it fails the scenario.
- ✓
A Deployment with a ReplicaSet
Why this is correct
A Deployment manages a ReplicaSet, which ensures the desired number of Pod replicas are running. If a container process fails, the kubelet restarts it according to the Pod's restartPolicy (default Always). If a node becomes unhealthy, the ReplicaSet controller creates replacement Pods on healthy nodes. This directly satisfies both automatic container restart and Pod rescheduling requirements for the payment microservice.
- ✗
A CronJob
Why it's wrong here
A CronJob creates Jobs on a scheduled basis, such as running a batch task every hour. It is designed for periodic, run-to-completion workloads, not for long-running microservices. It does not maintain a persistent replica count or provide continuous restart and rescheduling behavior for a payment service that must always be available, so it does not meet the stated requirements.
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.