Idempotent task design in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is idempotency important in Airflow tasks?

In Airflow, tasks may run multiple times due to retries or manual triggers. Why is designing tasks to be idempotent important?

A To prevent Airflow from scheduling tasks automatically

B To make tasks run faster by skipping all processing

C To allow tasks to run only once ever without retries

D To ensure tasks produce the same result and avoid side effects when run multiple times

💡 Hint

Think about what happens if a task runs more than once and changes data each time.

Idempotency ensures that running a task multiple times does not cause unintended changes or duplicate effects. This is crucial in Airflow where retries or manual reruns happen.

💻 Command Output

intermediate

Output of an Airflow task with idempotent file creation

Consider an Airflow PythonOperator task that creates a file only if it does not exist. What will be the output if the task runs twice?

Apache Airflow

import os
file_path = '/tmp/data.txt'
if not os.path.exists(file_path):
    with open(file_path, 'w') as f:
        f.write('Airflow data')
print('File created or already exists')

A

File created
File not created

B

File created or already exists
File created or already exists

C

File created
File created

D File not created

💡 Hint

Check what happens when the file already exists on the second run.

The code checks if the file exists before creating it. On the second run, the file exists, so it skips creation but still prints the message.

❓ Configuration

advanced

Idempotent database update in Airflow task

You want an Airflow task to update a database record only if a specific condition is met, avoiding duplicate updates on retries. Which SQL statement ensures idempotency?

A UPDATE users SET status='active' WHERE id=123 AND status!='active';

B UPDATE users SET status='active' WHERE id=123;

C INSERT INTO users (id, status) VALUES (123, 'active');

D DELETE FROM users WHERE id=123;

💡 Hint

Think about how to avoid changing the record if it already has the desired status.

Option A updates the record only if the status is not already 'active', preventing repeated updates on retries and ensuring idempotency.

❓ Troubleshoot

advanced

Troubleshooting non-idempotent Airflow task causing duplicate data

An Airflow task inserts rows into a table every time it runs, causing duplicates on retries. What is the best way to fix this?

A Modify the task to check if the row exists before inserting

B Increase the retry delay to avoid duplicates

C Disable retries for the task

D Run the task only once manually

💡 Hint

How can you prevent inserting the same data multiple times?

Checking for existing rows before inserting ensures the task does not create duplicates on retries, making it idempotent.

🔀 Workflow

expert

Designing an idempotent Airflow DAG with external API calls

You have an Airflow DAG that calls an external API to create resources. The API does not support idempotency keys. How can you design the DAG to avoid creating duplicate resources on retries?

A Ignore failures and manually clean duplicates later

B Increase the task timeout to avoid retries

C Store API response IDs in XCom and check before retrying to skip duplicate calls

D Use multiple tasks to call the API in parallel

💡 Hint

Think about how to remember what was created in previous attempts.

By storing created resource IDs in XCom, the task can check if the resource was already created and skip duplicate API calls, ensuring idempotency despite the API limitation.

Practice

1. What does it mean for a task in Airflow to be idempotent?

easy

A. It can run multiple times without changing the result beyond the first run

B. It runs only once and then stops permanently

C. It requires manual approval before each run

D. It always produces a different output every time it runs

Solution

1. Step 1: Understand idempotency in task context

   Idempotent means running the task multiple times does not change the final outcome after the first successful run.

2. Step 2: Compare options with definition

   Only It can run multiple times without changing the result beyond the first run matches this meaning; others describe different behaviors.

3. Final Answer:

   It can run multiple times without changing the result beyond the first run -> Option A

4. Quick Check:

   Idempotent = safe repeated runs [OK]

Hint: Idempotent means safe to run many times without side effects [OK]

Common Mistakes:

• Thinking idempotent means runs only once
• Confusing idempotent with manual approval
• Assuming output changes every run

2. Which Airflow feature helps store task state to support idempotent task design?

easy

A. XCom for passing messages between tasks

B. DAG scheduling interval

C. Task retries count

D. Airflow webserver UI

Solution

1. Step 1: Identify Airflow features related to task state

   XCom is used to share small pieces of data between tasks, useful to track if work is done.

2. Step 2: Match feature to idempotency support

   XCom helps tasks check previous results to avoid repeating work, supporting idempotency.

3. Final Answer:

   XCom for passing messages between tasks -> Option A

4. Quick Check:

   XCom stores task state for idempotency [OK]

Hint: XCom stores task info between runs to check completion [OK]

Common Mistakes:

• Confusing scheduling interval with task state
• Thinking retries control idempotency
• Assuming web UI manages task data

3. Given this Airflow PythonOperator task code snippet, what will be the output if the task runs twice?

def task_function(**kwargs):
    ti = kwargs['ti']
    if ti.xcom_pull(task_ids='task_function', key='status') == 'done':
        return 'Already done'
    # Simulate work
    ti.xcom_push(key='status', value='done')
    return 'Work done'

medium

A. Both runs return 'Work done'

B. First run: 'Work done', second run: 'Already done'

C. First run returns None, second run errors

D. Both runs return 'Already done'

Solution

1. Step 1: Analyze first run behavior

   On first run, no XCom value 'done' exists, so task pushes 'done' and returns 'Work done'.

2. Step 2: Analyze second run behavior

   On second run, XCom pull returns 'done', so task returns 'Already done' without repeating work.

3. Final Answer:

   First run: 'Work done', second run: 'Already done' -> Option B

4. Quick Check:

   Check XCom before work = different outputs [OK]

Hint: Check XCom pull result to decide task output [OK]

Common Mistakes:

• Ignoring XCom pull result and always doing work
• Assuming XCom push overwrites before pull
• Confusing return values with XCom data

4. You wrote an Airflow task to be idempotent by checking XCom before running. But the task always repeats work on every run. What is the most likely cause?

medium

A. The Airflow webserver is down

B. The DAG schedule interval is too frequent

C. The task retries are set to zero

D. The task uses different keys or task_ids when pushing and pulling XCom

Solution

1. Step 1: Understand XCom push and pull matching

   XCom pull must use the exact same key and task_id as the push to retrieve stored data.

2. Step 2: Identify cause of repeated work

   If keys or task_ids differ, pull returns None, so task thinks work is not done and repeats it.

3. Final Answer:

   The task uses different keys or task_ids when pushing and pulling XCom -> Option D

4. Quick Check:

   XCom key/task_id mismatch causes repeated work [OK]

Hint: Match XCom keys and task_ids exactly to avoid repeats [OK]

Common Mistakes:

• Blaming schedule interval for idempotency failure
• Thinking retries affect XCom data
• Assuming webserver status impacts task logic

5. You want to design an Airflow task that downloads a file only if it does not exist locally, ensuring idempotency. Which approach is best?

hard

A. Always download the file to overwrite local copy

B. Download the file only if the DAG run is the first of the day

C. Check if the file exists before downloading; if yes, skip download and mark task done

D. Use task retries to handle download failures

Solution

1. Step 1: Identify idempotent design for file download

   Idempotency means avoiding repeated work if already done, so check file existence first.

2. Step 2: Evaluate options for idempotency

   Check if the file exists before downloading; if yes, skip download and mark task done checks file presence and skips download if found, ensuring safe repeated runs.

3. Final Answer:

   Check if the file exists before downloading; if yes, skip download and mark task done -> Option C

4. Quick Check:

   Check before action ensures idempotency [OK]

Hint: Check existing output before work to ensure idempotency [OK]

Common Mistakes:

• Always downloading ignores idempotency
• Using DAG run time instead of file check
• Relying on retries for idempotency