0

You want to add a new optional field to a Kafka topic's schema without disrupting existing consumers. Which schema management strategy should you use?

hard🚀 Application Q8 of Q15

Kafka - Schema Registry

You want to add a new optional field to a Kafka topic's schema without disrupting existing consumers. Which schema management strategy should you use?

ADisable schema validation temporarily during the update

BRemove all old fields and replace with the new schema version

CChange the field types of existing fields to match the new data

DAdd the new field as optional and maintain backward compatibility in the schema

Step-by-Step Solution

Solution:

Step 1: Understand schema evolution
Adding optional fields allows schema evolution without breaking existing consumers.
Step 2: Maintain backward compatibility
By keeping old fields and adding optional ones, older consumers can still deserialize messages.
Final Answer:
Add the new field as optional and maintain backward compatibility in the schema -> Option D
Quick Check:
Optional fields preserve backward compatibility [OK]

Quick Trick: Add optional fields to keep compatibility [OK]

Common Mistakes:

MISTAKES

Removing old fields breaks consumers
Changing existing field types causes incompatibility
Disabling validation risks data corruption

Master "Schema Registry" in Kafka

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Kafka Quizzes