SELF-CHECK
The first run loads 100 unique enrollments. The identical file arrives again. What result should an idempotent load preserve?

REFERENCE REASONING
100 unique enrollments, with the second run recorded as a rerun or no-op. The exact merge strategy depends on the documented correction policy.

This is a reasoning reference for the supplied fictional case, not an executed app or tested cloud deployment. Alternative approaches are valid when supported by stated assumptions and evidence.
