Cloud Digital Leader Google Cloud Products and Services Practice Question
A data engineering team needs to process streaming data from IoT devices, perform real-time transformations, and load the results into BigQuery for analysis. Which TWO Google Cloud services should they use?
⚠ Common exam trap
GCDL often tests whether candidates confuse Dataproc (batch Spark/Hadoop) with Dataflow (streaming Beam), so picking Dataproc for 'real-time transformations' is the classic wrong answer.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Pub/Sub
Pub/Sub (A) is correct because it is Google Cloud's fully managed, globally scalable messaging service designed to ingest high-volume streaming data from IoT devices, decoupling producers from consumers. Dataflow (D) is correct because it provides a fully managed Apache Beam runner for real-time (streaming) transformations with exactly-once processing, and it has a native BigQueryIO connector for loading results into BigQuery. Together, Pub/Sub ingests the IoT stream and Dataflow transforms it and writes to BigQuery. Cloud Scheduler (B) is only a cron-based job trigger, not a streaming data processor. Dataproc (C) is a managed Hadoop/Spark service better suited to batch processing rather than low-latency streaming pipelines. Cloud Functions (E) is an event-driven serverless compute service for short-lived functions, not a scalable stream-processing framework for continuous IoT transformations.
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.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Data Security: Encryption and Access Controls
Key term
Event
An event is any identifiable occurrence or action in a computer system, network, or application that can be logged, monitored, or analyzed for security or operational purposes.
Key term
Cloud Functions
Cloud Functions are serverless compute services that let you run single-purpose code in response to events without managing servers.
About these practice questions
One of 848 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.