Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions
A data engineering team needs to build a pipeline that reads event data from Pub/Sub in real time, applies transformations and aggregations, and writes results to BigQuery — all without managing any infrastructure. Which Google Cloud product is designed for this serverless stream and batch data processing use case?
⚠ Common exam trap
Google Cloud often tests the distinction between a data processing service (Dataflow) and a data ingestion or orchestration service, leading candidates to mistakenly choose BigQuery streaming inserts or Cloud Composer for real-time transformations.
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
✓
Cloud Dataflow, Google Cloud's serverless stream and batch data processing service built on Apache Beam
Cloud Dataflow is Google Cloud's fully managed, serverless service for both stream and batch data processing, built on Apache Beam. It directly reads from Pub/Sub, applies transformations and aggregations using the Beam SDK, and writes the results to BigQuery without requiring any infrastructure management, making it the correct choice for this use case.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Cloud Dataflow, Google Cloud's serverless stream and batch data processing service built on Apache Beam
Why this is correct
Dataflow is exactly right: serverless (no infrastructure management), supports both streaming (from Pub/Sub) and batch, applies transformations and aggregations, and writes natively to BigQuery. The Pub/Sub → Dataflow → BigQuery pattern is one of the most common data engineering pipelines on Google Cloud.
- ✗
Cloud Composer, Google Cloud's managed Apache Airflow service for workflow orchestration
Why it's wrong here
Cloud Composer is a managed Apache Airflow service for orchestrating workflows — scheduling, sequencing, and monitoring tasks like running a Dataflow job or copying data between services. It does not itself execute data transformations or consume Pub/Sub messages; Airflow's operators (e.g., DataflowCreatePythonJobOperator, PubSubPullOperator) only coordinate jobs running on other systems. In a Pub/Sub → BigQuery pipeline, Composer might schedule a Dataflow job to run periodically, but it is not the data processing engine and cannot serve as a serverless streaming pipeline. Additionally, Composer's environment runs on GKE, which requires managing compute resources, so it is not purely serverless in the same sense as Dataflow.
- ✗
Cloud Dataproc, Google Cloud's managed Spark and Hadoop service
Why it's wrong here
Cloud Dataproc requires provisioning and managing a Spark or Hadoop cluster, even if ephemeral, which contradicts the "without managing any infrastructure" requirement in the stem. It is tempting because Dataproc can process streaming data via Spark Streaming, but it is designed for users who need full control over cluster configuration and open-source frameworks, not for a fully serverless pipeline where infrastructure is entirely abstracted away.
- ✗
BigQuery directly, using streaming inserts to load Pub/Sub data in real time
Why it's wrong here
BigQuery's streaming insert API (tabledata.insertAll) can ingest individual rows into a table in near real time, but it is a sink, not a processing engine. To get data from Pub/Sub into BigQuery, something must pull from the Pub/Sub subscription, deserialize the message payload, perform any transformations or aggregations, and then call the insert API or use a write pipeline. Dataflow provides exactly that connector and processing layer; without it, you'd have to build and operate a custom subscriber service, which violates the 'without managing any infrastructure' constraint. Also note that Dataflow can write to BigQuery via the BigQuery I/O connector, which handles batching and exactly-once semantics, whereas raw streaming inserts are at-least-once and have quotas.
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
Cloud Digital Transformation
Key term
Pub/Sub
Pub/Sub is a messaging pattern where publishers send messages without knowing who receives them, and subscribers receive only the messages they care about.
Key term
Data
Data is raw, unprocessed information, like numbers, words, or measurements, that can be stored, processed, and analyzed by computers.
About these practice questions
Courseiva writes every GCDL question from scratch — 829 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.