Cost optimization for cloud resources in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Cost Optimization Strategies in Airflow

Which of the following is the most effective way to reduce cloud costs when running Airflow workflows?

A Use Airflow's scheduling to run tasks only during off-peak hours to leverage cheaper cloud rates.

B Disable task retries to save compute resources even if tasks fail frequently.

C Always keep all Airflow workers running 24/7 to avoid startup delays.

D Increase the number of parallel tasks to finish workflows faster regardless of resource usage.

💡 Hint

Think about when cloud providers offer lower prices and how scheduling can help.

Scheduling tasks during off-peak hours can leverage cheaper cloud rates, reducing costs without sacrificing reliability. Increasing parallelism or keeping workers always on can increase costs. Disabling retries may cause failures and rework.

💻 Command Output

intermediate

Output of Airflow CLI Command for Worker Status

What is the output of the following command when no Airflow workers are currently running?

airflow celery status

A Error: command not found

B

celery@worker1: OK
celery@worker2: OK

C

celery@worker1: DOWN
celery@worker2: DOWN

D No nodes currently registered.

💡 Hint

Think about what the status command shows when no workers are connected.

The 'airflow celery status' command shows registered workers. If none are running, it outputs 'No nodes currently registered.'

❓ Configuration

advanced

Configuring Airflow to Scale Down Workers Automatically

Which Airflow configuration snippet correctly enables automatic scaling down of Celery workers to save cloud costs?

A

[celery]
worker_autoscale = 10,3

B

[scheduler]
worker_autoscale = 3,10

C

[celery]
worker_autoscale = 3,10

D

[core]
worker_autoscale = 10,3

💡 Hint

Check the correct section and the order of max and min workers in worker_autoscale.

The 'worker_autoscale' setting under the [celery] section uses the format 'min_workers,max_workers'. 'worker_autoscale = 3,10' means scale between 3 and 10 workers automatically.

❓ Troubleshoot

advanced

Troubleshooting Unexpected High Cloud Costs from Airflow

You notice your cloud bill increased sharply after deploying Airflow. Which of the following is the most likely cause?

A Airflow DAGs are scheduled too infrequently, causing idle resources.

B Airflow workers are not shutting down after task completion, running 24/7.

C Airflow is using the LocalExecutor instead of CeleryExecutor.

D Airflow logs are stored locally instead of cloud storage.

💡 Hint

Consider what causes continuous resource usage and costs.

If Airflow workers remain running all the time, they consume cloud resources continuously, increasing costs. Infrequent scheduling reduces costs. LocalExecutor runs tasks locally, not necessarily increasing cloud costs. Logs stored locally do not affect cloud costs.

🔀 Workflow

expert

Optimizing Airflow DAG for Cost Efficiency

You want to optimize an Airflow DAG to minimize cloud costs by reducing unnecessary task runs. Which workflow change achieves this best?

A Use task triggers to run downstream tasks only if upstream tasks succeed.

B Set all tasks to run daily regardless of upstream task success.

C Increase retries for all tasks to ensure completion even if costly.

D Disable task dependencies to allow parallel execution of all tasks.

💡 Hint

Think about avoiding running tasks that are not needed.

Using task triggers to run downstream tasks only if upstream tasks succeed prevents unnecessary task runs, saving cloud costs. Running all tasks daily or disabling dependencies can increase costs. Increasing retries may increase costs due to repeated runs.