Question 490
The lakehouse operations report for Horizon Energy Services describes this issue: An ingestion pipeline accepts negative invoice amounts for a source whose contract requires nonnegative values. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
The negative test record is flagged or rejected while valid invoices pass the rule. The observation provides evidence that the proposed fix (Enforce a supported range or quality expectation on the invoice amount and specify invalid-row handling.) addressed the reported issue (An ingestion pipeline accepts negative invoice amounts for a source whose contract requires nonnegative values.) for Horizon Energy Services and its remote field-worker sign-ins and operations. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
An intentionally invalid record causes a visible pipeline failure and is not silently discarded. This is suitable evidence for another condition (An operations team wants every incoming bad record to stop the whole pipeline but has configured a drop expectation that silently continues.) after a different response (Use an expectation failure mode aligned with the stated fail-fast quality contract.). For Horizon Energy Services, it does not prove the required result: The negative test record is flagged or rejected while valid invoices pass the rule.
Valid events continue loading and rejected-event counts appear in a reviewable quality report. This is suitable evidence for another condition (A high-volume feed can tolerate a few rejected events but an aggressive fail expectation stops the entire ingestion process.) after a different response (Use an approved drop or quarantine policy with monitored quality counts for the tolerance requirement.). For Horizon Energy Services, it does not prove the required result: The negative test record is flagged or rejected while valid invoices pass the rule.
A seeded bad record is handled as configured and expectation metrics reflect its occurrence. This is suitable evidence for another condition (A Lakeflow declarative pipeline counts every invalid row as valid because it has no data-quality expectation at its ingestion boundary.) after a different response (Define a suitable expectation expression and the chosen warn drop or fail behavior.). For Horizon Energy Services, it does not prove the required result: The negative test record is flagged or rejected while valid invoices pass the rule.