Practise the standard verbs for managing schemas in the Kafka Schema Registry.
0 / 5 completed
1 / 5
Fill in: 'We ___ every Avro schema in the registry before a producer is allowed to publish messages using it.'
We 'register a schema' — the standard, established Kafka Schema Registry collocation for adding a new schema version. The other options aren't the recognised term here.
2 / 5
Fill in: 'Publishing with an incompatible schema change can ___ every existing consumer failing to deserialize new messages.'
We say an incompatible change will 'leave' consumers failing — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ backward compatibility on every schema evolution so an old consumer can still read a newer message.'
We 'enforce' compatibility — the standard, established collocation for requiring a schema evolution rule. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a schema ID in every message header so a consumer knows exactly which version to deserialize against.'
We 'include' an ID — the standard, simple collocation for embedding a reference value in a message. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ schema changes through a review process so a breaking field rename never ships without a migration plan.'
We 'route changes' — the standard, simple collocation for directing an update through an approval workflow. The other options are less idiomatic here.