EmailOperator for notifications in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Airflow EmailOperator task?

Given the following Airflow task using EmailOperator, what will be the result when the task runs successfully?

Apache Airflow

from airflow.operators.email import EmailOperator
email_task = EmailOperator(
    task_id='send_email',
    to='[e-mail]',
    subject='Test Email',
    html_content='<h1>Hello</h1>',
    dag=None
)

result = email_task.execute(context={})

A Returns the string 'Email sent successfully' without sending email

B Raises a TypeError because 'dag' parameter is None

C Sends an email to [e-mail] with subject 'Test Email' and returns None

D Raises an AirflowException due to missing SMTP configuration

💡 Hint

EmailOperator's execute method sends the email and returns None on success.

EmailOperator sends the email when execute() is called and returns None if successful. It does not return a string or raise error if SMTP is configured properly. 'dag=None' is allowed for standalone task testing.

🧠 Conceptual

intermediate

Which parameter in EmailOperator specifies the email recipient?

In Airflow's EmailOperator, which parameter is used to specify the recipient email address?

A to

B recipient

C email_to

D address

💡 Hint

Think about the common English word used for sending emails.

The 'to' parameter is used to specify the recipient email address in EmailOperator.

❓ Troubleshoot

advanced

Why does this EmailOperator task fail with SMTPAuthenticationError?

An Airflow EmailOperator task fails with the error 'SMTPAuthenticationError: (535, b'Authentication failed')'. What is the most likely cause?

Apache Airflow

email_task = EmailOperator(
    task_id='send_email',
    to='[e-mail]',
    subject='Alert',
    html_content='Task failed',
    dag=dag
)

email_task.execute(context={})

A Missing 'to' parameter in EmailOperator

B Incorrect SMTP server credentials configured in Airflow settings

C The 'html_content' parameter is empty

D The DAG is not scheduled properly

💡 Hint

SMTPAuthenticationError means the email server rejected login.

SMTPAuthenticationError indicates the SMTP server credentials are wrong or missing in Airflow's configuration.

🔀 Workflow

advanced

In which Airflow DAG event is EmailOperator best used for failure notifications?

You want to send an email notification only when a DAG task fails. Which Airflow feature allows you to trigger EmailOperator only on failure?

A Adding EmailOperator as the first task in the DAG

B Setting 'trigger_rule' to 'all_success'

C Using 'start_date' to schedule the email

D Using the 'on_failure_callback' parameter in the task

💡 Hint

Callbacks run on specific task events like failure or success.

'on_failure_callback' lets you specify a function or operator to run when a task fails, perfect for sending failure emails.

✅ Best Practice

expert

What is the best practice to avoid exposing email credentials in Airflow EmailOperator?

To keep email server credentials secure when using EmailOperator in Airflow, what is the recommended approach?

A Store credentials in Airflow Connections and reference them in EmailOperator

B Hardcode credentials directly in the DAG file

C Use environment variables inside the DAG code without encryption

D Include credentials in the email content for transparency

💡 Hint

Airflow Connections are designed to securely store credentials.

Airflow Connections securely store credentials and can be referenced by operators, avoiding hardcoding sensitive data.

Practice

1. What is the primary purpose of the EmailOperator in Airflow?

easy

A. To store logs of task executions

B. To schedule tasks at specific times

C. To monitor CPU usage of Airflow workers

D. To send emails automatically from Airflow tasks

Solution

1. Step 1: Understand EmailOperator's role

   EmailOperator is designed to send emails triggered by Airflow tasks.

2. Step 2: Compare with other options

   Scheduling tasks, storing logs, and monitoring CPU are handled by other Airflow components, not EmailOperator.

3. Final Answer:

   To send emails automatically from Airflow tasks -> Option D

4. Quick Check:

   EmailOperator = send emails [OK]

Hint: EmailOperator is for sending emails, not scheduling [OK]

Common Mistakes:

• Confusing EmailOperator with scheduling operators
• Thinking EmailOperator manages logs or monitoring
• Assuming EmailOperator runs tasks instead of notifying

2. Which of the following is the correct way to import EmailOperator in an Airflow DAG file?

easy

A. from airflow.operators.email_operator import Email

