PDE Maintaining and Automating Data Workloads Practice Question
A company runs a Dataflow streaming pipeline that processes financial transactions. They need to apply a new transformation that enriches the data with a lookup from Cloud Bigtable without stopping the pipeline. The pipeline must be updated in a way that minimises data loss and preserves exactly-once semantics. What is the recommended approach?
⚠ Common exam trap
PDE often tests the difference between update, drain, and stop — the trap is choosing drain or a parallel pipeline when the question requires preserving exactly-once semantics and minimizing data loss.
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 the Dataflow update option with the same pipeline name and new version, ensuring the transform is backward compatible.
Dataflow supports in-place pipeline updates via the update option, which preserves the pipeline's state (including watermarks and deduplication state) and maintains exactly-once semantics. The new transform must be backward compatible with the existing pipeline's state and schema so that the update can be applied without draining.
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 the Dataflow update option with the same pipeline name and new version, ensuring the transform is backward compatible.
Why this is correct
Dataflow's update option replaces the pipeline definition while retaining the same name and state, so the Bigtable enrichment transform is applied without draining the pipeline, preserving exactly-once semantics provided the new transform stays backward compatible.
- ✗
Drain the pipeline first, then start a new pipeline with the updated code.
Why it's wrong here
Draining stops input processing until the backlog clears, then a new pipeline starts, so the enrichment transformation is not applied to in-flight data and the switch is not seamless. Draining is tempting because it guarantees clean state for incompatible updates, such as changing windowing or key structure.
- ✗
Create a new pipeline in parallel and switch the Pub/Sub subscription to the new pipeline.
Why it's wrong here
Running two pipelines in parallel duplicates processing of the same subscription, so transactions are enriched twice or split inconsistently, violating exactly-once semantics. Parallel pipelines suit A/B testing or migration with separate subscriptions, not an in-place transformation update on one stream.
- ✗
Stop the pipeline, update the code, and restart with a new pipeline name.
Why it's wrong here
Stopping the pipeline discards uncommitted in-flight data and breaks exactly-once continuity, and a new pipeline name abandons the existing state. Stopping is tempting when the update changes pipeline topology incompatibly, but Dataflow's update option replaces the job while preserving state and semantics.
Go deeper
Related to this question
About these practice questions
One of 747 original PDE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
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.