Question 960
A query applies LAG across every transaction, mixing the previous purchase of unrelated customers. Which continuing control should the team adopt after recovery?
Explanation
Correct Answer
Test multi-customer interleaving and duplicate timestamps. This is the most directly relevant preventive control because window functions do not infer entity boundaries unless a partition is specified. A concrete acceptance check is: A customer fixture references only that customer's previous order. To reduce recurrence: Test multi-customer interleaving and duplicate timestamps.
Incorrect Answers
A successful commit can be replayed by an at-least-once orchestration layer. The controlling issue in this question is that window functions do not infer entity boundaries unless a partition is specified.
Replaying unchanged invalid input repeats the same deterministic rejection. Here the important technical distinction is that window functions do not infer entity boundaries unless a partition is specified.
Generic dropDuplicates does not implement latest-event business semantics. The reported failure instead depends on this fact: window functions do not infer entity boundaries unless a partition is specified.