The correct approach is to write data to a staging BigQuery table, then use a MERGE statement to upsert into the final table. This guarantees exactly-once batch processing because BigQuery load jobs are not idempotent by default—if a batch is re-delivered after a failure, a retried load job will create duplicate rows. By staging the data first and applying a MERGE based on a unique key, you ensure that only new rows are inserted, making the pipeline idempotent even when the same batch is processed multiple times. On the Google Professional Data Engineer exam, this scenario tests your understanding of how to achieve exactly-once semantics in BigQuery without relying on Dataflow’s own deduplication, which is a common trap—candidates often mistakenly choose to use a simple load job with write disposition. The key insight is that BigQuery’s native load operations lack idempotency, so you must decouple ingestion from deduplication. Memory tip: “Stage and Merge—don’t load and pray.”
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 processes patient data using a Dataflow pipeline that reads from Cloud Storage, transforms data, and writes to BigQuery. They need to ensure that the processing is idempotent to handle failures and retries without duplicating records. The data arrives in daily batches and may be re-delivered if earlier processing failed. What approach should they take to guarantee exactly-once processing in BigQuery?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Write data to a staging BigQuery table, then use a MERGE statement to upsert into the final table
Option D is correct because BigQuery load jobs are not idempotent by default; if a load job is retried, it can create duplicate rows. By writing to a staging table first and then using a MERGE statement (or INSERT IF NOT EXISTS) to upsert into the final table, you can deduplicate based on a unique key. This approach guarantees exactly-once semantics even when the same batch is re-delivered, as the MERGE operation will only insert rows that do not already exist in the target table.
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 BigQuery's streaming inserts with InsertId to deduplicate
Why it's wrong here
InsertId dedup only works within a limited window (1 minute) and not for batch loads.
✗
Ingest data via Pub/Sub and use a Dataflow pipeline with exactly-once processing
Why it's wrong here
Pub/Sub does not guarantee exactly-once delivery; duplicates can occur.
✗
Use Dataflow's built-in exactly-once semantics and write to BigQuery via load jobs
Why it's wrong here
Dataflow exactly-once applies to internal processing; BigQuery loads are append; duplicates still possible.
✓
Write data to a staging BigQuery table, then use a MERGE statement to upsert into the final table
Why this is correct
MERGE ensures idempotency by matching on unique keys.
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 Dataflow's exactly-once semantics automatically extend to the sink (BigQuery), but in reality, BigQuery load jobs are not idempotent, so you must implement a deduplication strategy like staging + MERGE to guarantee exactly-once processing.
Detailed technical explanation
How to think about this question
Under the hood, BigQuery load jobs are atomic per job but not idempotent across retries. The MERGE statement in BigQuery uses a unique key (e.g., a composite of batch date and record ID) to conditionally insert rows, effectively providing idempotency. In a real-world scenario, if a daily batch is re-delivered due to a previous failure, the staging table may already contain some or all of the data; the MERGE operation will skip existing rows and only insert new ones, ensuring exactly-once semantics without requiring deduplication logic in the pipeline itself.
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.
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: Write data to a staging BigQuery table, then use a MERGE statement to upsert into the final table — Option D is correct because BigQuery load jobs are not idempotent by default; if a load job is retried, it can create duplicate rows. By writing to a staging table first and then using a MERGE statement (or INSERT IF NOT EXISTS) to upsert into the final table, you can deduplicate based on a unique key. This approach guarantees exactly-once semantics even when the same batch is re-delivered, as the MERGE operation will only insert rows that do not already exist in the target table.
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.