Why operators abstract common tasks in Apache Airflow - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the base class for Airflow operators.

Apache Airflow

from airflow.operators.[1] import BaseOperator

Drag options to blanks, or click blank then click option'

Abash

Bemail

Cpython

Dbase

Attempts:

3 left

💡 Hint

Common Mistakes

Importing from a specific operator module like bash or python instead of base.

Misspelling the module name.

The BaseOperator class is imported from airflow.operators.base. This is the base class for all operators in Airflow.

2fill in blank

medium

Complete the code to define a simple PythonOperator task.

Apache Airflow

task = PythonOperator(task_id='print_hello', python_callable=[1])

Drag options to blanks, or click blank then click option'

Aprint('hello')

Bprint_hello()

Cprint_hello

Dhello

Attempts:

3 left

💡 Hint

Common Mistakes

Adding parentheses which calls the function immediately.

Passing a string instead of a function reference.

The python_callable argument expects a function name without parentheses. Using print_hello passes the function itself.

3fill in blank

hard

Fix the error in the DAG definition by completing the missing argument.

Apache Airflow

dag = DAG('example_dag', [1], schedule_interval='@daily')

Drag options to blanks, or click blank then click option'

Adefault_args

Bargs

Cdefault_args_dict

Ddefault_args={}

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names like args.

Passing an empty dictionary directly in the argument list.

The default_args parameter is required to pass default arguments to the DAG. It should be a dictionary of arguments.

4fill in blank

hard

Fill both blanks to create a BashOperator that runs a simple command.

Apache Airflow

task = BashOperator(task_id='run_echo', bash_command=[1], dag=[2])

Drag options to blanks, or click blank then click option'

A'echo Hello World'

B'ls -l'

Cdag

Dmy_dag

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the command without quotes.

Passing a string instead of the DAG object for the dag argument.

The bash_command should be a string with the shell command. The dag argument should be the DAG object, here named my_dag.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that filters tasks by owner.

Apache Airflow

owner_tasks = {task.task_id: task for task in tasks if task.owner [1] [2]

Drag options to blanks, or click blank then click option'

A==

B'airflow'

C!=

D'admin'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong comparison operator.

Using the wrong owner string.

The comprehension filters tasks where the owner equals the string 'airflow'.

Practice

1. Why do Airflow operators help when building workflows?

easy

A. They let you reuse common tasks easily and keep code simple

B. They make workflows run faster by using more CPU

C. They automatically fix errors in your code

D. They replace the need for writing any Python code

Solution

1. Step 1: Understand the purpose of operators

   Operators are designed to represent common tasks in workflows so you don't rewrite code each time.

2. Step 2: Recognize benefits of using operators

   Using operators keeps your workflow code organized, simpler, and easier to read.

3. Final Answer:

   They let you reuse common tasks easily and keep code simple -> Option A

4. Quick Check:

   Operators simplify workflows = They let you reuse common tasks easily and keep code simple [OK]

Hint: Operators = reusable task blocks in workflows [OK]

Common Mistakes:

• Thinking operators speed up execution
• Believing operators fix code errors automatically
• Assuming operators remove all coding

2. Which of the following is the correct way to use an Airflow operator in a DAG?

easy

A. task = BashOperator('run', 'echo Hello')

B. task = BashOperator(task='run', command='echo Hello')

C. task = BashOperator(bash_command='echo Hello')

D. task = BashOperator(task_id='run', bash_command='echo Hello')

Solution

1. Step 1: Recall BashOperator syntax

   BashOperator requires named parameters: task_id and bash_command.

2. Step 2: Check each option's syntax

   task = BashOperator(task_id='run', bash_command='echo Hello') uses correct parameter names and syntax; others miss required names or use wrong ones.

3. Final Answer:

   task = BashOperator(task_id='run', bash_command='echo Hello') -> Option D

4. Quick Check:

   Correct parameter names = task = BashOperator(task_id='run', bash_command='echo Hello') [OK]

Hint: Use named parameters task_id and bash_command [OK]

Common Mistakes:

• Omitting task_id parameter
• Using positional instead of named arguments
• Wrong parameter names like 'task' or 'command'

3. Given this Airflow DAG snippet, what will be the output when the BashOperator runs?

task = BashOperator(task_id='print_date', bash_command='date')

medium

A. It prints the current date and time

B. It prints the string 'date'

C. It causes a syntax error

D. It does nothing and fails silently

Solution

1. Step 1: Understand bash_command in BashOperator

   The bash_command runs as a shell command; 'date' prints current date/time.

2. Step 2: Predict output of the command

   Running 'date' in shell outputs current date and time, not the literal word.

3. Final Answer:

   It prints the current date and time -> Option A

4. Quick Check:

   bash_command='date' runs shell date command = It prints the current date and time [OK]

Hint: bash_command runs shell commands literally [OK]

Common Mistakes:

• Thinking it prints the word 'date'
• Assuming syntax error without checking code
• Believing it fails silently without output

4. Identify the error in this Airflow operator usage:

task = BashOperator(task_id='run', bash_cmd='echo Hello')

medium

A. task_id cannot be 'run'

B. Parameter name 'bash_cmd' is incorrect; should be 'bash_command'

C. BashOperator cannot run echo commands

D. Missing task_id parameter

Solution

1. Step 1: Check parameter names for BashOperator

   BashOperator requires 'bash_command' parameter, not 'bash_cmd'.

2. Step 2: Verify other parameters

   task_id is present and valid; echo commands are allowed; 'run' is valid task_id.

3. Final Answer:

   Parameter name 'bash_cmd' is incorrect; should be 'bash_command' -> Option B

4. Quick Check:

   Correct parameter name is bash_command = Parameter name 'bash_cmd' is incorrect; should be 'bash_command' [OK]

Hint: Use exact parameter names: bash_command, not bash_cmd [OK]

Common Mistakes:

• Using wrong parameter names
• Thinking task_id is missing
• Assuming BashOperator can't run echo

5. You want to run a Python function repeatedly in your Airflow DAG. Why is it better to use the PythonOperator instead of writing the function call directly in the DAG file?

hard

A. PythonOperator automatically fixes bugs in your function

B. Direct function calls run faster than PythonOperator

C. PythonOperator abstracts the task, making it reusable and easier to manage

D. Using PythonOperator removes the need to write the function

Solution

1. Step 1: Understand PythonOperator role

   PythonOperator wraps a Python function as a task, allowing reuse and better workflow structure.

2. Step 2: Compare direct calls vs operator usage

   Direct calls run immediately and don't integrate with Airflow's scheduling or retries; operators manage these features.

3. Final Answer:

   PythonOperator abstracts the task, making it reusable and easier to manage -> Option C

4. Quick Check:

   Operators improve task reuse and management = PythonOperator abstracts the task, making it reusable and easier to manage [OK]

Hint: Use PythonOperator to wrap functions as tasks [OK]

Common Mistakes:

• Thinking direct calls are better for reuse
• Believing operators fix bugs automatically
• Assuming operators remove need to write code