Pubsub Avro Schema Evolution Deserialization

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.

An enterprise architecture team is designing a real-time streaming ingestion pipeline on Google Cloud using Cloud Pub/Sub to process events across multiple microservices. The Pub/Sub topic enforces an Apache Avro schema that evolves over time as upstream services add optional fields, creating multiple schema revisions.

The downstream subscriber applications maintain their own reader schema and must reliably deserialize incoming binary-encoded messages that may have been published under different schema revisions.

How should the subscriber application be architected to handle messages across evolving schema revisions?

Configure a dead-letter topic on the subscription to discard messages whose revision ID does not match the latest registered schema version.

Configure Cloud Pub/Sub to automatically rewrite and translate all message payloads to the subscriber's expected reader schema version before message delivery.

Inspect the googclient_schemarevisionid attribute on each message, fetch the corresponding writer schema revision definition from the Pub/Sub Schema service, and deserialize using an Avro DatumReader configured with both the writer schema and the reader schema.

Deserialize incoming messages using only the compiled local Avro reader schema directly, without retrieving or referencing the specific writer schema revision.

Professional Cloud Data Engineer

Pubsub Avro Schema Evolution Deserialization

Related questions