The answer is that the pipeline code was changed to send an integer for the last_name field. This is correct because BigQuery enforces strict type checking at ingestion time; when a Dataflow pipeline attempts to write an integer into a STRING column, the write fails due to a schema mismatch, as BigQuery does not automatically coerce incompatible data types. On the Google Professional Data Engineer exam, this scenario tests your understanding of how Dataflow and BigQuery handle schema validation, often appearing as a trap where candidates assume schema evolution or transient errors are the cause. A common memory tip is to remember that BigQuery is strict about data types at write time—unlike some databases that allow implicit conversion, BigQuery will reject a Dataflow write failure schema mismatch if the source data type changes. Keep this in mind: if a pipeline was working and suddenly fails, always check the data types being sent before blaming the schema.
PDE Practice Question: Building and operationalizing data processing systems
This PDE practice question tests your understanding of building and operationalizing 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.
Exhibit
Refer to the exhibit.
Error log from Dataflow job:
"""
Workflow failed. Causes: S3D3: BigQueryIO.Write/BatchLoads/Loads/AllocateLoadTable/ParDo(AllocateLoadTable) failed.
org.apache.beam.sdk.io.gcp.bigquery.BigQueryIO$Write$BigQueryWriteException: BigQuery insertion failed: Response JSON: {
"error": {
"errors": [
{
"domain": "global",
"reason": "invalid",
"message": "Provided Schema does not match Table employee_records. Field last_name has type STRING but provided type INTEGER"
}
],
"code": 400,
"message": "Provided Schema does not match Table employee_records. Field last_name has type STRING but provided type INTEGER"
}
}
"""
Refer to the exhibit. A Dataflow pipeline writes to BigQuery table employee_records. The pipeline was working yesterday but fails today. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Refer to the exhibit.
Error log from Dataflow job:
"""
Workflow failed. Causes: S3D3: BigQueryIO.Write/BatchLoads/Loads/AllocateLoadTable/ParDo(AllocateLoadTable) failed.
org.apache.beam.sdk.io.gcp.bigquery.BigQueryIO$Write$BigQueryWriteException: BigQuery insertion failed: Response JSON: {
"error": {
"errors": [
{
"domain": "global",
"reason": "invalid",
"message": "Provided Schema does not match Table employee_records. Field last_name has type STRING but provided type INTEGER"
}
],
"code": 400,
"message": "Provided Schema does not match Table employee_records. Field last_name has type STRING but provided type INTEGER"
}
}
"""
A
The pipeline dropped the last_name field entirely.
Why wrong: Dropping a field would cause a missing field error, not type mismatch.
B
The pipeline code was changed to send an integer for the last_name field.
The error clearly states that an integer was provided for a string field.
C
The BigQuery table quota was exceeded.
Why wrong: Quota errors have different error messages.
D
The BigQuery table schema was changed from STRING to INTEGER for last_name.
Why wrong: If the table changed, the error would indicate that the table expects INTEGER, but it says provided type INTEGER.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The pipeline code was changed to send an integer for the last_name field.
Option B is correct because if the pipeline code was changed to send an integer for the last_name field, BigQuery will reject the write due to a schema mismatch. BigQuery enforces strict type checking at ingestion time; an integer value cannot be written into a STRING column unless the schema explicitly allows coercion. Since the pipeline was working yesterday, the most likely change is in the data type being sent, not the schema itself.
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.
✗
The pipeline dropped the last_name field entirely.
Why it's wrong here
Dropping a field would cause a missing field error, not type mismatch.
✓
The pipeline code was changed to send an integer for the last_name field.
Why this is correct
The error clearly states that an integer was provided for a string field.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The BigQuery table quota was exceeded.
Why it's wrong here
Quota errors have different error messages.
✗
The BigQuery table schema was changed from STRING to INTEGER for last_name.
Why it's wrong here
If the table changed, the error would indicate that the table expects INTEGER, but it says provided type INTEGER.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that schema changes in BigQuery are the primary cause of pipeline failures, when in fact the most common cause is a code change that alters the data type of a field being written, especially in streaming or batch pipelines where schema enforcement is strict.
Detailed technical explanation
How to think about this question
BigQuery uses a strongly typed schema where each column has a defined data type (e.g., STRING, INTEGER, FLOAT). When writing data via the Dataflow pipeline (using the Apache Beam BigQueryIO connector), the SDK performs a schema validation against the table's existing schema. If a value type does not match the column type, the write fails with a 'java.lang.IllegalArgumentException: Schema mismatch' or similar error. In real-world scenarios, this often occurs when a developer inadvertently changes a data transformation step (e.g., casting a string to an integer) without updating the target table schema.
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.
Building and operationalizing data processing systems — This question tests Building and operationalizing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The pipeline code was changed to send an integer for the last_name field. — Option B is correct because if the pipeline code was changed to send an integer for the last_name field, BigQuery will reject the write due to a schema mismatch. BigQuery enforces strict type checking at ingestion time; an integer value cannot be written into a STRING column unless the schema explicitly allows coercion. Since the pipeline was working yesterday, the most likely change is in the data type being sent, not the schema itself.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.