Fabric Deployment Pipeline Configuration for Dataflow Gen2

The question requires deploying a Dataflow Gen2 item from a development workspace (Workspace1) to a production workspace (Workspace2) using a deployment pipeline, ensuring the data source points to the correct production storage account.

Data Source Rule: This is the primary mechanism in Fabric deployment pipelines for remapping connections. When you create a data source rule, you map the connection in the source environment (e.g., Dev Storage Account) to the corresponding connection in the target environment (e.g., Prod Storage Account). This automatically updates the gateway or direct lake connection reference during deployment. Without this, the deployed item would still point to the development storage, which is incorrect for production.

Parameter Rule: While parameter rules are useful for changing specific values within Power Query (like file paths or table names), they are secondary to the connection itself. However, in many scenarios involving blob storage, simply remapping the container connection might not be enough if the path structure differs significantly or if specific parameters need overriding. More importantly, the question asks what you need to do to ensure the data source references the correct location. The most complete and robust approach described in Microsoft documentation for handling environment-specific configurations in deployment pipelines often involves both: using a data source rule to handle the connection identity and parameter rules to handle any variable parts of the query logic that differ between environments. However, looking at the options, Option C suggests creating both. Is a parameter rule strictly necessary? Often, yes, if the CSV path or other query parameters change. But even if only the connection changes, the 'best practice' answer for ensuring full correctness in complex deployments usually includes both mechanisms to cover all bases of configuration drift. Let's look closer. If I only use a data source rule, the connection changes. If the path inside the blob storage also changes (which is common), I need a parameter rule. The prompt implies a general need to ensure correct references. The most comprehensive solution provided in the options is C. Furthermore, comments support C, noting that data source rules replace connections and parameter rules override internal values like paths.

Why A is insufficient: It only handles the connection, potentially missing path variations. Why B is insufficient: Parameters alone don't change the underlying connection object reference managed by the pipeline. Why D is manual and violates automation principles. Therefore, creating both ensures the connection is mapped and any internal query variables are adjusted.