Schema evolution (backward, forward, full) in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the schema compatibility to backward in Kafka.

Kafka

props.put("schema.compatibility.level", "[1]");

Drag options to blanks, or click blank then click option'

Abackward

Bforward

Cfull

Dnone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'forward' instead of 'backward' for backward compatibility.

Setting schema.compatibility.level to backward ensures new schemas can read data produced with previous schemas.

2fill in blank

medium

Complete the code to set the schema compatibility to forward in Kafka.

Kafka

props.put("schema.compatibility.level", "[1]");

Drag options to blanks, or click blank then click option'

Afull

Bnone

Cbackward

Dforward

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing forward with backward compatibility.

Setting schema.compatibility.level to forward ensures old schemas can read data produced with new schemas.

3fill in blank

hard

Fix the error in setting the schema compatibility to full in Kafka.

Kafka

props.put("schema.compatibility.level", "[1]");

Drag options to blanks, or click blank then click option'

Abackward

Bfull

Cforward

Dnone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'backward' or 'forward' instead of 'full' for full compatibility.

Full compatibility means schemas are both backward and forward compatible.

4fill in blank

hard

Fill both blanks to create a schema registry configuration with backward compatibility and a URL.

Kafka

props.put("schema.compatibility.level", "[1]");
props.put("schema.registry.url", "[2]");

Drag options to blanks, or click blank then click option'

Abackward

Bhttp://localhost:8081

Cforward

Dfull

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing forward and backward compatibility or wrong URL format.

The first blank sets backward compatibility, the second sets the schema registry URL.

5fill in blank

hard

Fill all three blanks to configure full compatibility, schema registry URL, and subject name strategy.

Kafka

props.put("schema.compatibility.level", "[1]");
props.put("schema.registry.url", "[2]");
props.put("value.subject.name.strategy", "[3]");

Drag options to blanks, or click blank then click option'

Abackward

Bhttp://schema-registry:8081

Cio.confluent.kafka.serializers.subject.TopicNameStrategy

Dfull

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong compatibility level or incorrect subject name strategy class.

Full compatibility is set, the schema registry URL points to the service, and the subject name strategy is set to TopicNameStrategy.