After a pipeline item is promoted from the Test stage to the Production stage of a deployment pipeline, it should point to Production's own Lakehouse rather than the one used in Test, without anyone manually editing the connection after every deployment. What should be configured?
Select an answer to reveal the explanation.
Short Explanation
A deployment rule is like a label-swapping machine on the conveyor belt -- every time an item rolls into the Production stage, the rule automatically points it at Production's own resources instead of carrying Test's settings along for the ride.
Full Explanation
A deployment rule lets a deployment pipeline automatically rebind stage-specific configuration, such as which Lakehouse a pipeline item connects to, every time content is deployed into that stage -- so Production always ends up pointed at its own Lakehouse without manual edits after each promotion. A custom Spark pool sized to match Production's capacity addresses Spark compute sizing, not which data source an item connects to after deployment. Rebuilding a database project applies to warehouse schema source control, not to rebinding a pipeline item's data-source connection between stages. Reassigning the domain changes governance grouping and has no effect on an item's runtime connection settings. A scope note: deployment rules must be configured once per target stage and per parameter that needs to differ; they don't retroactively fix items already deployed before the rule existed. Confirm the rule works by deploying again and checking the promoted pipeline item's connection now points at Production's Lakehouse rather than Test's.