The answer is to use a side input from a BigQuery query with a global window and periodic refresh. This approach is correct because it broadcasts the patient records as a static lookup table into memory across all Dataflow workers, eliminating the need for per-element synchronous BigQuery queries that cause pipeline lag. By caching the enrichment data and refreshing it periodically, the pipeline avoids the high latency of repeated BigQuery lookups, which is a common performance bottleneck in streaming enrichment patterns. On the Google Professional Data Engineer exam, this scenario tests your understanding of Beam’s side input semantics versus direct BigQuery IO, with a common trap being to choose a CoGroupByKey or a streaming insert, which would not handle the static lookup efficiently. Remember the memory tip: “Broadcast, don’t fetch per event” — side inputs are ideal for reference data that changes slowly, making them perfect for BigQuery enrichment in Dataflow.
PDE Designing data processing systems Practice Question
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 healthcare company streams patient monitoring data to Cloud Pub/Sub. A Dataflow pipeline reads the stream, enriches with patient records from BigQuery, and writes to Bigtable for real-time queries. The BigQuery lookup is slow and causes pipeline lag. What is the best approach to improve performance?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a side input from a BigQuery query with a global window and periodic refresh.
Option D is correct because using a side input from BigQuery with a global window and periodic refresh allows the Dataflow pipeline to cache the patient records in memory across all workers, avoiding per-element slow lookups. This pattern leverages Beam's side input semantics to broadcast a relatively static lookup table, significantly reducing latency compared to synchronous BigQuery queries for each incoming event.
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.
✗
Increase the number of Dataflow workers and use vertical scaling.
Why it's wrong here
Does not fix the slow lookup.
✗
Use BigQuery's streaming read API in the pipeline.
Why it's wrong here
Streaming reads are still per-element.
✗
Pre-join the data in a batch pipeline and load into Bigtable.
Why it's wrong here
Batch adds latency, not real-time.
✓
Use a side input from a BigQuery query with a global window and periodic refresh.
Why this is correct
Side inputs cache data efficiently.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume that increasing parallelism (Option A) or using a faster read API (Option B) will solve the latency issue, when in fact the core problem is the synchronous per-element lookup pattern, which is best addressed by caching the reference data as a side input.
Detailed technical explanation
How to think about this question
Under the hood, a side input in Apache Beam is materialized as a `PCollectionView`, which is broadcast to all worker tasks via the shuffle or a distributed cache. The periodic refresh is typically implemented using `Window.into(FixedWindows.of(...))` combined with a `Trigger` that fires at a specified interval, allowing the side input to be updated without restarting the pipeline. In real-world scenarios, this pattern is ideal when the lookup table is small enough to fit in memory (e.g., a few hundred thousand rows) and changes infrequently, such as patient demographic data that is updated daily.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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.
Designing data processing systems — This question tests Designing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a side input from a BigQuery query with a global window and periodic refresh. — Option D is correct because using a side input from BigQuery with a global window and periodic refresh allows the Dataflow pipeline to cache the patient records in memory across all workers, avoiding per-element slow lookups. This pattern leverages Beam's side input semantics to broadcast a relatively static lookup table, significantly reducing latency compared to synchronous BigQuery queries for each incoming event.
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.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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.