Question 352 of 1,000
hardMultiple ChoiceObjective-mapped

Dataflow BigQuery Write Errors: Dead-Letter Queue Strategy

This PDE practice question tests your understanding of bigquery sink write disposition. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: bigQuery sink write disposition. 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 company runs a Dataflow streaming pipeline that reads from Pub/Sub and writes to BigQuery. They experience a sudden spike in data volume causing BigQuery write throughput to be exceeded, resulting in errors. Which strategy should they implement to handle this gracefully?

Quick Answer

The correct answer is to use a BigQuery sink with 'FAIL_FAST' error handling and set a dead-letter queue for failed writes. This strategy is essential because when a sudden spike in data volume causes BigQuery write throughput to be exceeded, the 'FAIL_FAST' mode immediately surfaces the errors rather than silently retrying, allowing the pipeline to route those problematic records to a separate Pub/Sub topic—the dead-letter queue—for later reprocessing. This prevents data loss and avoids backpressure that could stall the entire streaming pipeline. On the Google Professional Data Engineer exam, this scenario tests your understanding of error handling in Dataflow’s BigQuery I/O connector, a common trap being to confuse retry logic with error routing; many candidates mistakenly choose options that change write mode or disable table creation, which do not address throughput errors. Remember the memory tip: “Fail fast, queue the rest”—if BigQuery can’t keep up, let the errors flow to a dead-letter topic rather than holding up the stream.

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 BigQuery sink with 'WRITE_APPEND' mode and set 'writeDisposition' to 'WRITE_APPEND'.

Option B is correct because setting 'WRITE_APPEND' mode and 'writeDisposition' to 'WRITE_APPEND' configures the BigQuery sink to append data to the existing table. The default error handling in the BigQuery sink includes automatic retries and backpressure, which gracefully handle spikes in data volume. Options A, C, and D are incorrect because: A uses FAIL_FAST error handling, which fails the pipeline on write errors and does not route to a dead-letter queue; C truncates the table; D prevents table creation.

Key principle: BigQuery sink write disposition

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 BigQuery sink with 'FAIL_FAST' error handling and set a dead-letter queue for failed writes.

    Why it's wrong here

    Incorrect. FAIL_FAST error handling causes the pipeline to fail when write throughput is exceeded, rather than routing failed writes to a dead-letter queue. The correct approach for a dead-letter queue is to use WriteResult to retrieve failed inserts.

  • Use a BigQuery sink with 'WRITE_APPEND' mode and set 'writeDisposition' to 'WRITE_APPEND'.

    Why this is correct

    Correct. WRITE_APPEND mode ensures data is appended, and the BigQuery sink's default retry and backpressure mechanisms handle spikes gracefully without requiring special error handling.

    Related concept

    BigQuery sink write disposition

  • Use a BigQuery sink with 'WRITE_TRUNCATE' mode.

    Why it's wrong here

    Incorrect. WRITE_TRUNCATE mode overwrites the entire table, which is not appropriate for handling a spike in data volume and would cause data loss.

  • Use a BigQuery sink with 'CREATE_NEVER' write method.

    Why it's wrong here

    Incorrect. CREATE_NEVER write method prevents creating a new table if it does not exist, but does not address write throughput errors.

Common exam traps

Common exam trap: answer the scenario, not the keyword

FAIL_FAST error handling does not send failed writes to a dead-letter queue; it terminates the pipeline. Always use WriteResult to capture failures for dead-letter processing.

Detailed technical explanation

How to think about this question

Treat this as a scenario question. Identify the problem, the constraint, and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • BigQuery sink write disposition
  • FAIL_FAST error handling
  • Dead-letter queue

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

BigQuery sink write disposition

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. BigQuery sink write disposition Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

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.

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?

BigQuery sink write disposition

What is the correct answer to this question?

The correct answer is: Use a BigQuery sink with 'WRITE_APPEND' mode and set 'writeDisposition' to 'WRITE_APPEND'. — Option B is correct because setting 'WRITE_APPEND' mode and 'writeDisposition' to 'WRITE_APPEND' configures the BigQuery sink to append data to the existing table. The default error handling in the BigQuery sink includes automatic retries and backpressure, which gracefully handle spikes in data volume. Options A, C, and D are incorrect because: A uses FAIL_FAST error handling, which fails the pipeline on write errors and does not route to a dead-letter queue; C truncates the table; D prevents table creation.

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

Review bigQuery sink write disposition, then practise related PDE questions on the same topic to reinforce the concept.

What is the key concept behind this question?

BigQuery sink write disposition

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

Keep practising

More PDE practice questions

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 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.