In Confluent Schema Registry, what does a compatibility level of FULL ensure?

In Confluent Schema Registry, what does a compatibility level of FULL ensure?

• A. FULL requires no compatibility checks.
• B. FULL enforces both backward and forward compatibility; producers and consumers remain compatible across evolution.
• C. FULL checks backward compatibility only.
• D. FULL checks forward compatibility only.

Answer: (B)

Full means the system enforces both directions of compatibility as schemas evolve. In practice, this means a new schema can read data written with older schemas (backward compatibility) and older schemas can read data written with the new schema (forward compatibility). By requiring both, producers and consumers remain compatible across evolutions. For example, adding an optional field with a default value typically preserves both directions of compatibility, while removing a field or making incompatible changes without defaults would break one or both directions.

Full means the system enforces both directions of compatibility as schemas evolve. In practice, this means a new schema can read data written with older schemas (backward compatibility) and older schemas can read data written with the new schema (forward compatibility). By requiring both, producers and consumers remain compatible across evolutions. For example, adding an optional field with a default value typically preserves both directions of compatibility, while removing a field or making incompatible changes without defaults would break one or both directions.