A data provider may rename a column.
A Glue script's CI pipeline must verify compatibility with the expected schema before production promotion.
Which test is most appropriate?
Use a data-contract test to validate column names, types, required fields, and compatibility in CI.
Detailed explanation
The failure reaches production data and business processing instead of being caught early.
The failure reaches production data and business processing instead of being caught early.
Request records do not validate column structure or compatibility.
Request records do not validate column structure or compatibility.
CI can reject incompatible names, types, nullability, and required columns before production.
CI can reject incompatible names, types, nullability, and required columns before production.
The actor making an API call does not describe the data schema.
The actor making an API call does not describe the data schema.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Catalog、CodeBuild、データ契約・スキーマ検証の公式説明を確認する。
What to confirm
運用ログ・監査主体と、スキーマ互換性テストの違いを説明できる。
Key points
- Data contract
- Schema validation
- CodeBuild
- Compatibility
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Breaking versus additive change
An added optional field may be compatible, while a removed or retyped required field may break consumers.
Shift left
Run contract checks with fixtures and catalog metadata before deployment and production data access.