You are implementing several batch jobs that must be executed on a schedule. These jobs have many interdependent steps that must be executed in a specific order. Portions of the jobs involve…

Question

Options

• ACloud Scheduler
• BCloud Dataflow
• CCloud Functions
• DCloud Composer

• A
  2% (1)
• B
  15% (6)
• C
  7% (3)
• D
  76% (31)

Explanation

Cloud Composer (managed Apache Airflow) is purpose-built for exactly this scenario: orchestrating complex, multi-step workflows with dependencies, supporting shell scripts, Hadoop, and BigQuery operators natively, with built-in retry logic and scheduling for long-running jobs.

Why the distractors are wrong:

• A. Cloud Scheduler is just a cron trigger - it can kick off a single job but cannot manage step dependencies, retries, or multi-system orchestration.
• B. Cloud Dataflow is a data processing service (Apache Beam) for stream/batch data pipelines, not a general-purpose workflow orchestrator across heterogeneous systems.
• C. Cloud Functions is event-driven serverless compute with strict execution time limits (max 60 min), making it unsuitable for multi-hour jobs with complex dependency graphs.

Memory tip: Think of Cloud Composer as the "conductor" of an orchestra - it doesn't play any instruments itself, but it coordinates when and in what order each section (shell scripts, Hadoop, BigQuery) performs. When a question mentions interdependent steps, mixed systems, and retry logic, that's the Composer pattern.

No community discussion yet for this question.