Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
A data engineering team is migrating a legacy data ingestion pipeline to Google Cloud Managed Service for Apache Kafka. They need to enforce strict schema validation to prevent malformed data from breaking downstream structured sinks.
The team has the following requirements for the new pipeline:
Which architecture and configuration strategy should the team implement?
Schema auto-registration is a client-side configuration where a producer application automatically submits and registers a new schema with the schema registry if it determines that the schema does not currently exist under the target subject.
Enabling auto-registration directly violates the requirement for a production-ready schema deployment strategy. Allowing producers to register schemas dynamically at runtime introduces significant risk, as unexpected or erroneous schema changes can bypass governance and immediately break downstream structured sinks.
The team was operating in an isolated development or rapid-prototyping environment where strict governance is not yet required, and developer velocity is prioritized over pipeline stability.
JSON Schema is a declarative vocabulary that allows you to annotate and validate JSON documents. It provides a standard way to describe the expected structure, data types, and constraints of JSON data.
While JSON is a ubiquitous data format, the schema registry API for Managed Service for Apache Kafka does not support JSON formats. Therefore, attempting to use JSON Schema natively with this specific registry will fail.
The team was utilizing a custom, external schema validation service that specifically required JSON, rather than relying on the natively integrated Managed Service for Apache Kafka schema registry.
This architecture utilizes Apache Avro, a compact binary serialization format, integrated with a schema registry. It enforces backwards-compatibility rules and relies on a centralized CI/CD process to register schemas, explicitly disabling the ability for producer clients to register schemas on the fly.
This is the only approach that selects a natively supported serialization format, applies the correct compatibility direction for the stated requirement, and adheres to the best practice of disabling client-side schema auto-registration in production environments.
Forwards-compatibility is a schema evolution strategy that ensures consumer applications configured with an older schema version can successfully read and process data produced with a newer schema version.
The scenario explicitly requires that "consumer applications configured with updated schemas can still read data produced with older schema versions." This is the exact definition of backwards-compatibility, not forwards-compatibility.
The deployment strategy required upgrading all producer applications to emit new data structures before the team was allowed to update the downstream consumer applications.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated