Question 60
A streaming pipeline uses append-only source events but assumes a deleted upstream Delta row will be replayed as a delete. Which action should the data engineer take FIRST to resolve this issue?
Explanation
Correct Answer
Use a supported change-feed or CDC propagation design rather than append-only source semantics. This is the most directly relevant remediation 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
Repeated full or expensive view refresh can waste compute for new append records. For the observed behavior, an append stream cannot infer historical deletes without explicit change events.
At-least-once event transport can replay the same logical change. The controlling issue in this question is that an append stream cannot infer historical deletes without explicit change events.
Job orchestration does not make all independent writes one global ACID transaction. Here the important technical distinction is that an append stream cannot infer historical deletes without explicit change events.