B. from airflow.operators.email import EmailOperator

C. from airflow.operators.email_operator import EmailOperator

D. import EmailOperator from airflow.operators.email_operator

Solution

1. Step 1: Recall correct import path

   The correct import path for EmailOperator in Airflow is from airflow.operators.email_operator import EmailOperator.

2. Step 2: Check other options for syntax or naming errors

   from airflow.operators.email import EmailOperator uses wrong module name (missing '_operator'); from airflow.operators.email_operator import Email imports wrong class name; import EmailOperator from airflow.operators.email_operator uses invalid Python import syntax.

3. Final Answer:

   from airflow.operators.email_operator import EmailOperator -> Option C

4. Quick Check:

   Correct import = airflow.operators.email_operator [OK]

Hint: Use 'from airflow.operators.email_operator import EmailOperator' [OK]

Common Mistakes:

• Using wrong module path like email
• Incorrect import syntax like 'import X from Y'
• Confusing class name with module name

3. Given this Airflow task using EmailOperator:

email_task = EmailOperator(
    task_id='send_email',
    to='[e-mail]',
    subject='Test Email',
    html_content='Hello from Airflow!',
    dag=dag
)

What will happen when this task runs successfully?

medium

A. The task will send an email but with empty content

B. An email with subject 'Test Email' is sent to [e-mail]

C. No email is sent because 'to' is not a list

D. The task will fail because html_content is missing

Solution

1. Step 1: Analyze EmailOperator parameters

   The task specifies 'to' as a string email address, 'subject', and 'html_content' correctly.

2. Step 2: Understand EmailOperator behavior

   EmailOperator accepts a string or list for 'to' and sends the email with given subject and content.

3. Final Answer:

   An email with subject 'Test Email' is sent to [e-mail] -> Option B

4. Quick Check:

   Valid params = email sent [OK]

Hint: Single string 'to' is valid for EmailOperator [OK]

Common Mistakes:

• Thinking 'to' must be a list
• Assuming html_content is required to be a file
• Believing task fails without attachments

4. You wrote this EmailOperator task but it fails with an error:

email_task = EmailOperator(
    task_id='notify',
    to=['[e-mail]'],
    subject='Alert',
    html_content='Check this alert',
    dag=dag
)

What is the most likely cause of the failure?

medium

A. SMTP server is not configured in Airflow settings

B. The 'to' parameter must be a string, not a list

C. Missing 'from_email' parameter in EmailOperator

D. The 'subject' parameter cannot contain spaces

Solution

1. Step 1: Check EmailOperator parameters

   The 'to' parameter accepts a list, and 'subject' with spaces is valid.

2. Step 2: Identify common failure cause

   EmailOperator requires SMTP server setup in Airflow config; missing this causes failure.

3. Final Answer:

   SMTP server is not configured in Airflow settings -> Option A

4. Quick Check:

   SMTP setup missing = failure [OK]

Hint: Check SMTP config if EmailOperator fails [OK]

Common Mistakes:

• Assuming 'to' cannot be a list
• Thinking the 'subject' parameter cannot contain spaces
• Thinking 'from_email' is mandatory parameter

5. You want to send an email notification only when a task fails using EmailOperator. Which Airflow feature should you use to trigger the email task only on failure?

hard

A. Set trigger_rule="one_failed" on the EmailOperator task

B. Set trigger_rule="all_success" on the EmailOperator task

C. Use depends_on_past=True on the EmailOperator task

D. Set email_on_failure=False in the DAG definition

Solution

1. Step 1: Understand trigger_rule usage

   Setting trigger_rule="one_failed" makes the task run only if any upstream task fails.

2. Step 2: Evaluate other options

   all_success runs only if all succeed; depends_on_past controls task dependency on previous runs; email_on_failure is a DAG-level flag, not for task trigger.

3. Final Answer:

   Set trigger_rule="one_failed" on the EmailOperator task -> Option A

4. Quick Check:

   Trigger on failure = trigger_rule one_failed [OK]

Hint: Use trigger_rule='one_failed' to run on failure only [OK]

Common Mistakes:

• Using trigger_rule='all_success' for failure notification
• Confusing depends_on_past with failure triggers
• Misusing email_on_failure flag for task triggers