You work for a company that operates an ecommerce website. You are developing a new integration that will manage all order fulfillment steps after orders are placed. You have created multiple Cloud Ru

Question

Options

• AUse Workflows to call the functions, and use callbacks to handle the execution logic.
• BUse Workflows to call the functions, and use conditional jumps to handle the execution logic.
• CUse Cloud Composer to call the functions, and use an Apache Airflow HTTP operator to handle
• DUse Cloud Composer to call the functions, and use an Apache Airflow operator to handle the

• A
  4% (1)
• B
  77% (20)
• C
  12% (3)
• D
  8% (2)

Explanation

Google Cloud Workflows is the right orchestration tool here because it is serverless, low-latency, and natively designed to call HTTP endpoints (like Cloud Run functions) and make branching decisions based on their outputs. Option B (Workflows with conditional jumps) directly supports evaluating function outputs and routing execution accordingly - exactly what the question requires. Option A (Workflows with callbacks) is designed for long-running waits on external events, not inline conditional logic, which adds unnecessary latency. Options C and D use Cloud Composer (managed Apache Airflow), which is a much heavier, higher-latency platform built for batch data pipelines - not for low-latency transactional workflows. Airflow's scheduler overhead makes it a poor fit when minimizing latency is a priority.

No community discussion yet for this question.