Quick Answer
The answer is partitioning by date, along with clustering and using materialized views, as these three techniques directly improve BigQuery performance optimization without requiring data migration. Partitioning by date enables the query engine to prune entire partitions that don’t match a date filter, drastically reducing data scanned and accelerating queries—this is a metadata-level reorganization, not a physical move. Clustering further optimizes by sorting data within partitions based on specified columns, while materialized views precompute and cache complex aggregations, all operating on existing storage. On the Google Professional Data Engineer exam, this tests your understanding of cost-efficient, non-disruptive tuning methods; a common trap is suggesting sharding or denormalization, which can increase complexity or storage costs. Remember the memory tip: “Partition, Cluster, Materialize—no migration, just optimization.”
This PDE practice question tests your understanding of designing 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.
A data warehouse in BigQuery is experiencing performance issues. Which THREE techniques can improve performance without moving data to a different storage system?
Partition by date
Partitioning limits scans to relevant partitions.
Cluster by common filter columns
Clustering reduces bytes read for filtered queries.
Use streaming buffer
Why wrong: Streaming buffer is for real-time ingestion, not query performance.
Use BigQuery slots
Why wrong: Slots are for reserved capacity, not performance optimization.
Use materialized views
Materialized views pre-compute aggregations, speeding up queries.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Partition by date
Partitioning by date in BigQuery allows the query engine to prune entire partitions that do not match the query's date filter, significantly reducing the amount of data scanned and improving performance. This technique works without moving data to a different storage system because it is a metadata-level reorganization of the existing table.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Partition by date
Why this is correct
Partitioning limits scans to relevant partitions.
Related concept
Read the scenario before looking for a memorised answer.
Cluster by common filter columns
Why this is correct
Clustering reduces bytes read for filtered queries.
Related concept
Read the scenario before looking for a memorised answer.
Use streaming buffer
Why it's wrong here
Streaming buffer is for real-time ingestion, not query performance.
Use BigQuery slots
Why it's wrong here
Slots are for reserved capacity, not performance optimization.
Use materialized views
Why this is correct
Materialized views pre-compute aggregations, speeding up queries.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Google Cloud often tests the misconception that streaming buffer (Option C) is a performance optimization, when in fact it is designed for near-real-time ingestion and can degrade query performance due to the small, unoptimized files it creates.
Detailed technical explanation
Under the hood, BigQuery's partitioning uses a pseudo-column `_PARTITIONTIME` for ingestion-time partitioning or a specified column for unit-time partitioning, enabling the storage engine to skip entire columnar blocks. In real-world scenarios, a table with 10 TB of data partitioned by day can reduce a query scanning 1 year of data to just 1 day's partition, cutting costs and latency by over 99%.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Designing data processing systems — study guide chapter
Learn the concepts, then practise the questions
Designing data processing systems practice questions
Targeted practice on this topic area only
All PDE questions
499 questions across all exam domains
Google Professional Data Engineer study guide
Full concept coverage aligned to exam objectives
PDE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PDE questions linked to Designing data processing systems.
Practise PDE questions linked to Building and operationalizing data processing systems.
Practise PDE questions linked to Operationalizing machine learning models.
Practise PDE questions linked to Ensuring solution quality.
Practise PDE questions linked to PDE fundamentals.
Practise PDE questions linked to PDE scenario.
Practise PDE questions linked to PDE troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Designing data processing systems — This question tests Designing data processing systems — Read the scenario before looking for a memorised answer..
The correct answer is: Partition by date — Partitioning by date in BigQuery allows the query engine to prune entire partitions that do not match the query's date filter, significantly reducing the amount of data scanned and improving performance. This technique works without moving data to a different storage system because it is a metadata-level reorganization of the existing table.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 30, 2026
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.