Delivery retries can ingest the same event_id more than once.
Detect duplicates before aggregation, report the count, and retain the original data.
Which quality approach is most appropriate?
Define an event_id uniqueness rule and preserve evidence while applying a deterministic deduplication policy.
Detailed explanation
The selected row cannot be reproduced or audited.
The selected row cannot be reproduced or audited.
Duplicate keys are identified as a quality violation that can be quarantined and reported.
Duplicate keys are identified as a quality violation that can be quarantined and reported.
API volume does not identify duplicate business events.
API volume does not identify duplicate business events.
File age does not establish event uniqueness.
File age does not establish event uniqueness.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Quality uniqueness rules、SQL COUNT、deduplicationの公式説明を確認する。
What to confirm
一意性検知とランダム削除の再現性の違いを説明できる。
Key points
- Uniqueness
- event_id
- Duplicate
- Selection rule
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Idempotency
Use the event key so delivery retries do not create another accepted result.
Evidence
Retain original rows and the deduplication decision for investigation.