Course contents

The Analytics Engineer’s Field GuideAirflow 3: running it for a teamChallenge: Airflow 3

Challenge: Airflow 3

Challenge: Airflow 3

Three situations from running dbt on an Airflow that several teams share.

Challenge questions

  1. The finance team merges a new DAG into the pre_prod branch of its own project repo. In the lesson's core-and-submodules setup, which Airflow can end up running it?

    1. Neither, until finance gets its own Astronomer Deployment
    2. Both, since the core holds one combined view of all dags
    3. The pro Airflow, since pro pulls every branch's dags/
    4. Only the pre_prod Airflow, once the core's pre_prod deploys
  2. A push to the core repo changes one model under dbt/ and nothing else. The pipeline runs astro deploy $DEPLOYMENT_ID --dags and goes green, but tomorrow's Cosmos run still uses the old SQL. What should it have run?

    1. astro dbt deploy $DEPLOYMENT_ID
    2. astro deploy $DEPLOYMENT_ID --dags --force
    3. astro dev restart
    4. astro deployment wake-up $DEPLOYMENT_ID
  3. The CI check validates DAG ids with NAME = re.compile(r"^[a-z0-9]+__[a-z0-9_]+__[a-z]+$"). Which of these DAG ids passes it?

    1. finance__revenue__daily_v2
    2. finance_revenue_daily
    3. finance__revenue_eu__daily
    4. Finance__revenue__daily