CV0-004 Deployment Practice Question
A DevOps team is deploying a new version of a microservice to a Kubernetes cluster on AWS. They want to minimize the risk of introducing errors by gradually shifting traffic to the new version while monitoring key metrics. They also need the ability to automatically roll back if the new version does not perform well. Which deployment strategy should they use?
⚠ Common exam trap
Watch out — candidates often confuse rolling updates with canary deployments, as both are gradual, but only canary provides controlled traffic shifting and automated rollback based on custom metrics.
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 designed to reduce risk by gradually shifting a small percentage of traffic to the new version, monitoring its performance, and then progressively increasing traffic if metrics are satisfactory. It supports automated rollback if anomalies are detected. Recreate causes downtime, rolling update lacks fine-grained traffic control and automated rollback based on metrics, and blue/green switches all traffic at once, which is riskier.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Canary deployment
Why this is correct
Canary deployment involves releasing the new version to a small subset of users or traffic, then gradually increasing the traffic while monitoring metrics. If issues are detected, the deployment can be automatically rolled back. This strategy minimizes risk by limiting exposure and allows for data-driven decisions based on real-time performance. It aligns perfectly with the requirements for gradual traffic shifting and automated rollback.
- ✗
Recreate deployment
Why it's wrong here
The recreate strategy terminates all existing pods before creating new ones, causing downtime. It does not support gradual traffic shifting or automated rollback based on metrics. This strategy is unsuitable for minimizing risk because it introduces a period of unavailability and does not allow for monitoring the new version under live traffic before full cutover.
- ✗
Rolling update
Why it's wrong here
A rolling update gradually replaces old pods with new ones, but it does not provide fine-grained control over traffic shifting or the ability to automatically roll back based on custom metrics. While it reduces downtime, it lacks the canary analysis and automated rollback features required to minimize risk when introducing a new version. It also does not allow for easy A/B testing.
- ✗
Blue/green deployment
Why it's wrong here
Blue/green deployment involves running two identical environments and switching traffic from the old to the new all at once. While it allows for quick rollback by switching back, it does not support gradual traffic shifting. This makes it riskier because the new version receives 100% of traffic immediately, and any issues affect all users. It also requires double the resources during deployment.
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.