BranchPythonOperator in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of BranchPythonOperator with conditional branching

Given the following Airflow DAG snippet using BranchPythonOperator, what will be the output of the task branch_task when execution_date.day is 15?

Apache Airflow

def choose_branch(**kwargs):
    day = kwargs['execution_date'].day
    if day < 10:
        return 'task_a'
    else:
        return 'task_b'

branch_task = BranchPythonOperator(
    task_id='branch_task',
    python_callable=choose_branch,
    provide_context=True,
    dag=dag
)

A 'task_a'

B 'branch_task'

C None

D 'task_b'

💡 Hint

Check the condition comparing the day of execution_date to 10.

The function returns 'task_b' because the day (15) is not less than 10, so the else branch is taken.

🧠 Conceptual

intermediate

Understanding BranchPythonOperator behavior

What happens to downstream tasks that are not returned by the BranchPythonOperator's callable?

A They cause the DAG to fail.

B They are executed normally.

C They are skipped and not executed.

D They are retried automatically.

💡 Hint

Think about how branching controls the flow of tasks.

BranchPythonOperator skips all downstream tasks except those returned by its callable function.

🔀 Workflow

advanced

Correct order of task execution with BranchPythonOperator

Arrange the following tasks in the order they execute in an Airflow DAG with a BranchPythonOperator named branch_task that chooses between task_a and task_b. The DAG starts with start_task and ends with end_task.

A 1,2,3,4

B 1,3,2,4

C 2,1,3,4

D 1,2,4,3

💡 Hint

BranchPythonOperator runs after the start and before the chosen task.

The DAG runs start_task first, then branch_task decides which task to run next (task_a or task_b), then finally end_task.

❓ Troubleshoot

advanced

Error caused by BranchPythonOperator returning invalid task_id

What error will Airflow raise if the BranchPythonOperator's callable returns a task_id that does not exist in the DAG?

A AirflowSkipException

B AirflowException

C AirflowTaskNotFoundException

D AirflowDagCycleException

💡 Hint

Consider what happens when the DAG tries to find a task by a name that is missing.

Airflow raises an AirflowException because it cannot find the task_id returned by the BranchPythonOperator in the DAG's task dictionary.

✅ Best Practice

expert

Best practice for multiple branches in BranchPythonOperator

Which approach is best to handle multiple possible branches in a BranchPythonOperator to ensure all branches are valid and maintainable?

A Return a list of task_ids for all possible branches and ensure they exist in the DAG.

B Return a single task_id and use multiple BranchPythonOperators chained for other branches.

C Return task_ids as strings concatenated with commas in one string.

D Return None to run all downstream tasks.

💡 Hint

BranchPythonOperator supports returning multiple task_ids as a list.

Returning a list of valid task_ids allows branching to multiple tasks cleanly and is supported by Airflow.