Cloud Digital Leader Fundamental Cloud Concepts 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.

• ✗

  BigQuery

  Why it's wrong here

  BigQuery is a serverless data warehouse and analytics engine for SQL queries over vast static datasets. Although it supports a streaming ingestion API for loading data in near real-time, it is not designed to execute complex event-stream transformations such as windowed aggregations, joins across streams, or sessionization. It lacks built-in primitives for stream processing like event-time processing and watermarks, so using it as the primary processing engine for streaming pipelines would require additional orchestration and external logic.

• ✗

  Cloud Pub/Sub

  Why it's wrong here

  Pub/Sub is a fully managed, asynchronous messaging service that decouples event producers from consumers and provides durable, at-least-once delivery of messages. It acts as the ingestion backbone for streaming data, but it does not compute or transform the data as it flows; it simply buffers and relays messages according to subscription pull/push models. Consequently, relying on Pub/Sub alone to 'process streaming data' would yield no aggregation, filtering, windowing, or analytics — it only moves the raw events.

• ✗

  Cloud Dataproc

  Why it's wrong here

  Dataproc is a managed service for Apache Hadoop and Spark clusters, which can perform stream processing via Spark Streaming or Structured Streaming using micro-batches. However, that requires you to manage workload scaling, cluster lifecycle, and dependency configuration, and its handling of event-time windows and exactly-once semantics is less integrated than a purpose-built stream processor. For a team needing a seamless, fully managed real-time pipeline with automatic scaling and direct BigQuery integration, Dataproc adds operational overhead and is not as naturally aligned with the event-driven pattern.

• ✓

  Cloud Dataflow

  Why this is correct

  Dataflow is Google's fully managed, unified programming model for batch and stream processing, built on Apache Beam. It provides exactly-once processing guarantees, intelligent watermarks, and automatic handling of out-of-order data, along with built-in windowing and triggering for time-based aggregations. Its native connectors to BigQuery and Pub/Sub allow the team to read streaming events, transform them in real time, and write results directly into BigQuery for analysis without managing any infrastructure.

Go deeper

Related to this question