Question 1
Fraud analytics requires historical merchant category values but a current-state MERGE overwrites every change. How should the team correct this issue while preserving the required data contract?
Explanation
Correct Answer
Configure AUTO CDC with stored_as_scd_type 2 and the appropriate historical tracking columns. This is the most directly relevant remediation because type 1 updates discard values needed for point-in-time historical analysis. A concrete acceptance check is: Two ordered updates create nonoverlapping valid historical versions of the same merchant. To reduce recurrence: Test history intervals and key uniqueness with late events.
Incorrect Answers
Mutable aggregate sources are not equivalent to a never-changing append event stream. The controlling issue in this question is that type 1 updates discard values needed for point-in-time historical analysis.
Append mode emits results when the engine can consider them final. Here the important technical distinction is that type 1 updates discard values needed for point-in-time historical analysis.
Output schema drift can break downstream writes despite plausible sample values. The reported failure instead depends on this fact: type 1 updates discard values needed for point-in-time historical analysis.