Set spec.strategy.rollingUpdate.maxSurge=1 and maxUnavailable=0
Why wrong: This allows a surge of new pods before terminating old ones, but does not guarantee that new pods are ready before old pods are terminated, because maxUnavailable=0 means old pods are not terminated until new pods are ready, but with maxSurge=1, new pods can start, but the old pods are only terminated when new ones are ready; however, this is actually correct for zero-downtime? Wait, the question states old pods terminated before new pods ready, so the issue is that maxUnavailable is too high. Setting maxUnavailable=0 ensures no old pods are terminated until new ones are ready. But the correct answer is B? Let's re-evaluate. The actual issue: old pods terminated before new pods ready. With maxSurge=0, no extra pods can be created, so to update, you must terminate old pods first, causing downtime. With maxSurge=1 and maxUnavailable=0, you create a new pod first, then terminate old pod after new pod is ready. That would prevent the described issue. So why is B correct? B sets maxSurge=0 and maxUnavailable=1, which means you terminate one old pod first (since maxUnavailable=1), then create a new pod. That could cause downtime if the new pod takes time to become ready. So B is actually flawed. The correct answer should be maxSurge=1, maxUnavailable=0. But the question says 'Which configuration change should they make to the Deployment to prevent this?' and the options: A: maxSurge=1, maxUnavailable=0; B: maxSurge=0, maxUnavailable=1; C: set minReadySeconds to 0; D: add liveness probe. So A is correct. I'll fix the response accordingly.