Run a data-quality check after a Glue ETL job.
Publish to the production table only on success; isolate and notify on failure.
Which configuration is most appropriate?
Use a Glue Conditional trigger based on the quality-job state to branch to publication or failure handling.
Detailed explanation
Encryption state does not represent whether a quality check passed.
Encryption state does not represent whether a quality check passed.
An API audit record does not indicate data-quality acceptance.
An API audit record does not indicate data-quality acceptance.
Publication could occur before validation and expose bad data.
Publication could occur before validation and expose bad data.
A trigger can start publication on success and route failure to isolation or notification.
A trigger can start publication on success and route failure to isolation or notification.
Check official documentation
Compare the following points with the official documentation.
AWS Glue TriggerのConditional、Job state、Crawler state、Workflowを確認する。
What to confirm
状態条件と保存暗号化・監査ログの役割を区別できる。
Key points
- Conditional trigger
- Glue job
- Quality gate
- Branch
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Promotion control
A state condition prevents invalid data from reaching the production table.
Evidence versus gate
A CloudTrail record or encryption setting is evidence or protection, not a quality result.