The answer is to implement a dead-letter queue in the Dataflow pipeline to store failed records for later analysis, alongside using Cloud Pub/Sub for decoupled ingestion and enabling robust error handling with side outputs. This approach directly addresses dataflow pipeline reliability when dealing with malformed data because it isolates corrupt JSON records from the healthy processing stream, preventing a single bad file from crashing the entire job. On the Google Professional Data Engineer exam, this scenario tests your understanding of fault-tolerant pipeline design, often appearing as a multi-select question where the trap is choosing to simply log errors and continue—which loses data—rather than persisting failures for reprocessing. A common memory tip is to think of the pipeline as a factory conveyor belt: you don’t stop the line for a broken widget; you kick it to a “dead-letter bin” for later inspection.
PDE Designing data processing systems Practice Question
This PDE practice question tests your understanding of designing data processing systems. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 data pipeline reads thousands of JSON files from Cloud Storage, processes them with Cloud Dataflow, and writes to BigQuery. The pipeline sometimes fails because of malformed JSON records. Which three steps should the data engineering team take to improve pipeline reliability? (Choose THREE.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Integrate Cloud Pub/Sub as an intermediary to buffer and allow message retry
Option A is correct because integrating Cloud Pub/Sub as an intermediary decouples the ingestion of JSON files from the Dataflow pipeline. Pub/Sub provides at-least-once delivery and automatic retries for messages that are not acknowledged, which buffers against transient failures and malformed records. This allows the pipeline to pull messages at its own pace and retry processing without losing data.
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.
✓
Integrate Cloud Pub/Sub as an intermediary to buffer and allow message retry
Why this is correct
Pub/Sub can retry delivery of messages, improving reliability.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a try-catch block in the pipeline to retry processing failed records
Why it's wrong here
Retrying will not fix malformed JSON; must be handled differently.
✗
Create a Cloud Monitoring alert on pipeline failures
Why it's wrong here
Alerts only notify; do not improve pipeline reliability directly.
✓
Add schema validation before processing to reject invalid JSON records
Why this is correct
Early validation prevents malformed data from entering processing.
Related concept
Read the scenario before looking for a memorised answer.
✓
Implement a dead-letter queue in the Dataflow pipeline to store failed records for later analysis
Why this is correct
Catches malformed records without failing the entire pipeline.
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 confuse reactive monitoring (Option C) with proactive reliability improvements, or they assume a simple try-catch block (Option B) is sufficient in a distributed processing framework like Dataflow, where fault tolerance requires persistent retry mechanisms and dead-letter queues.
Detailed technical explanation
How to think about this question
Under the hood, Cloud Pub/Sub uses a pull-based subscription model where the Dataflow pipeline acknowledges messages only after successful processing. If a message is malformed and the pipeline fails to process it, the message is not acknowledged and is redelivered after the acknowledgment deadline (default 10 seconds). This retry mechanism, combined with a dead-letter queue (Option E), ensures that malformed records are isolated and can be analyzed without blocking the main pipeline. In real-world scenarios, this pattern is critical for high-throughput pipelines where JSON schemas evolve or external data sources introduce unexpected formats.
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: Integrate Cloud Pub/Sub as an intermediary to buffer and allow message retry — Option A is correct because integrating Cloud Pub/Sub as an intermediary decouples the ingestion of JSON files from the Dataflow pipeline. Pub/Sub provides at-least-once delivery and automatic retries for messages that are not acknowledged, which buffers against transient failures and malformed records. This allows the pipeline to pull messages at its own pace and retry processing without losing data.
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.