A city CMS Deployment must bump its container image while the citizen portal keeps answering requests. Which update behavior should the platform team rely on?
Select an answer to reveal the explanation.
Short Explanation
Think of swapping engines on a train while it is still moving—you change cars one at a time so passengers never all stop. RollingUpdate does that for Pods: new replicas come up as old ones leave, so the CMS keeps serving.
Full Explanation
A Deployment with strategy type RollingUpdate replaces Pods gradually according to maxUnavailable and maxSurge, so some ready Pods remain to serve traffic during an image change. Recreating the whole Deployment or mutating naked Pods is not the supported high-availability update path. Service type changes do not implement a rolling image upgrade.