Question 33 of 503
Design and implement database schemasmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to partition by date and cluster by sensor_id with a timestamp column. This strategy is most cost-effective for IoT time-series analytics because partitioning by date (using ingestion or event time) automatically prunes irrelevant data for hourly aggregation queries, while clustering by sensor_id physically co-locates rows for the same sensor, drastically reducing the data scanned when filtering on specific devices. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding that partitioning should align with the primary query filter (time range), while clustering optimizes secondary filters like sensor_id. A common trap is choosing partition by sensor_id, which would create too many small partitions and degrade write throughput, or using integer range partitioning for dates, which lacks the automatic time-based pruning. Memory tip: partition the time, cluster the thing.

PCDE Design and implement database schemas Practice Question

This PCDE practice question tests your understanding of design and implement database schemas. 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 team is designing a BigQuery schema for time-series analytics on IoT sensor data. They expect high write throughput and queries that aggregate data by hour. Which partitioning and clustering strategy is most cost-effective?

Question 1mediummultiple choice
Full question →

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

Partition by date and cluster by sensor_id with a timestamp column.

Partitioning by date (e.g., ingestion time or event date) is standard for time-series. Clustering by sensor_id helps queries that filter on specific sensors. Option C (partition by date, cluster by sensor_id) is best. Option A uses ingestion time, which may not align with event time. Option B partitions by sensor_id, creating many partitions. Option D (integer range) is not suitable for dates.

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.

  • Partition by ingestion_time and cluster by sensor_id.

    Why it's wrong here

    Ingestion time may not correspond to event time, and writes are append-only, causing hotspotting.

  • Use integer range partitioning on sensor_id.

    Why it's wrong here

    Integer range partitioning is not optimal for date-based queries.

  • Partition by date and cluster by sensor_id with a timestamp column.

    Why this is correct

    Date-based partitioning efficiently prunes scans; clustering by sensor_id further reduces data read.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Partition by sensor_id and cluster by timestamp.

    Why it's wrong here

    Partitioning by sensor_id creates many small partitions, increasing cost and management.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Detailed technical explanation

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

What to study next

Got this wrong? Here's your next step.

Identify which PCDE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

Related practice questions

Related PCDE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PCDE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PCDE question test?

Design and implement database schemas — This question tests Design and implement database schemas — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Partition by date and cluster by sensor_id with a timestamp column. — Partitioning by date (e.g., ingestion time or event date) is standard for time-series. Clustering by sensor_id helps queries that filter on specific sensors. Option C (partition by date, cluster by sensor_id) is best. Option A uses ingestion time, which may not align with event time. Option B partitions by sensor_id, creating many partitions. Option D (integer range) is not suitable for dates.

What should I do if I get this PCDE question wrong?

Identify which PCDE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

This PCDE 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 PCDE exam.