Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Architectural logic: Global parameters = factory-level; accessible to all pipelines. Local (pipeline) parameters = per-pipeline; passed at runtime or from triggers. Use global for env, base URL; local for LoadDate, table list. Reference: @pipeline().globalParameters.Environment,...
Architectural logic: Global parameters = factory-level; accessible to all pipelines. Local (pipeline) parameters = per-pipeline; passed at runtime or from triggers. Use global for env, base URL; local for LoadDate, table list. Reference: @pipeline().globalParameters.Environment, @pipeline().parameters.LoadDate. Why: Centralize cross-pipeline config; pipeline-specific for runtime. Best practice: Global for env; pipeline params from triggers; secrets in Key Vault.
Red Flag: Hardcoding env in every pipeline. Pro-Move: 'We use global Environment=prod; pipeline params from trigger—one change updates all pipelines.'
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.