task_a >> task_b; [task_a, task_b] >> task_c with task_c's trigger_rule=TriggerRule.ALL_DONE. **Why**: C runs after both A and B complete regardless of success/failure. ALL_DONE = run when all upstream finished (success or fail). **Architecture**: A→B (B only on A success by default); A,B→C (C always). Use on_failure_callback for alerts....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Dunnhumby. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.