easyMultiple Choice
CAS-004 Practice Question: A development team wants to deploy a…
A development team wants to deploy a microservices application using containers. They need a solution to automate the deployment, scaling, and management of the containers across a cluster. Which technology is most suitable?
⚠ Common exam trap
Candidates often confuse CI/CD tools (Jenkins) or single-host orchestration (Docker Compose) with full cluster orchestration, or assuming that virtualization platforms like vSphere provide native container orchestration; candidates must recognize that Kubernetes (often with Helm) is the dedicated solution for automated deployment, scaling, and management across a cluster.
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
✓
Kubernetes with Helm charts.
Kubernetes is the de facto standard for container orchestration, providing automated deployment, scaling, and management of containerized applications across a cluster. Helm charts add package management, templating, and release versioning, which are essential for managing complex microservices deployments. Together, they directly address the requirement to automate deployment, scaling, and management across a cluster.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
VMware vSphere with container support.
Why it's wrong here
vSphere with container support runs containers inside VMs on ESXi hosts, providing no native pod scheduling, replica reconciliation or cluster-wide autoscaling. It appeals when consolidating existing virtualised workloads, yet the stem requires orchestrating containers across a cluster, which vSphere does not do.
- ✗
Jenkins with Docker plugins.
Why it's wrong here
Jenkins orchestrates CI/CD pipelines; its Docker plugins build and push images, not schedule pods across a cluster. Tempting because it automates container builds and deployments, but it lacks a scheduler, desired-state reconciliation and self-healing, so it cannot manage cluster scaling.
- ✗
Docker Compose with manual scaling.
Why it's wrong here
Docker Compose defines and runs multi-container applications on a single host, and its scaling is manual, so it cannot automate scheduling or management across a cluster. It is tempting for local development, but cluster orchestration requires Kubernetes, which provides automated deployment, scaling and self-healing.
- ✓
Kubernetes with Helm charts.
Why this is correct
Kubernetes provides the cluster-wide orchestration layer for scheduling, scaling and self-healing containers, while Helm charts package and version the microservices' manifests for repeatable automated deployment. Together they meet the automation, scaling and management requirements across the cluster.
Go deeper
Related to this question
About these practice questions
This CAS-005 question is part of Courseiva's 973-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 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 CAS-005 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 CAS-005 exam.