A producer adds an optional field to an event.
Existing consumers cannot be upgraded immediately and must continue processing the event.
Which configuration is most appropriate?
Use Glue Schema Registry with a backward-compatibility mode and validate the new schema at registration time.
Detailed explanation
Registration can reject changes that an existing consumer cannot read.
Registration can reject changes that an existing consumer cannot read.
Processing is interrupted and incompatible data can fail when consumers return.
Processing is interrupted and incompatible data can fail when consumers return.
This loses the schema contract and moves validation burden to consumers.
This loses the schema contract and moves validation burden to consumers.
S3 object lifecycle rules do not validate or manage event schemas.
S3 object lifecycle rules do not validate or manage event schemas.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Schema Registry compatibility modes、schema versions、data formatの公式説明を確認する。
What to confirm
スキーマ契約、互換性モード、文字列化の違いを説明できる。
Key points
- Schema Registry
- Backward compatibility
- Schema version
- Producer/consumer
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Compatibility contract
Producer and consumer versions must be tested together rather than relying on untyped strings.
Change classification
Optional additions, removals, and type changes have different compatibility effects.