Sharing data between tasks effectively in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does XCom share data between tasks?

In Apache Airflow, what is the primary mechanism used to share small pieces of data between tasks?

A Writing data to a shared file system manually.

B Using XCom to push and pull data between tasks.

C Passing data through environment variables automatically.

D Using global Python variables accessible by all tasks.

💡 Hint

Think about the built-in Airflow feature designed for inter-task communication.

XCom (short for cross-communication) is Airflow's built-in feature to share small amounts of data between tasks by pushing and pulling key-value pairs.

💻 Command Output

intermediate

Output of XCom pull with no matching key

What is the output of the following Airflow PythonOperator task code snippet when no XCom value exists for the given key?

Apache Airflow

ti.xcom_pull(key='nonexistent_key', task_ids='task_a')

A '' (empty string)

B Raises KeyError

C None

D 0

💡 Hint

Consider what Airflow returns when no XCom value is found for a key.

If no XCom value exists for the specified key and task, Airflow returns None instead of raising an error.

❓ Configuration

advanced

Correct XCom push syntax in a PythonOperator

Which code snippet correctly pushes a value to XCom inside a PythonOperator's callable function?

A

def task_func():
    xcom_push(key='result', value=42)

B

def task_func(ti):
    ti.xcom_push('result', 42)

C

def task_func(ti):
    ti.push_xcom(key='result', value=42)

D

def task_func(ti):
    ti.xcom_push(key='result', value=42)

💡 Hint

Remember the method name and parameters for pushing XCom data.

The correct method is ti.xcom_push with named parameters key and value.

🔀 Workflow

advanced

Best practice for sharing large data between tasks

Which approach is best for sharing large datasets between Airflow tasks?

A Store the data in an external storage like S3 or a database and pass the reference via XCom.

B Push the entire dataset directly via XCom between tasks.

C Serialize the data as a string and push it via XCom.

D Use global variables in the DAG file to share data.

💡 Hint

Think about XCom size limits and performance.

XCom is designed for small data. Large data should be stored externally and referenced by XCom to avoid performance issues.

❓ Troubleshoot

expert

Why does XCom pull return None unexpectedly?

You have two tasks: task_a pushes a value to XCom with key 'data', and task_b tries to pull it. But task_b always gets None. What is the most likely cause?

A task_b runs before task_a completes, so the XCom value is not yet available.

B The key used in task_b's xcom_pull is misspelled.

C XCom backend is disabled in Airflow configuration.

D task_a did not push any value to XCom.

💡 Hint

Consider task execution order and dependencies.

If task_b runs before task_a finishes, the XCom value won't exist yet, so xcom_pull returns None.

Practice

1. What is the primary purpose of using Airflow Variables when sharing data between tasks?

easy

A. To execute tasks in parallel

B. To monitor task execution logs

C. To schedule DAG runs automatically

D. To store small pieces of data accessible across different tasks

Solution

1. Step 1: Understand Airflow Variables role

   Airflow Variables are designed to hold small data values that can be shared between tasks.

2. Step 2: Identify the correct use case

   Sharing data between tasks requires a storage mechanism accessible by all tasks, which Airflow Variables provide.

3. Final Answer:

   To store small pieces of data accessible across different tasks -> Option D

4. Quick Check:

   Airflow Variables = data sharing [OK]

Hint: Variables store shared data between tasks easily [OK]

Common Mistakes:

• Confusing Variables with task scheduling
• Thinking Variables execute tasks
• Using Variables for logging

2. Which of the following is the correct way to set an Airflow Variable named my_var with value 123 inside a PythonOperator task?

easy

A. Variable.set('my_var', 123)

B. Variable.set(my_var, '123')

C. Variable.get('my_var', 123)

D. Variable.create('my_var', 123)

Solution

1. Step 1: Recall Variable.set syntax

   The correct method to set a variable is Variable.set(key, value) where key is a string and value is the data.

2. Step 2: Check option correctness

   Variable.set('my_var', 123) uses Variable.set with key 'my_var' and value 123 correctly as a string key and integer value.

3. Final Answer:

   Variable.set('my_var', 123) -> Option A

4. Quick Check:

   Set variable = Variable.set(key, value) [OK]

Hint: Use Variable.set('key', value) to store data [OK]

Common Mistakes:

• Using Variable.get instead of set to store data
• Not quoting the variable name key
• Using a non-existent method like Variable.create

3. Given the following code snippet in two tasks, what will be printed by task_b?

from airflow.models import Variable

def task_a():
    Variable.set('shared_key', 'hello')

def task_b():
    value = Variable.get('shared_key')
    print(value)

medium

A. None

B. hello

C. shared_key

D. Error: Variable not found

Solution

1. Step 1: Analyze task_a behavior

   task_a sets the Variable 'shared_key' with value 'hello'.

2. Step 2: Analyze task_b behavior

   task_b retrieves the Variable 'shared_key' and prints its value, which is 'hello'.

3. Final Answer:

   hello -> Option B

4. Quick Check:

   Set then get Variable = 'hello' [OK]

Hint: Get returns the stored value by key [OK]

Common Mistakes:

• Expecting the key name instead of value
• Assuming Variable.get returns None if set
• Forgetting to set the Variable before getting

4. You wrote this code in task_b to get a Variable set by task_a:

value = Variable.get('my_var')

But you get an error: KeyError: 'Variable my_var does not exist'. What is the best fix?

medium

A. Set a default value in Variable.get like Variable.get('my_var', default_var='default')

B. Change Variable.get to Variable.set

C. Remove the Variable.get call

D. Restart Airflow scheduler

Solution

1. Step 1: Understand the error cause

   The error means 'my_var' was not set before getting it, so Variable.get fails.

2. Step 2: Use default value to avoid error

   Variable.get supports a default_var parameter to return if key missing, preventing KeyError.

3. Final Answer:

   Set a default value in Variable.get like Variable.get('my_var', default_var='default') -> Option A

4. Quick Check:

   Use default_var to avoid missing key error [OK]

Hint: Add default_var to Variable.get to prevent errors [OK]

Common Mistakes:

• Using Variable.set instead of get to read data
• Ignoring missing Variable errors
• Restarting scheduler without fixing code

5. You want to share a list of user IDs between two tasks in Airflow. Which approach is best to share this data effectively?

hard

A. Write the list to a local file and read it in the next task

B. Pass the list directly as a Python variable between tasks

C. Use XComs to push and pull the list between tasks

D. Serialize the list as JSON string and store it in an Airflow Variable

Solution

1. Step 1: Understand data sharing options

   Airflow Variables are for small strings; passing Python variables directly is not possible between tasks.

2. Step 2: Identify best practice for complex data

   XComs are designed to share data like lists between tasks efficiently and safely.

3. Final Answer:

   Use XComs to push and pull the list between tasks -> Option C

4. Quick Check:

   XComs = best for task-to-task data sharing [OK]

Hint: Use XComs for complex data sharing between tasks [OK]

Common Mistakes:

• Trying to pass Python variables directly
• Using Variables for large or complex data
• Using local files which break portability