The answer is Cloud Bigtable. This fully managed NoSQL database is designed for high-throughput, low-latency time-series data, making it the ideal choice for storage for IoT time-series data when the primary query pattern involves device-time range queries. By designing a row key like device_id plus timestamp, Bigtable enables efficient range scans across millions of devices generating 2 TB per month, retrieving all readings for a specific device over a time range such as the last 24 hours without costly full table scans. On the Google Professional Data Engineer exam, this question tests your understanding of workload-specific storage selection, often contrasting Bigtable with Cloud Storage (too slow for sub-second queries) or BigQuery (optimized for analytics, not point lookups). A common trap is choosing Cloud Spanner for its strong consistency, but Bigtable’s simpler key-value model and native support for time-range scans are better suited here. Memory tip: think “Bigtable for big time-series tables” — if your query is “device + time range,” Bigtable is the right table.
PDE Practice Question: Building and operationalizing data processing systems
This PDE practice question tests your understanding of building and operationalizing data processing systems. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your team needs to store time-series data from millions of IoT devices. Each device sends a reading every 5 minutes, and the total data volume is about 2 TB per month. The most common query pattern is retrieving all readings for a specific device over a time range (e.g., last 24 hours). Which storage service should you choose?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Cloud Bigtable
Cloud Bigtable is a fully managed, scalable NoSQL database designed for high-throughput, low-latency time-series data. It supports single-row key lookups and range scans, making it ideal for retrieving all readings for a specific device over a time range (e.g., last 24 hours) from millions of IoT devices generating 2 TB/month. Its row key design (e.g., device_id + timestamp) enables efficient time-range queries without full table scans, unlike object storage or analytical warehouses.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 Storage (objects per device per time interval)
Why it's wrong here
Object storage has high latency per request and not suitable for frequent single-device queries.
✗
BigQuery
Why it's wrong here
BigQuery is optimized for large analytical aggregations, not for thousands of small point queries per second.
✓
Cloud Bigtable
Why this is correct
Bigtable is ideal for time-series data with high write throughput and row-key-based range scans for device/time.
Related concept
Read the scenario before looking for a memorised answer.
✗
Cloud Spanner
Why it's wrong here
Spanner is a globally distributed relational database; it can handle time-series but at higher cost and with complexity.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that BigQuery is suitable for operational, low-latency time-series queries, but the trap here is that BigQuery is an analytical warehouse optimized for large-scale batch queries, not for repeated, sub-second per-device range scans, which is a classic NoSQL (Bigtable) workload.
Detailed technical explanation
How to think about this question
Cloud Bigtable uses a distributed, sorted key-value store based on Google's Chubby and Bigtable papers, where row keys are stored in lexicographic order. By designing a row key as `device_id#reverse_timestamp`, you can efficiently scan all readings for a device over a time range using a single prefix scan, leveraging the underlying SSTable structure and Bloom filters for fast lookups. In real-world IoT deployments, this pattern supports millions of writes per second and sub-10ms latency for time-range queries, which is critical for real-time monitoring and alerting.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Building and operationalizing data processing systems — This question tests Building and operationalizing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Cloud Bigtable — Cloud Bigtable is a fully managed, scalable NoSQL database designed for high-throughput, low-latency time-series data. It supports single-row key lookups and range scans, making it ideal for retrieving all readings for a specific device over a time range (e.g., last 24 hours) from millions of IoT devices generating 2 TB/month. Its row key design (e.g., device_id + timestamp) enables efficient time-range queries without full table scans, unlike object storage or analytical warehouses.
What should I do if I get this PDE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PDE 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 PDE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.