Cloud Digital Leader Google Cloud Products and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Pub/Sub, Cloud Functions, Cloud SQL

  Why it's wrong here

  Pub/Sub + Cloud Functions + Cloud SQL fails on two fronts. Cloud Functions is a serverless compute service optimized for short-lived, event-driven single-event processing; it has no built-in state management or windowing to aggregate a continuous stream of events over time. Cloud SQL is a relational OLTP database designed for transactional workloads and modest scale; it is not architected for high-ingest-rate analytics or the append-heavy, columnar-scan patterns needed for real-time dashboards, and it would become a bottleneck under sustained streaming load.

• ✗

  Cloud Storage, Dataflow, Cloud SQL

  Why it's wrong here

  Cloud Storage + Dataflow + Cloud SQL misuses the ingestion layer. Cloud Storage is object storage for immutable, batch-oriented files (e.g., CSV, Parquet); it is not a low-latency streaming ingest service, and relying on it for a click stream would add minutes-to-hours of latency from object finalization and notification. While Dataflow can read from Cloud Storage, that is a batch or micro-batch pattern, not true streaming; Cloud SQL again is not suited for the query patterns of a live analytics dashboard, making the end-to-end pipeline both slow and analytically limited.

• ✓

  Pub/Sub, Dataflow, BigQuery

  Why this is correct

  Pub/Sub + Dataflow + BigQuery is the correct streaming pipeline. Pub/Sub is a fully managed, durable message ingestion service that decouples producers from consumers and supports exactly-once delivery semantics in combination with Dataflow. Dataflow (Apache Beam runner) provides unified batch and stream processing with built-in windowing, stateful aggregations, and exactly-once guarantees, enabling real-time click aggregation. BigQuery is a serverless, columnar data warehouse optimized for scanning large volumes of data with high concurrency, making it ideal for serving a live dashboard with sub-second SQL queries on aggregated results.

• ✗

  Pub/Sub, Cloud Functions, BigQuery

  Why it's wrong here

  Pub/Sub + Cloud Functions + BigQuery is closer but still inappropriate. Cloud Functions is triggered per message and processes each event in isolation; it cannot natively maintain state across multiple events, so performing a continuous aggregation (e.g., counting clicks over a 5-minute window) requires external state storage and complex orchestration, defeating the purpose of a managed streaming pipeline. Also, Cloud Functions has a maximum execution timeout (typically 9-10 minutes) and is not designed for high-throughput, sustained data transformations, even though BigQuery as the sink is a good choice. The missing Dataflow layer leaves a gap for reliable, stateful stream processing.

Go deeper

Related to this question