CV0-004 Deployment Practice Question
A DevOps team wants to deploy a containerized application to a Kubernetes cluster with zero downtime. The team needs to gradually shift traffic from the old version to the new version, monitoring error rates and automatically rolling back if errors exceed a threshold. Which deployment strategy should the team implement?
⚠ Common exam trap
Test-takers frequently confuse rolling deployment with canary deployment — both are gradual, but only canary provides percentage-based traffic control with automated metric-driven rollback, which is what the question explicitly requires.
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
✓
Canary deployment
Canary deployment is correct because it introduces the new version to a small subset of users/traffic first, allowing the team to monitor error rates and metrics in production before progressively shifting more traffic. If error thresholds are breached, traffic can be instantly routed back to the stable version, achieving zero-downtime with automated rollback. This matches the requirement for gradual traffic shifting with monitoring and automatic rollback.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Blue/green deployment
Why it's wrong here
Blue/green runs two full environments and flips traffic at once, so it cannot gradually shift a percentage of requests while watching error rates. It suits instant cutover with fast environment-level rollback. The stem's incremental traffic weighting and threshold-triggered rollback require a canary deployment instead.
- ✗
Rolling deployment
Why it's wrong here
A rolling deployment replaces pods in batches but routes traffic to new pods as soon as they pass readiness probes; it offers no weighted traffic split or error-rate-driven automatic rollback. It suits routine updates where gradual pod replacement suffices. The stem's canary-style traffic shifting and threshold-based rollback demand a canary strategy.
- ✗
Recreate deployment
Why it's wrong here
Recreate tears down all existing pods before starting new ones, producing downtime, and provides no traffic splitting or automated rollback mechanism. It suits dev or batch workloads tolerating an outage window. The stem requires zero downtime plus monitored, reversible traffic shifting, which recreate cannot deliver.
- ✓
Canary deployment
Why this is correct
Canary deployment routes a small percentage of traffic to the new version first, then gradually shifts the remainder while monitoring error rates. If errors exceed the threshold, traffic reverts to the old version, delivering the gradual shift, monitoring and automatic rollback the team requires.
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.