Question 560
A streaming pipeline uses append-only source events but assumes a deleted upstream Delta row will be replayed as a delete. What is the most direct underlying cause of the incident?
Explanation
Correct Answer
An append stream cannot infer historical deletes without explicit change events. This is the most directly relevant technical explanation because an append stream cannot infer historical deletes without explicit change events. A concrete acceptance check is: A controlled source deletion is reflected under the chosen CDC contract. To reduce recurrence: Record whether every source supports inserts, updates and deletes.
Incorrect Answers
Pipeline scheduling requires explicit data lineage to enforce upstream-before-downstream execution. The reported failure instead depends on this fact: an append stream cannot infer historical deletes without explicit change events.
Scheduling both branches without condition cannot enforce mutually exclusive remediation. That consideration does not remove the current constraint: an append stream cannot infer historical deletes without explicit change events.
Type 2 versioning on every changed attribute creates unnecessary historical rows. In this situation, an append stream cannot infer historical deletes without explicit change events.