- A
Use a CoGroupByKey transform to join the incoming stream with a stream from BigQuery.
Why wrong: CoGroupByKey requires both sides to be in a stream; the lookup table is static, not a stream.
- B
Use BigQuery IO to query the table for every incoming message.
Why wrong: This would be very slow and expensive due to many queries.
- C
Use a side input that reads the BigQuery table periodically and caches it.
Side inputs are ideal for distributing a static lookup table to all workers. The data can be refreshed on a schedule.
- D
Use a stateful DoFn and store the lookup in state per key.
Why wrong: Stateful DoFn is for per-key state across events, not for a global lookup table.
Question 33 of 1,000
PDE Ingesting and Processing the Data Practice Question
This PDE practice question tests your understanding of ingesting and processing the data. 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.
You are building a Dataflow pipeline in Python that reads messages from Pub/Sub, enriches them with data from a BigQuery table, and writes the results to BigQuery. The enrichment lookup table is large and changes infrequently. Which approach minimizes cost and latency?
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
✓
Use a side input that reads the BigQuery table periodically and caches it.
Option C is correct because using a side input that periodically reads the BigQuery table and caches it avoids querying BigQuery for every incoming message, which would be prohibitively expensive and high-latency. The side input is refreshed at a configurable interval (e.g., every 10 minutes) via a pipeline option, and the cached data is broadcast to all workers, enabling fast, in-memory lookups without per-element I/O. This approach minimizes cost by reducing BigQuery API calls and minimizes latency by avoiding synchronous queries for each message.
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.
- ✗
Use a CoGroupByKey transform to join the incoming stream with a stream from BigQuery.
Why it's wrong here
CoGroupByKey requires both sides to be in a stream; the lookup table is static, not a stream.
- ✗
Use BigQuery IO to query the table for every incoming message.
Why it's wrong here
This would be very slow and expensive due to many queries.
- ✓
Use a side input that reads the BigQuery table periodically and caches it.
Why this is correct
Side inputs are ideal for distributing a static lookup table to all workers. The data can be refreshed on a schedule.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use a stateful DoFn and store the lookup in state per key.
Why it's wrong here
Stateful DoFn is for per-key state across events, not for a global lookup table.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that querying a database per message is acceptable in streaming pipelines, but the trap here is that candidates overlook the cost and latency implications of per-element I/O, especially with BigQuery's pricing model and query latency.
Detailed technical explanation
How to think about this question
Under the hood, a side input in Apache Beam is implemented as a `PCollectionView` that is materialized as a persistent, immutable map or list broadcast to all parallel workers via the Beam runner's side-input distribution mechanism (e.g., gRPC or shared memory). The periodic refresh is achieved by using `GenerateSequence` with a fixed interval to trigger a `ParDo` that reads the BigQuery table and updates the side input; this avoids stale data while keeping costs low. In a real-world scenario, a large lookup table (e.g., 10 GB) would be cached in memory across workers, and the refresh interval (e.g., 1 hour) would be tuned to balance freshness against memory overhead.
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 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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Ingesting and Processing the Data — study guide chapter
Learn the concepts, then practise the questions
- →
Ingesting and Processing the Data practice questions
Targeted practice on this topic area only
- →
All PDE questions
1,000 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
Related PDE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Designing Data Processing Systems practice questions
Practise PDE questions linked to Designing Data Processing Systems.
Ingesting and Processing the Data practice questions
Practise PDE questions linked to Ingesting and Processing the Data.
Storing the Data practice questions
Practise PDE questions linked to Storing the Data.
Preparing and Using Data for Analysis practice questions
Practise PDE questions linked to Preparing and Using Data for Analysis.
Maintaining and Automating Data Workloads practice questions
Practise PDE questions linked to Maintaining and Automating Data Workloads.
Building and operationalizing data processing systems practice questions
Practise PDE questions linked to Building and operationalizing data processing systems.
Operationalizing machine learning models practice questions
Practise PDE questions linked to Operationalizing machine learning models.
Ensuring solution quality practice questions
Practise PDE questions linked to Ensuring solution quality.
PDE fundamentals practice questions
Practise PDE questions linked to PDE fundamentals.
PDE scenario practice questions
Practise PDE questions linked to PDE scenario.
PDE troubleshooting practice questions
Practise PDE questions linked to PDE troubleshooting.
Practice this exam
Start a free PDE 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 PDE question test?
Ingesting and Processing the Data — This question tests Ingesting and Processing the Data — 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 that reads the BigQuery table periodically and caches it. — Option C is correct because using a side input that periodically reads the BigQuery table and caches it avoids querying BigQuery for every incoming message, which would be prohibitively expensive and high-latency. The side input is refreshed at a configurable interval (e.g., every 10 minutes) via a pipeline option, and the cached data is broadcast to all workers, enabling fast, in-memory lookups without per-element I/O. This approach minimizes cost by reducing BigQuery API calls and minimizes latency by avoiding synchronous queries for each message.
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 →
Last reviewed: Jul 4, 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.