A batch invoice worker can tolerate brief downtime but must never run old and new code together. Which Deployment strategy type fits that downtime tolerance and mutual-exclusion need?
Select an answer to reveal the explanation.
Short Explanation
Some upgrades need a clear stage swap—lights out on the old cast, then the new cast enters. Recreate tears down the old Pods first so versions never overlap, accepting a short downtime window RollingUpdate tries to avoid.
Full Explanation
Deployment .spec.strategy.type can be RollingUpdate or Recreate. Recreate scales the old ReplicaSet to zero before creating Pods for the new template, so old and new versions do not run concurrently; the tradeoff is downtime. RollingUpdate gradually replaces Pods and typically allows overlap controlled by maxSurge/maxUnavailable. DaemonSets and Jobs are different workload kinds and do not replace this Deployment strategy choice.