Google Cloud Professional Cloud Architect · Free practice question 9 of 12
Managed Service for Apache Airflow for complex DAGs
Ravensworth Media already maintains 220 Apache Airflow DAGs on a self-managed server that schedules BigQuery, Spark and external API tasks with complex dependencies. The deciding constraint is to keep the DAG code and stop operating Airflow. What should the architect recommend?
- A.Cloud Scheduler cron jobs replacing the DAGs
- B.Managed Service for Apache Airflow (formerly Cloud Composer)
- C.A rewrite of each DAG as a Workflows definition triggered by Cloud Scheduler
- D.A larger Compute Engine VM for the Airflow server
Show answer and explanation
Correct answer: B. Managed Service for Apache Airflow (formerly Cloud Composer)
Why: Managed Service for Apache Airflow runs Apache Airflow for you, so existing DAGs move with little change and the team no longer operates the scheduler and workers. Rewriting 220 DAGs in Workflows discards existing code. Cron jobs cannot express complex dependencies, and a larger VM keeps the operational burden.
More free Google Cloud Professional Cloud Architect questions
- Config Sync GitOps across a cluster fleet
- Chirp speech model for call transcription
- AlloyDB read pools for read scaling
- VM Manager OS patch management
- BigQuery long-term storage pricing
- Feature Store against training-serving skew
- Autoclass for unpredictable object access
- Workflows orchestrating serverless steps
- Cloud DNS failover routing policy
- Datastream change data capture into BigQuery
- Cloud Asset Inventory IAM policy analysis