Create and configure deployment pipelines with deployment rules to promote content across development, test, and production stages.

An analytics engineer is configuring a Fabric deployment pipeline that promotes a "semantic model" and a "Dataflows Gen2" item through development, test, and production stages. When content reaches the production stage, the model must connect to the production "Warehouse" instead of the development one, and a dataflow parameter named BatchSize must be forced to its full production value. Which TWO deployment rule types should the engineer create on the production stage to meet these needs? Select TWO.

• AA data source rule on the production stage that rewrites the model's connection so it reads from the production "Warehouse" on every deployment into production.check_circle Correct
• BA parameter rule on the production stage that sets BatchSize to its required production value whenever the dataflow is deployed into the production stage.check_circle Correct
• CA Git integration commit rule on the production stage that serialises the model definition to the connected branch each time content is deployed into production.
• DA sensitivity label rule on the production stage that reapplies the model's confidential classification to the dataflow each time content is deployed into production.

Why A is correct: Correct because a data source rule rebinds an item's source connection as it lands in the stage holding the rule, so the model points at the production "Warehouse" without a manual edit after promotion.

Why B is correct: Correct because a parameter rule overrides a named parameter to a fixed value on deployment into the stage that holds it, so BatchSize is pinned to its production figure regardless of the development setting.

Why C is wrong: Tempting because Git and pipelines are both ALM tools, but no commit rule exists inside deployment pipelines and Git integration is a separate feature, so this does not rebind a source or set a parameter.

Why D is wrong: Plausible because labels travel with governed items, but deployment rules cover data sources and parameters, not sensitivity classification, so no such label rule type governs a promotion.