Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Architectural process: Linked Services (connections) → Datasets (data shapes) → Pipelines (orchestration) → Activities (Copy, Transform). Triggers run pipelines; IR executes (Azure, SHIR, SSIS). Use cases: Lift-and-shift ETL, Synapse/Blob ingestion, SaaS API ingestion, lake...
Architectural process: Linked Services (connections) → Datasets (data shapes) → Pipelines (orchestration) → Activities (Copy, Transform). Triggers run pipelines; IR executes (Azure, SHIR, SSIS). Use cases: Lift-and-shift ETL, Synapse/Blob ingestion, SaaS API ingestion, lake orchestration. Example: Daily trigger → Copy SQL Server (SHIR) to ADLS → Data Flow cleanse → Copy to Synapse. Scalability: Parameterize for reuse; stage large files. Cost: Activity runs, IR runtime. Best practice: Parameters; ARM for IaC; Alerts + Logic Apps for failures.
Red Flag: Hardcoded connection strings or env-specific values. Pro-Move: 'We parameterize all config; ARM templates per env; Logic App on failure for PagerDuty—deploys are reproducible.'
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.