Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions
A financial services company needs a managed data warehouse that can ingest streaming transaction data in real time AND support complex SQL analytics across years of historical data — all without managing any infrastructure. Which Google Cloud product meets both streaming ingest and analytical query requirements in a single serverless service?
⚠ Common exam trap
Google Cloud often tests the misconception that streaming ingest and analytical querying require separate services, leading candidates to overlook BigQuery's unified serverless capability in favor of multi-service architectures like Cloud Bigtable plus BigQuery.
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
✓
BigQuery, which supports real-time streaming ingest via its Storage Write API and large-scale analytical SQL queries across petabytes of data in a single fully managed, serverless service
BigQuery is a fully managed, serverless data warehouse that supports real-time streaming ingest via the Storage Write API and enables complex SQL analytics across petabytes of historical data. This single service meets both requirements without any infrastructure management, unlike the other options that require separate services or manual orchestration.
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 Bigtable for streaming ingest and BigQuery for historical analytics — two separate services
Why it's wrong here
While Cloud Bigtable for streaming ingest and BigQuery for historical analytics can technically work, it introduces a two-service architecture with data synchronization complexity. You would need to export Bigtable data to BigQuery or run periodic pipelines to move data, creating latency and potential inconsistency between the 'real-time' and 'historical' datasets. The question asks for a single service that meets both needs; BigQuery's Storage Write API supports direct real-time streaming ingestion, and its analytical engine queries the same data with sub-second to few-second latencies, eliminating the need for a separate serving system. Bigtable is an OLTP-style NoSQL database optimized for point lookups and high write throughput, not for complex analytical SQL across petabytes, so pairing it with BigQuery is a workaround rather than a native solution.
- ✓
BigQuery, which supports real-time streaming ingest via its Storage Write API and large-scale analytical SQL queries across petabytes of data in a single fully managed, serverless service
Why this is correct
BigQuery meets both requirements natively. The Storage Write API (and legacy streaming API) enables sub-minute data availability for analytics. BigQuery's distributed query engine handles analytical SQL across petabytes. No infrastructure to manage, no separate streaming and analytical systems to maintain.
- ✗
Cloud SQL with read replicas — one instance for streaming writes, read replicas for analytical queries
Why it's wrong here
Cloud SQL is a transactional OLTP database, not a data warehouse. It doesn't scale to petabytes of analytical data and its streaming ingest is limited by transactional throughput constraints. It's not designed for the analytical query complexity described.
- ✗
Cloud Dataflow running continuously to process the stream and load to Persistent Disk for SQL queries
Why it's wrong here
This option conflates stream processing with storage and analytics. Cloud Dataflow is a unified stream and batch processing engine, but Persistent Disk is a block storage service that does not support SQL querying — you would still need a separate query engine (e.g., a cluster or data warehouse) on top of those files. Running Dataflow continuously to write to Persistent Disk also means managing a custom pipeline, dealing with file formats, partitioning, and query orchestration, and you lose the serverless, fully managed scalability that BigQuery provides. BigQuery natively combines streaming ingestion, storage, and SQL analytics in one service, so this architecture is both unnecessarily complex and functionally misaligned with the requirement.
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
BigQuery
BigQuery is a fully managed, serverless data warehouse on Google Cloud that lets you run fast SQL queries on massive datasets without managing any infrastructure.
Key term
Google Cloud
Google Cloud is a suite of cloud computing services offered by Google that provides infrastructure, platform, and software solutions over the internet.
About these practice questions
One of 829 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 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.