I am producing Avro data on my Kafka cluster that is integrated with the Confluent Schema Registry. After a schema change that is incompatible, I know my data will be rejected. Which component will…

The correct answer is A. The Confluent Schema Registry. The Confluent Schema Registry is your safeguard against incompatible schema changes and will be the component that ensures no breaking schema evolution will be possible. Kafka Brokers do not look at your payload and your payload schema, and therefore will not reject data.

Application Design

Question

I am producing Avro data on my Kafka cluster that is integrated with the Confluent Schema Registry. After a schema change that is incompatible, I know my data will be rejected. Which component will reject the data?

Options

AThe Confluent Schema Registry
BThe Kafka Broker
CThe Kafka Producer itself
DZookeeper

How the community answered

(21 responses)

A
95% (20)
C
5% (1)

Explanation

The Confluent Schema Registry is your safeguard against incompatible schema changes and will be the component that ensures no breaking schema evolution will be possible. Kafka Brokers do not look at your payload and your payload schema, and therefore will not reject data.

Topics

#Schema Registry#schema compatibility#Avro evolution#incompatible schema

Community Discussion

No community discussion yet for this question.

Full CCDAK Practice