PDE Maintaining and Automating Data Workloads Practice Question
Your company uses Cloud Composer to orchestrate a complex data pipeline. You need to ensure that the pipeline can recover from failures and that tasks are retried automatically with exponential backoff. You also want to be alerted if a task fails after all retries. Which combination of features should you implement?
⚠ Common exam trap
It's easy for candidates to confuse Airflow's SLA feature with retry logic; SLA is for monitoring, not retrying.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set retries and retry_exponential_backoff on each task, and use Cloud Monitoring alerts based on Airflow metrics.
Tasks in Airflow can be configured with retries and retry_exponential_backoff to automatically retry failed tasks with increasing delays. Cloud Composer exports metrics to Cloud Monitoring, where you can set up alerts for task failures. This combination provides both automatic recovery and alerting, fulfilling the requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Airflow's SLA feature to trigger retries and send alerts.
Why it's wrong here
Airflow's SLA (Service Level Agreement) feature is used to track task duration and trigger alerts if tasks exceed expected times, but it does not automatically retry tasks. Retries must be configured separately. SLA misses are not the same as failures and do not trigger retries. This option does not meet the retry requirement.
- ✗
Set retries and retry_delay on each task, and configure email alerts on task failure.
Why it's wrong here
Setting retries and retry_delay is correct for retrying tasks, but email alerts alone are not the most robust alerting mechanism in Cloud Composer. Cloud Composer integrates with Cloud Monitoring for alerting, which provides more flexible and centralized alerting. Email alerts require SMTP configuration and may not be as reliable or manageable.
- ✓
Set retries and retry_exponential_backoff on each task, and use Cloud Monitoring alerts based on Airflow metrics.
Why this is correct
Setting retries and retry_exponential_backoff on tasks enables automatic retries with exponential backoff. Cloud Composer exports Airflow metrics to Cloud Monitoring, allowing you to create alerts on task failures or other conditions. This combination provides robust retry logic and centralized alerting, meeting the requirements.
- ✗
Configure a custom operator that implements retry logic and sends alerts via Pub/Sub.
Why it's wrong here
While you can implement custom retry logic in a custom operator, Airflow already provides built-in retry mechanisms with exponential backoff. Using a custom operator adds unnecessary complexity and maintenance. Also, sending alerts via Pub/Sub requires additional integration and is not the standard alerting method in Cloud Composer.
Go deeper
Related to this question
About these practice questions
One of 747 original PDE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This PDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PDE exam.