Execution date vs logical date in Apache Airflow - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Airflow Execution Date

In Apache Airflow, what does the execution date represent?

A The date and time when the DAG was last modified.

B The date and time when the task actually runs on the system.

C The current system date and time when the DAG is triggered manually.

D The logical date and time for which the DAG run is scheduled, representing the data interval start.

💡 Hint

Think about what Airflow uses to identify the data period a DAG run is processing.

The execution date in Airflow is a logical timestamp representing the start of the data interval the DAG run is processing. It is not the actual time the task runs.

💻 Command Output

intermediate

Output of Airflow DAG Run Dates

Given a DAG scheduled to run daily starting at 2024-06-01, if a DAG run starts at 2024-06-02 01:00 AM, what is the execution date shown in the Airflow UI for this run?

A 2024-06-01 00:00:00

B 2024-06-02 01:00:00

C 2024-06-02 00:00:00

D 2024-06-03 00:00:00

💡 Hint

Remember that execution date points to the start of the data interval, not the actual run time.

The execution date for a daily DAG run is the start of the day it processes. Even if the run starts later, the execution date remains the previous day at midnight.

🔀 Workflow

advanced

Airflow Logical Date vs Execution Date in Backfill

You run an Airflow backfill command for a DAG with daily schedule from 2024-05-28 to 2024-05-30. Which dates will be used as execution dates for the backfill runs?

A 2024-05-29, 2024-05-30, 2024-05-31

B 2024-05-28, 2024-05-29, 2024-05-30

C 2024-05-27, 2024-05-28, 2024-05-29

D 2024-05-30, 2024-05-31, 2024-06-01

💡 Hint

Execution dates correspond to the logical schedule dates you specify for backfill.

Backfill runs use the execution dates you specify, which are the logical dates for the DAG runs. For daily schedules, these are the dates you pass to backfill.

❓ Troubleshoot

advanced

Troubleshooting Unexpected Execution Date in Airflow

You notice that a DAG run triggered manually shows an execution date of 2024-06-01 00:00:00, even though you triggered it on 2024-06-05. Why does this happen?

A Manual triggers always use the current system date as execution date.

B The DAG schedule interval is ignored for manual triggers, so execution date is random.

C Manual triggers use the logical execution date you specify or default to the previous scheduled interval start.

D Airflow has a bug causing execution dates to not update on manual triggers.

💡 Hint

Think about how Airflow assigns execution dates for manual runs.

When manually triggering a DAG, Airflow uses the execution date you specify or defaults to the previous scheduled interval start, not the current date.

✅ Best Practice

expert

Best Practice for Using Execution Date in Airflow Tasks

Which is the best practice for using the execution date inside an Airflow task to process data?

A Use the execution date as the start of the data interval and calculate the end date by adding the schedule interval.

B Use the current system date and time to process data, ignoring the execution date.

C Use the execution date as the exact timestamp to fetch data only for that second.

D Use a fixed date hardcoded in the DAG to avoid confusion.

💡 Hint

Think about how to define the data interval for processing in scheduled DAGs.

The execution date marks the start of the data interval. Adding the schedule interval gives the end of the interval, which is the best way to process data for that run.