A producer adds an optional field to an existing event.
Keep old consumers running while the new event schema is introduced.
Which configuration is most appropriate?
Register the schema with a backward-compatibility mode in Schema Registry and reject incompatible changes.
Detailed explanation
The registry checks whether an old consumer can continue reading the new schema.
The registry checks whether an old consumer can continue reading the new schema.
Object versions do not validate fields in an event schema.
Object versions do not validate fields in an event schema.
An incompatible change can reach production consumers and fail at runtime.
An incompatible change can reach production consumers and fail at runtime.
Authorization rules do not determine whether a schema is backward compatible.
Authorization rules do not determine whether a schema is backward compatible.
Check official documentation
Compare the following points with the official documentation.
Glue Schema Registry compatibility mode（BACKWARD等）の公式説明を確認する。
What to confirm
スキーマ互換性と、オブジェクト版・権限拒否の違いを説明できる。
Key points
- Backward compatibility
- Schema Registry
- Schema version
- Consumer
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Additive versus breaking
An optional field can be compatible, while removing or retyping a required field can break readers.
Registration gate
Reject incompatible schemas before they reach the stream and downstream applications.