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.

Practice

1. What is the main purpose of DAG versioning in Airflow?

easy

A. To speed up the execution of tasks in a DAG

B. To reduce the number of DAGs in the Airflow UI

C. To give each workflow version a unique name for safe management

D. To automatically fix errors in DAG code

Solution

1. Step 1: Understand DAG versioning concept

   DAG versioning means assigning unique names to different versions of workflows to avoid confusion and conflicts.

2. Step 2: Identify the main benefit

   This unique naming helps run and manage multiple workflow versions safely without overwriting or mixing them.

3. Final Answer:

   To give each workflow version a unique name for safe management -> Option C

4. Quick Check:

   DAG versioning = unique naming for safety [OK]

Hint: Remember: versioning means unique names for workflows [OK]

Common Mistakes:

• Thinking versioning speeds up task execution
• Confusing versioning with error fixing
• Believing versioning reduces DAG count

2. Which of the following is a correct way to name a DAG version in Airflow?

easy

A. my_dag_v1

B. my dag version 1

C. my-dag-version-1!

D. my.dag.version.1

Solution

1. Step 1: Check valid DAG naming rules

   DAG names should be simple strings without spaces or special characters like ! or dots.

2. Step 2: Identify the valid option

   my_dag_v1 uses underscores and no spaces or special characters, making it valid.

3. Final Answer:

   my_dag_v1 -> Option A

4. Quick Check:

   Valid DAG names use underscores, no spaces [OK]

Hint: Use underscores, avoid spaces and special chars [OK]

Common Mistakes:

• Using spaces in DAG names
• Including special characters like !
• Using dots which can cause issues

3. Given this DAG code snippet, what will be the DAG id when versioning is applied as shown?

version = 3
dag_id = f"example_dag_v{version}"
print(dag_id)

medium

A. example_dagv3

B. example_dag_version3

C. example_dag_3

D. example_dag_v3

Solution

1. Step 1: Understand f-string usage

   The f-string inserts the value of 'version' variable into the string where {version} is placed.

2. Step 2: Substitute version value

   Since version = 3, the string becomes 'example_dag_v3'.

3. Final Answer:

   example_dag_v3 -> Option D

4. Quick Check:

   f-string with version=3 = example_dag_v3 [OK]

Hint: f-string inserts variable value directly [OK]

Common Mistakes:

• Confusing variable placement in f-string
• Adding extra words like 'version' manually
• Missing underscores in the name

4. You have two DAG versions named data_pipeline_v1 and data_pipeline_v2. You accidentally overwrite data_pipeline_v1 code with v2 code but keep the same DAG id. What is the main problem here?

medium

A. Airflow will only run the latest code under one DAG id, losing version 1

B. The scheduler will crash due to duplicate DAG ids

C. Airflow will create duplicate DAGs with same id

D. Both versions run simultaneously causing conflicts

Solution

1. Step 1: Understand DAG id uniqueness

   Airflow identifies DAGs by their DAG id. If two versions share the same id, only one is recognized.

2. Step 2: Identify effect of overwriting code

   Overwriting v1 code with v2 under same id means v1 is lost and only v2 runs.

3. Final Answer:

   Airflow will only run the latest code under one DAG id, losing version 1 -> Option A

4. Quick Check:

   Same DAG id means only one version runs [OK]

Hint: Unique DAG ids prevent overwriting versions [OK]

Common Mistakes:

• Thinking both versions run at once
• Expecting duplicate DAGs with same id
• Assuming scheduler crashes on duplicates

5. You want to manage multiple DAG versions without changing DAG ids manually. Which strategy below best helps you achieve this in Airflow?

hard

A. Manually rename DAG files for each version

B. Use Airflow Variables to store the version and dynamically set DAG id

C. Use the same DAG id and overwrite code for each version

D. Disable all DAGs except the latest version

Solution

1. Step 1: Understand dynamic DAG id setting

   Using Airflow Variables allows you to store version info externally and inject it into DAG id dynamically.

2. Step 2: Compare with other options

   Manual renaming is error-prone, overwriting loses old versions, disabling DAGs is manual and not scalable.

3. Final Answer:

   Use Airflow Variables to store the version and dynamically set DAG id -> Option B

4. Quick Check:

   Dynamic DAG id via Variables = best versioning [OK]

Hint: Use Variables to automate version naming [OK]

Common Mistakes:

• Relying on manual file renaming
• Overwriting code without versioning
• Disabling DAGs instead of versioning