Which Kubernetes-native deployment strategy supports zero-downtime updates of a workload?

The correct answer is D. RollingUpdate. RollingUpdate (D) is Kubernetes' built-in deployment strategy that gradually replaces old pods with new ones, keeping some instances of the application running at all times - achieving zero downtime. Recreate (B) terminates all existing pods before creating new ones, causing…

Submitted by haruto_sh· May 4, 2026Kubernetes Fundamentals

Question

Options

ACanary
BRecreate
CBlueGreen
DRollingUpdate

How the community answered

(42 responses)

A
5% (2)
B
2% (1)
D
93% (39)

Explanation

RollingUpdate (D) is Kubernetes' built-in deployment strategy that gradually replaces old pods with new ones, keeping some instances of the application running at all times - achieving zero downtime. Recreate (B) terminates all existing pods before creating new ones, causing downtime. Canary (A) and BlueGreen (C) are valid deployment patterns but are not native Kubernetes Deployment strategies - they require additional tooling or manual configuration to implement in Kubernetes.

Topics

#Kubernetes Deployments#Deployment Strategies#Rolling Update#Zero-downtime

Community Discussion

No community discussion yet for this question.

Full KCNA Practice