Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Why IaC for pipelines**: Reproducibility, audit trail, environment parity. ARM (and Bicep) define ADF pipelines, datasets, linked services as JSON. **Architecture**: Use parameters for environment-specific values (dev/prod URLs, IR names). Reference Key Vault for secrets—never...
This hard-level Cloud/Tools question appears frequently in data engineering interviews at companies like Accenture. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (sql) will help you answer variations of this question confidently.
This is a senior-level question that tests architectural thinking. Lead with the high-level design, then drill into specifics. Discuss trade-offs explicitly - there is rarely one correct answer. Show awareness of scale, fault tolerance, and operational complexity.
Why IaC for pipelines: Reproducibility, audit trail, environment parity. ARM (and Bicep) define ADF pipelines, datasets, linked services as JSON. Architecture: Use parameters for environment-specific values (dev/prod URLs, IR names). Reference Key Vault for secrets—never inline. In CI/CD: az deployment group create with parameter file. Use Git integration in ADF for version control; ARM deploys infra, Git syncs pipeline definitions. Scalability: Modularize—separate templates for linked services, datasets, pipelines; use nested deployments. Cost: No direct cost for ARM; deployment time and pipeline runs cost money. Best practice: Separate templates per environment; use Bicep for cleaner syntax; run what-if before apply. Validate in dev, promote to prod via pipeline. Document parameter contracts; use managed identities for ADF→storage/SQL.
Pro-Move: 'We use Bicep modules with a parameter hierarchy—dev overrides only what changes; prod gets full validation before deploy.' Red Flag: Manual pipeline creation or copying JSON between environments—no audit, no rollback.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
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.