Question 560
A review of the governed data platform at Orion Network Services documents this problem: A pipeline continues to publish an incomplete curated dataset after a mandatory upstream validation task fails. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
A deliberately failing validation prevents the publish task and generates a visible error status. The observation provides evidence that the proposed fix (Use explicit task dependency and failure semantics to block publication when required checks fail.) addressed the reported issue (A pipeline continues to publish an incomplete curated dataset after a mandatory upstream validation task fails.) for Orion Network Services and its subscriber applications and remote operations. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
A controlled run starts the aggregation only after the raw normalization task completes successfully. This is suitable evidence for another condition (A curated finance table starts aggregating before its upstream raw-event normalization task finishes and reports partial daily totals.) after a different response (Express the correct upstream dependency sequence in the pipeline task graph.). For Orion Network Services, it does not prove the required result: A deliberately failing validation prevents the publish task and generates a visible error status.
A simulated transient failure is retried within policy and either completes or generates an actionable terminal failure. This is suitable evidence for another condition (An ETL task fails intermittently on recoverable network timeouts but the job has no retry or timeout handling.) after a different response (Add bounded retries, timeout limits, and safe failure reporting appropriate to the operation.). For Orion Network Services, it does not prove the required result: A deliberately failing validation prevents the publish task and generates a visible error status.
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 Orion Network Services, it does not prove the required result: A deliberately failing validation prevents the publish task and generates a visible error status.