TaskFlow API for cleaner XCom in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Airflow TaskFlow function?

Given the following Airflow DAG task using TaskFlow API, what will be the output when the task runs successfully?

Apache Airflow

from airflow.decorators import task

@task
def multiply_by_two(x: int) -> int:
    return x * 2

result = multiply_by_two(5)
print(result)

A XComArg object

B 10

C None

D TypeError

💡 Hint

Remember that TaskFlow API returns a special object representing the task output, not the raw value.

In Airflow's TaskFlow API, calling a decorated task function returns an XComArg object, which represents the future result of the task. The actual value is pushed to XCom only after the task runs.

🧠 Conceptual

intermediate

Which statement best describes XCom behavior in TaskFlow API?

Select the correct statement about how XComs are handled when using Airflow's TaskFlow API.

A TaskFlow API disables XComs by default to improve performance.

B You must manually push XCom values using task_instance.xcom_push() inside the task.

C TaskFlow API automatically serializes and pushes return values to XCom without extra code.

D XComs are only available if you use PythonOperator, not TaskFlow API.

💡 Hint

Think about how TaskFlow API simplifies passing data between tasks.

TaskFlow API automatically handles pushing the return value of a decorated task to XCom, so you don't need to manually push or pull values.

❓ Troubleshoot

advanced

Why does this TaskFlow task fail to push the expected XCom value?

Consider this task code snippet: from airflow.decorators import task @task def add_numbers(a, b): sum = a + b What is the reason the XCom value is None after task execution?

A The function does not return the sum, so nothing is pushed to XCom.

B The @task decorator requires explicit xcom_push calls inside the function.

C The variables a and b are not typed, causing serialization failure.

D Airflow disables XCom for functions with more than one argument.

💡 Hint

Check if the function returns a value to be pushed to XCom.

In TaskFlow API, only the return value of the decorated function is pushed to XCom. Without a return statement, the XCom value is None.

🔀 Workflow

advanced

What is the correct way to pass data between two TaskFlow tasks?

Given two tasks defined with TaskFlow API: @task def task_a(): return 42 @task def task_b(x): return x + 1 How do you correctly set up the DAG to pass the output of task_a to task_b?

A

result = task_a()
task_b()  # no argument

B

task_a()
task_b(task_a())  # call twice

C final = task_b(task_a) # pass function, not result

D

result = task_a()
final = task_b(result)

💡 Hint

Remember that calling a task returns an XComArg that can be passed as argument to another task.

Calling task_a() returns an XComArg object representing its output, which can be passed directly as argument to task_b().

✅ Best Practice

expert

Which approach best improves XCom data handling in TaskFlow API for large data?

You have a TaskFlow task that returns a large dictionary. Which method is best to avoid performance issues with XCom?

A Serialize the dictionary as a JSON string and return it directly from the task.

B Store the large data in external storage (e.g., S3) and push only the reference (path) via XCom.

C Split the dictionary into smaller chunks and return multiple tasks each pushing part of data.

D Increase Airflow's XCom max size limit to accommodate the large dictionary.

💡 Hint

Think about how to keep XCom lightweight and efficient.

XCom is designed for small messages. For large data, best practice is to store it externally and pass only a reference via XCom to avoid performance degradation.