- A
Raise an exception in the pipeline and stop processing
Why wrong: Stopping the pipeline on malformed data would cause data loss for valid messages.
- B
Use retry logic in the pipeline to reprocess malformed messages indefinitely
Why wrong: Indefinite retries may cause backpressure and do not fix malformed data.
- C
Implement a dead letter sink to store malformed messages for later analysis
Dead letter sinks store problematic records without blocking the pipeline, enabling later inspection and reprocessing.
- D
Discard malformed messages and log an error
Why wrong: Discarding data loses potentially recoverable information and does not allow for reprocessing.
Question 718 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.
A media company streams real-time viewer data from Pub/Sub to BigQuery using a Dataflow pipeline. They need to handle occasional malformed messages without losing valid data. Which pattern should they implement?
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
✓
Implement a dead letter sink to store malformed messages for later analysis
Option C is correct because a dead letter sink (e.g., a separate Pub/Sub topic or a BigQuery error table) allows the Dataflow pipeline to route malformed messages out of the main processing path while continuing to process valid data. This pattern ensures no valid data is lost and provides a durable location for later analysis or reprocessing of the malformed records, which is essential for streaming pipelines where data quality issues are intermittent.
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.
- ✗
Raise an exception in the pipeline and stop processing
Why it's wrong here
Stopping the pipeline on malformed data would cause data loss for valid messages.
- ✗
Use retry logic in the pipeline to reprocess malformed messages indefinitely
Why it's wrong here
Indefinite retries may cause backpressure and do not fix malformed data.
- ✓
Implement a dead letter sink to store malformed messages for later analysis
Why this is correct
Dead letter sinks store problematic records without blocking the pipeline, enabling later inspection and reprocessing.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Discard malformed messages and log an error
Why it's wrong here
Discarding data loses potentially recoverable information and does not allow for reprocessing.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the dead letter pattern to see if candidates understand that streaming pipelines must handle bad data gracefully without stopping or losing valid records, and the trap is that many candidates choose retry logic (Option B) because they confuse transient errors with permanent data quality issues.
Detailed technical explanation
How to think about this question
In Dataflow, a dead letter sink is typically implemented using a side output (via ParDo with ProcessContext.output() and a tagged output) that writes malformed records to a separate Pub/Sub topic or a BigQuery table. This pattern leverages Beam's robust error handling to separate business logic from error routing, and the dead letter records can later be replayed or analyzed using Cloud Logging or a separate Dataflow job. A real-world scenario involves JSON parsing failures where a field is missing or has an incorrect type; the dead letter sink captures the raw payload and the error reason, enabling downstream teams to fix the source or reprocess the data without impacting the main pipeline's throughput.
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.
- →
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: Implement a dead letter sink to store malformed messages for later analysis — Option C is correct because a dead letter sink (e.g., a separate Pub/Sub topic or a BigQuery error table) allows the Dataflow pipeline to route malformed messages out of the main processing path while continuing to process valid data. This pattern ensures no valid data is lost and provides a durable location for later analysis or reprocessing of the malformed records, which is essential for streaming pipelines where data quality issues are intermittent.
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.