Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Architectural Logic:** ADF triggers orchestrate pipeline runs; tumbling window triggers partition time into fixed, non-overlapping intervals (e.g., 15min, 1hr). **Why tumbling over schedule:** Idempotency—each window processes mutually exclusive data, enabling safe retries and...
This medium-level SQL question appears frequently in data engineering interviews at companies like Accenture, Yash Technologies. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (partition, window) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Architectural Logic: ADF triggers orchestrate pipeline runs; tumbling window triggers partition time into fixed, non-overlapping intervals (e.g., 15min, 1hr). Why tumbling over schedule: Idempotency—each window processes mutually exclusive data, enabling safe retries and backfills. Scalability: Max concurrency controls parallel window execution; oversubscription can exhaust DTU/IR capacity. Cost: Higher concurrency = more runs = higher IR cost; tune window size vs. SLA. Trade-offs: Large windows reduce trigger overhead but increase latency; small windows improve granularity but multiply orchestration cost. Other triggers: schedule (cron), storage events (blob created), manual. Production pattern: Use dependency conditions for chained pipelines; parameterize paths for environment promotion.
RED FLAG: Saying 'tumbling windows run at fixed intervals' without discussing idempotency or max concurrency. PRO MOVE: 'We set max concurrency to 2 with 1hr windows to cap cost while meeting our 4hr SLA; each window is idempotent so backfills are safe.'
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 SQL interview questions, reported at 2 companies. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.