professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
Use Apache Avro for data serialization. Configure the schema registry subject with forwards-compatibility rules. Pre-register all schema updates through a CI/CD pipeline and disable schema auto-registration in the producer clients.
Use JSON Schema for data serialization. Configure the schema registry subject with backwards-compatibility rules. Pre-register all schema updates through a CI/CD pipeline and disable schema auto-registration in the producer clients.
Use Apache Avro for data serialization. Configure the schema registry subject with backwards-compatibility rules. Pre-register all schema updates through a CI/CD pipeline and disable schema auto-registration in the producer clients.
Use Protocol Buffers (Protobuf) for data serialization. Configure the schema registry subject with backwards-compatibility rules. Enable schema auto-registration in the producer clients to ensure new fields are immediately available to downstream sinks.
Use Apache Avro for data serialization. Configure the schema registry subject with forwards-compatibility rules. Pre-register all schema updates through a CI/CD pipeline and disable schema auto-registration in the producer clients.
Use JSON Schema for data serialization. Configure the schema registry subject with backwards-compatibility rules. Pre-register all schema updates through a CI/CD pipeline and disable schema auto-registration in the producer clients.
Use Apache Avro for data serialization. Configure the schema registry subject with backwards-compatibility rules. Pre-register all schema updates through a CI/CD pipeline and disable schema auto-registration in the producer clients.
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.
Use Protocol Buffers (Protobuf) for data serialization. Configure the schema registry subject with backwards-compatibility rules. Enable schema auto-registration in the producer clients to ensure new fields are immediately available to downstream sinks.
StudyCerts
StudyCerts