1. Streaming Schema Evolution advanced

    A producer added a required field. New consumers work. A consumer replaying from three months ago fails. Why, and what is the policy fix?

    2 min answer schemacompatibilityreplay
  2. Streaming Schema Evolution intermediate

    A team needs to change the schema of an event that many consumers read. What is the safe process?

    2 min answer sharechatschemacompatibilityregistry
  3. Streaming Schema Evolution intermediate Multiple choice

    A topic's subject is registered with FORWARD compatibility. A producer team adds a new field with no default and plans to ship the producer first and let 30 consumer teams upgrade over the following month. A reviewer blocks the change saying the compatibility mode already settled the order and the plan is backwards. Who is right?

    3 min answer schema-registrycompatibilitydeployment-orderavro
  4. Streaming Schema Evolution advanced

    An event schema must change while consumers and retained history both depend on the old version. How is this managed?

    2 min answer schema-evolutioncompatibilityregistryretention
  5. Streaming Schema Evolution advanced

    Review this. A payments platform runs 300 topics with the schema registry in FULL compatibility mode for every subject, a rule that each new field must be optional with a default, and a schema-change request that goes to an architecture review board with a three-week turnaround. Engineers have started putting new data into a generic metadata map to avoid the queue. What would you remove, what would you change, and what would you leave alone?

    3 min answer schema-registrygovernancecompatibilitypayments
  6. Streaming Schema Evolution advanced

    Walk me through retiring a field from an event consumed by around 40 teams, where the field is populated from a system being decommissioned in six months.

    2 min answer schema evolutiondeprecationconsumer censuscompatibility