Chaining notebooks and pipelines together with parameters and dynamic expressions

Microsoft Fabric supports orchestration through pipelines that can invoke notebooks, other pipelines, and dataflows, allowing you to build modular, reusable analytics workflows. Parameters and dynamic expressions let you pass values between activities and adapt behavior at runtime, similar to Azure Data Factory patterns. Understanding how notebooks expose parameters and how pipelines consume outputs is essential for building maintainable orchestration solutions.

Must-know

• Notebook cells can be tagged as 'parameters' cells, which defines the default values that a pipeline's Notebook activity can override at runtime via the Base parameters section.
• The Notebook activity in a pipeline uses the mssparkutils.notebook.exit() function's return value to pass output data back to the pipeline for use in subsequent activities.
• Pipeline expressions use the same dynamic content language as Azure Data Factory (e.g., @pipeline().parameters.paramName, @activity('ActivityName').output), enabling data-driven behavior without hardcoding values.
• The ForEach activity enables iterative orchestration, such as running a parameterized notebook once per item in an array (e.g., once per table or file), supporting parallel or sequential execution.
• The Invoke Pipeline activity allows one pipeline to call another and pass parameters, enabling hierarchical, reusable orchestration patterns rather than duplicating logic across pipelines.
• Pipeline parameters must be defined at design time (name and type) before they can be referenced in expressions or set via triggers, and they are immutable during a single pipeline run (use variables if you need to mutate values mid-run).

Coverage checked against the published exam guide on Aug 11, 2026.

These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.