A data engineer adds a data-quality constraint to a Lakeflow declarative pipeline table so that any record failing the constraint is discarded before it is written to the target, while the pipeline update keeps running. Which expectation clause achieves this?
Answer & explanation
Correct answer: C
WHY C: ON VIOLATION DROP ROW discards records failing the boolean EXPECT condition before writing and lets the update continue with the valid rows.
WHY NOT B: FAIL UPDATE stops the pipeline update on the first violation; it does not quietly discard rows and continue.
WHY NOT A: An EXPECT with no clause is the warn/retain default, which keeps invalid records (and records the violation metric) rather than dropping them.
WHY NOT D: DROP is not a valid constraint keyword, and the description also contradicts itself by both filtering and halting.
WHY NOT E: RESCUE ROW is not an expectation policy; _rescued_data belongs to Auto Loader schema handling, not pipeline expectations.