Customer data should refresh hourly but has not changed for six hours.
Detect freshness loss rather than relying on a successful job message.
Which quality approach is most appropriate?
Monitor the gap between the newest event time and now, with an explicit freshness threshold and response path.
Detailed explanation
The time gap measures whether data arrived within the expected window.
The time gap measures whether data arrived within the expected window.
Deletion does not create a new data arrival.
Deletion does not create a new data arrival.
Old rows can remain while freshness has already failed.
Old rows can remain while freshness has already failed.
An API timestamp is not the business-data update time.
An API timestamp is not the business-data update time.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Quality freshness、CloudWatch metrics、event timeの公式説明を確認する。
What to confirm
行数・処理成功とデータ鮮度を別指標で扱う理由を説明できる。
Key points
- Freshness
- event_time
- Latency
- Timeliness
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Time semantics
Distinguish event, receipt, and processing times and document the time zone.
Stale-data response
Expose the last successful time and avoid silently presenting old data as current.