# Three Airflow DAGs all hit the same Snowflake XL warehouse: a customer-facing daily dashboard DAG, a

Canonical URL: <https://datadriven.io/problems/three-airflow-dags-all-hit-the-same-snowflake-xl-warehouse-012d2f82>

Domain: Pipeline Design · Difficulty: medium

## Problem

Three Airflow DAGs all hit the same Snowflake XL warehouse: a customer-facing daily dashboard DAG, a 365-day backfill DAG, and an experimental ML feature build DAG. On Mondays they collide and the daily dashboard misses its 6am SLA. Apply the pools-and-priority framing this section just taught and add structural isolation: split into two orchestrators (one running the customer-facing daily dashboard at high priority on a dedicated path, another running the backfill and ML experimental DAGs at lower priority on isolated compute). The two orchestration nodes together with an observability_tool monitoring the customer-facing path's SLA replace the implicit shared-pool contention with explicit priority isolation that the canvas can model.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/three-airflow-dags-all-hit-the-same-snowflake-xl-warehouse-012d2f82)
- [System Design Interview Questions](https://datadriven.io/data-engineering-system-design)
- [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep)
- [Daily Challenge](https://datadriven.io/daily)

---

Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.