Google Cloud Professional Cloud Architect · Free practice question 8 of 12
Workflows orchestrating serverless steps
Larchmont Insurance's claim intake calls four services in order: a Cloud Run validation service, a Document AI processor, a fraud-scoring API and a notification service, with retries and a conditional branch for high-risk claims. The process must run every 15 minutes. Which TWO services should the architect combine? (Select TWO.)
- A.Managed Service for Apache Airflow (formerly Cloud Composer) with an environment for one small process
- B.Workflows to define the ordered steps, retries and conditional branch
- C.Dataflow streaming pipelines for each step of the claim process
- D.Cloud Tasks queues chained manually between each pair of services
- E.Cloud Scheduler to start the workflow every 15 minutes
Show answer and explanation
Correct answers: B. Workflows to define the ordered steps, retries and conditional branch · E. Cloud Scheduler to start the workflow every 15 minutes
Why: Workflows orchestrates service and API calls with built-in retries, conditions and error handling, and Cloud Scheduler can trigger a workflow on a fixed schedule. Chaining Cloud Tasks queues spreads the logic across services and makes the flow hard to follow. Dataflow is for data processing pipelines, and a managed Airflow environment is heavyweight for a single small process.
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
- Managed Service for Apache Airflow for complex DAGs
- Cloud DNS failover routing policy
- Datastream change data capture into BigQuery
- Cloud Asset Inventory IAM policy analysis