Courseiva
Deployment →mediumMultiple Choice

CV0-004 Deployment Practice Question

An organization wants to deploy a new microservice to a Kubernetes cluster with zero downtime. The deployment should update pods gradually by replacing old pods with new ones, and if the new pods fail health checks, the rollout should stop. Which Kubernetes deployment strategy meets these requirements?

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

✓

Rolling update

A rolling update strategy in Kubernetes replaces pods incrementally and can be configured to pause on failed health checks.

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

    Why it's wrong here

    Canary shifts a percentage of live traffic to the new version, typically using service mesh or ingress weighting, rather than replacing pods gradually within a single Deployment. It suits controlled exposure of a release to a subset of users, not the rolling update described.

  • ✗

    Recreate

    Why it's wrong here

    Recreate terminates every existing pod before starting new ones, causing an outage that violates the zero-downtime requirement. It would be acceptable for non-production workloads where brief unavailability is tolerable, but it cannot stop a rollout on failing health checks while serving traffic.

  • ✓

    Rolling update

    Why this is correct

    A rolling update replaces pods incrementally, keeping the service available throughout. Its maxUnavailable and maxSurge settings control the gradual replacement, and the rollout halts automatically when new pods fail readiness probes, satisfying the zero-downtime and health-check constraints.

  • ✗

    Blue/green

    Why it's wrong here

    Blue/green runs two full environments and switches all traffic at once, so a failing new version is caught only after the cutover rather than by halting a gradual pod-by-pod replacement. It suits instant rollback between stable releases, not incremental health-checked rollouts.

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 →

How Courseiva writes practice questions · Editorial policy

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.