A pipeline copies newly digitised object records into a Lakehouse and then runs a notebook that reformats them for the public collections catalog. The archives team wants a Teams alert sent to the on-call engineer only if the copy step fails, and the reformatting notebook should never run against a failed copy. How should the activity dependencies be configured?
Select an answer to reveal the explanation.
Short Explanation
This is a fork in the road, and each path needs its own sign. Point the notebook's dependency at the copy activity's success, and point the Teams alert's dependency at the copy activity's failure — now each branch only fires when it's supposed to, and the two paths never cross.
Full Explanation
Fabric pipeline activities support dependency conditions such as Succeeded and Failed, which let a single upstream activity fan out into different downstream branches based on its outcome. Wiring the notebook to the copy activity's Succeeded condition and the Teams alert to its Failed condition creates exactly the two-path behavior described: good data flows forward, bad runs get flagged, and the two never happen on the same run. Leaving both downstream activities with no dependency means they both fire the moment the pipeline starts, regardless of whether the copy even finished, which would let the reformatting notebook process partial or missing data and would send a spurious alert on every successful night too. Wiring the notebook to run regardless of outcome reintroduces the exact risk the team is trying to avoid — reformatting against a failed or partial copy. Combining both pieces of business logic into one activity removes the ability to alert independently of the transformation step and makes failure handling far harder to reason about. The caveat: a Completed dependency condition fires on both success and failure, so it's not a substitute for the explicit Succeeded/Failed split here. Check it by forcing the copy activity to fail in a test run and confirming only the Teams alert activity executes.