The answer is to use Avro with a schema registry that enforces backward-compatible changes. This strategy is correct because Avro schema evolution relies on a registry to validate that new schemas—such as those adding optional fields with defaults—can be read by consumers using older schemas, ensuring deserialization never breaks. On the Google Professional Data Engineer exam, this scenario tests your understanding of how schema registries manage compatibility rules in streaming pipelines, often appearing as a distractor against options like manual schema updates or ignoring the registry. A common trap is assuming that simply adding optional fields without a registry guarantees backward compatibility, but the registry enforces the rule that new fields must have defaults. Memory tip: think “registry enforces defaults” to remember that backward compatibility requires both the schema tool and the rule enforcement.
PDE Designing data processing systems Practice Question
This PDE practice question tests your understanding of designing data processing systems. 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 gaming company uses Avro schemas for its streaming event data. They anticipate adding new optional fields to events over time. They need to ensure backward compatibility so that existing pipelines continue to work. Which strategy should they adopt?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Avro with a schema registry that enforces backward-compatible changes
Option A is correct because Avro, combined with a schema registry, allows schema evolution with backward compatibility. The registry enforces rules such as adding optional fields with defaults, ensuring that consumers using older schemas can still deserialize new data without breaking. This directly addresses the requirement for existing pipelines to continue working as new optional fields are added.
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.
✓
Use Avro with a schema registry that enforces backward-compatible changes
Why this is correct
Avro's schema evolution rules allow adding optional fields without breaking existing consumers, and a schema registry enables version management.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use JSON instead of Avro and ignore unknown fields
Why it's wrong here
JSON does not enforce schema validation, which can lead to data corruption and lack of structure.
✗
Use Protocol Buffers with breaking changes
Why it's wrong here
Breaking changes would break existing pipelines; Protocol Buffers require careful management of field numbers and compatibility.
✗
Use FlatBuffers for performance
Why it's wrong here
FlatBuffers are designed for memory efficiency but do not natively support schema evolution like Avro.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that any serialization format (like JSON or Protocol Buffers) inherently supports backward compatibility, but the key is the combination of a schema registry with enforced evolution rules, which only Avro explicitly provides in this context.
Detailed technical explanation
How to think about this question
Avro schema evolution works by storing the writer's schema alongside the data; the reader's schema is used to resolve differences via a 'resolution' process that matches fields by name and applies defaults for missing fields. The schema registry (e.g., Confluent Schema Registry) enforces compatibility levels (BACKWARD, FORWARD, FULL) and stores schema versions, preventing incompatible changes from being registered. A real-world scenario is a Kafka-based event pipeline where adding a new optional field with a default value allows old consumers to continue processing without modification.
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.
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: Use Avro with a schema registry that enforces backward-compatible changes — Option A is correct because Avro, combined with a schema registry, allows schema evolution with backward compatibility. The registry enforces rules such as adding optional fields with defaults, ensuring that consumers using older schemas can still deserialize new data without breaking. This directly addresses the requirement for existing pipelines to continue working as new optional fields are added.
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.