The CRM and billing systems send the same customer under different IDs.
Avoid double-counting while retaining the basis for the merge decision.
Which quality approach is most appropriate?
Normalize matching attributes, define survivorship rules and confidence, and keep candidates separate from confirmed matches.
Detailed explanation
The result is traceable and low-confidence candidates can be reviewed.
The result is traceable and low-confidence candidates can be reviewed.
The chosen source and decision cannot be audited or reproduced.
The chosen source and decision cannot be audited or reproduced.
Spelling variations and namesakes can be incorrectly merged or split.
Spelling variations and namesakes can be incorrectly merged or split.
An IAM principal identifies an API actor, not a customer entity.
An IAM principal identifies an API actor, not a customer entity.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Quality matching、entity resolution、data catalogの公式説明を確認する。
What to confirm
完全一致やランダム削除より、根拠を持つエンティティ解決が必要な理由を説明できる。
Key points
- Entity resolution
- Normalization
- Confidence
- Mastering
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
False merge
An incorrect match can affect billing, access, and personal-data handling.
Lineage
Retain source IDs, rules, versions, and the decision history for each merged entity.