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

  Why this is correct

  Pub/Sub is a fully managed, globally distributed messaging and ingestion service built for real-time event streaming. It reliably captures high-volume data from IoT devices via pull or push subscriptions, decouples producers from downstream consumers, and provides at-least-once delivery without requiring any server provisioning. As the entry point in a streaming data pipeline, it buffers and routes telemetry so that downstream systems like Dataflow can process it without data loss.

• ✗

  Cloud Scheduler

  Why it's wrong here

  Cloud Scheduler is a managed cron service that triggers jobs on a fixed schedule, such as invoking an HTTP endpoint or publishing to a Pub/Sub topic at a prescribed time. It is fundamentally batch-oriented, not event-driven: it cannot react to streaming data as it arrives, nor handle unbounded, continuous ingestion from IoT devices. Using it for streaming would require polling, introduce latency, and fail to scale with real-time event rates.

• ✗

  Dataproc

  Why it's wrong here

  Dataproc is a service for running managed Hadoop and Spark clusters against bounded datasets, typically stored in Cloud Storage or BigQuery, as batch analytics workloads. Although Spark Streaming can technically run on a Dataproc cluster, the service itself is not a fully managed streaming pipeline and requires you to provision, monitor, and scale clusters manually. In a cloud-native architecture, it is not the appropriate tool for ingesting and transforming an unbounded, real-time IoT data stream.

• ✓

  Dataflow

  Why this is correct

  Dataflow is a fully managed stream and batch processing engine built on Apache Beam. It can subscribe directly to a Pub/Sub topic, apply windowing, watermarking, and transformations to unbounded data with exactly-once semantics, and write results to BigQuery or other sinks. In this scenario, Dataflow performs the actual processing of the ingested IoT stream, complementing Pub/Sub's role as the real-time message ingestion layer.

• ✗

  Cloud Functions

  Why it's wrong here

  Cloud Functions is a serverless function-as-a-service platform designed for short-lived, event-driven tasks that execute in milliseconds to at most a few minutes. While it can be triggered by Pub/Sub messages, it is not intended to run continuous, stateful streaming pipelines or process high-throughput data with complex transformations. Its timeout limits and lack of built-in streaming state management make it unsuitable for the sustained, precisely ordered processing required by real-time IoT analytics.

Go deeper

Related to this question