Question 590
Evermere Health processes care team access and regulated data handling with controlled access to customer records. The investigation finds: A downstream data mart is triggered by an upstream task but the mart query reads stale snapshots because pipeline refresh order is not defined. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
The mart's test timestamp and record counts match the completed upstream refresh checkpoint. The observation provides evidence that the proposed fix (Set explicit upstream refresh and transformation sequencing before publishing the mart.) addressed the reported issue (A downstream data mart is triggered by an upstream task but the mart query reads stale snapshots because pipeline refresh order is not defined.) for Evermere Health and its care team access and regulated data handling. 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 Evermere Health, it does not prove the required result: The mart's test timestamp and record counts match the completed upstream refresh checkpoint.
An unattended run executes the notebook tasks in the required sequence and records each result. This is suitable evidence for another condition (A notebook pipeline runs its steps manually in a fixed order with no reproducible task sequencing when the operator is absent.) after a different response (Define reusable notebook tasks in a Lakeflow Job with explicit predecessor constraints.). For Evermere Health, it does not prove the required result: The mart's test timestamp and record counts match the completed upstream refresh checkpoint.
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 Evermere Health, it does not prove the required result: The mart's test timestamp and record counts match the completed upstream refresh checkpoint.