DAG versioning strategies in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding DAG Versioning Purpose

Why is versioning DAGs important in Apache Airflow?

A To allow multiple users to edit the same DAG simultaneously without conflicts

B To track changes and ensure reproducibility of workflows over time

C To automatically delete old DAGs from the Airflow UI

D To increase the speed of DAG execution by caching versions

💡 Hint

Think about why keeping track of changes in workflows matters in real life.

Versioning DAGs helps track changes and ensures workflows can be reproduced exactly as before, which is critical for reliability and debugging.

💻 Command Output

intermediate

Effect of Changing DAG ID on Airflow UI

What happens in the Airflow UI when you change the dag_id of a DAG file and deploy it?

Apache Airflow

from airflow import DAG
from datetime import datetime

dag = DAG(dag_id='my_dag_v2', start_date=datetime(2024, 1, 1))

A The UI shows a new DAG with ID 'my_dag_v2' and the old DAG remains unchanged

B The UI updates the existing DAG to the new ID automatically

C The UI merges the old and new DAGs into one entry

D The UI deletes the old DAG and shows only the new one

💡 Hint

Consider how Airflow identifies DAGs uniquely.

Changing the dag_id creates a new DAG entry in the UI; the old DAG remains unless manually removed.

🔀 Workflow

advanced

Implementing DAG Versioning with Git Branches

You want to maintain multiple versions of a DAG in production using Git branches. Which workflow correctly supports this?

A Use tags in Git to mark versions but deploy only the main branch to Airflow

B Keep all DAG versions in one branch and rename <code>dag_id</code> dynamically at runtime

C Store all DAG versions in one file and comment out unused versions before deployment

D Use separate Git branches for each DAG version and deploy the branch matching the desired version to Airflow

💡 Hint

Think about how Git branches isolate code changes.

Using separate branches allows deploying specific DAG versions independently, avoiding conflicts and confusion.

❓ Troubleshoot

advanced

Troubleshooting DAG Conflicts from Multiple Versions

You deployed two DAG versions with the same dag_id but different code. What problem will Airflow likely show?

A Airflow will show only one DAG but with unpredictable behavior from mixed code

B Airflow will show both DAGs separately without conflict

C Airflow will throw a syntax error on startup

D Airflow will automatically merge the DAGs into one stable version

💡 Hint

Consider how Airflow identifies DAGs uniquely by dag_id.

Airflow identifies DAGs by dag_id. Deploying multiple versions with the same ID causes one DAG to appear, but code conflicts cause unpredictable runs.

✅ Best Practice

expert

Best Practice for DAG Versioning in Production

Which strategy is best to safely version DAGs in a production Airflow environment?

A Deploy all versions with the same <code>dag_id</code> and rely on Airflow to pick the latest

B Keep all versions in the same DAG file and toggle active version with environment variables

C Use semantic versioning in <code>dag_id</code> and deploy only one version active at a time

D Use random <code>dag_id</code> names for each deployment to avoid conflicts

💡 Hint

Think about clarity and safety in production workflows.

Semantic versioning in dag_id clearly identifies versions and deploying one active version avoids confusion and errors.