A Deployment's rolling update strategy allows updating Pods gradually. What two fields control this behavior?

Correct answer: maxSurge and maxUnavailable

Option A is correct: a Deployment's rolling update strategy is governed by maxSurge, which sets how many extra Pods can exist above the desired count during an update, and maxUnavailable, which sets how many Pods can be unavailable at once, together controlling the pace and safety of the rollout. Option B is incorrect because replicas sets the desired Pod count and strategy selects the update type, but neither directly controls the rolling update pacing. Option C is incorrect because image and tag specify what container to run, not how the rollout proceeds. Option D is incorrect because selector identifies which Pods belong to the Deployment and template defines the Pod spec, but neither governs rolling update speed.