What is recommended before you start producing new events when schemas change?

What is recommended before you start producing new events when schemas change?

• A. Upgrade all Producers Before Producing New Events
• B. Upgrade all Consumers Before Producing New Events
• C. Disable Compatibility Checks
• D. Start Producing Immediately with the New Schema

Answer: (B)

When schemas change, the important practice is to upgrade the consumers before you start producing with the new schema. If producers start writing data with a new schema while some consumers still expect the old one, those consumers may fail to deserialize the messages, causing errors and gaps in processing. By updating consumers first, you ensure they can handle the new data format (and you can verify compatibility against the schema registry), then you can safely deploy producers to emit the new schema. Disabling compatibility checks or rushing to produce with the new schema without updated consumers increases the risk of widespread deserialization failures.

When schemas change, the important practice is to upgrade the consumers before you start producing with the new schema. If producers start writing data with a new schema while some consumers still expect the old one, those consumers may fail to deserialize the messages, causing errors and gaps in processing. By updating consumers first, you ensure they can handle the new data format (and you can verify compatibility against the schema registry), then you can safely deploy producers to emit the new schema. Disabling compatibility checks or rushing to produce with the new schema without updated consumers increases the risk of widespread deserialization failures.