Which two activities support parameterization in the data pipeline UI?

Which two activities support parameterization in the data pipeline UI?

• A. Notebooks & SQL stored procedures
• B. Dataflows & Python scripts
• C. SQL queries & Dataflows
• D. PowerShell & Notebooks

Answer: (A)

Parameterization in the data pipeline UI lets you inject runtime values so the same pipeline can run with different inputs without changing the code. Notebooks support parameters through notebook widgets or parameterized cells, and the pipeline can pass concrete values into those parameters when the notebook activity executes. SQL stored procedures naturally accept input parameters, and the pipeline can supply those values from its own parameters, letting the stored procedure run with different inputs each time. This combination—notebooks with parameter inputs and SQL stored procedures with input parameters—is the most direct way to enable dynamic behavior in a pipeline, which is why they’re the best fit for parameterization. While other activities can sometimes be configured with dynamic content, they don’t inherently provide the same straightforward, built-in parameterization pathway in the UI for routine runtime variation.

Parameterization in the data pipeline UI lets you inject runtime values so the same pipeline can run with different inputs without changing the code. Notebooks support parameters through notebook widgets or parameterized cells, and the pipeline can pass concrete values into those parameters when the notebook activity executes. SQL stored procedures naturally accept input parameters, and the pipeline can supply those values from its own parameters, letting the stored procedure run with different inputs each time.

This combination—notebooks with parameter inputs and SQL stored procedures with input parameters—is the most direct way to enable dynamic behavior in a pipeline, which is why they’re the best fit for parameterization. While other activities can sometimes be configured with dynamic content, they don’t inherently provide the same straightforward, built-in parameterization pathway in the UI for routine runtime variation.