# An ImageUpdateAutomation sets spec.policyChangeDelay: 2m, and ImagePolicy changes arrive at minutes 0, 1 and 3. What gets committed?

Flux CD, Hard (Expert), Integration. https://k8wiz.com/uquiz/an-imageupdateautomation-sets-specpolicychangedelay-2m-and-imagepolicy-changes-arrive-at-minutes-0-1-and-3-what-gets-committed

- A. It restarts the 2m wait on each change and commits all three at the end
- B. It commits the first two together at 2m and the third in a later run
- C. It commits each change separately, at least 2m after the previous commit
- D. It waits 2m after the last change, then commits only the newest tag

**Answer:** It commits the first two together at 2m and the third in a later run

**Explanation:** policyChangeDelay defers the run after an ImagePolicy change so that updates arriving within the delay land in one commit. The delay starts at the first change and later changes don't extend it, so the change at minute 3 misses that window and goes into a following run.