Question 600
A review of the governed data platform at Briarwood Property Group documents this problem: An ingestion pipeline writes directly into a consumer-facing table before schema and quality checks can reject invalid records. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
A seeded invalid record never reaches the consumer-facing result while valid rows are published. The observation provides evidence that the proposed fix (Stage or validate incoming records before the controlled write to the curated table.) addressed the reported issue (An ingestion pipeline writes directly into a consumer-facing table before schema and quality checks can reject invalid records.) for Briarwood Property Group and its tenant portals and property records. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
The pipeline dependency graph shows the correct relationship and downstream results include the expected upstream records. This is suitable evidence for another condition (A declarative pipeline writes an intermediate dataset and the downstream query assumes it is available before the dataflow dependency resolves.) after a different response (Declare the downstream table query in terms of supported upstream dataset references.). For Briarwood Property Group, it does not prove the required result: A seeded invalid record never reaches the consumer-facing result while valid rows are published.
A staging execution writes only to staging objects and a production write requires the appropriate deployment context. This is suitable evidence for another condition (A data pipeline hard-codes a production catalog name in every notebook and developers accidentally write tests into production.) after a different response (Parameterize environment-specific object names and validate the resolved target at deployment time.). For Briarwood Property Group, it does not prove the required result: A seeded invalid record never reaches the consumer-facing result while valid rows are published.
A deliberately failing validation prevents the publish task and generates a visible error status. This is suitable evidence for another condition (A pipeline continues to publish an incomplete curated dataset after a mandatory upstream validation task fails.) after a different response (Use explicit task dependency and failure semantics to block publication when required checks fail.). For Briarwood Property Group, it does not prove the required result: A seeded invalid record never reaches the consumer-facing result while valid rows are published.