Every order customer_id must exist in the customer master.
Master updates can arrive after orders, so delayed references need handling.
Which quality approach is most appropriate?
Check referenced-key existence, hold late records for a bounded period, and recheck before final quarantine.
Detailed explanation
Orphan orders are detected while late master data can be allowed through a controlled hold path.
Orphan orders are detected while late master data can be allowed through a controlled hold path.
Inventing master data can corrupt business meaning.
Inventing master data can corrupt business meaning.
Later master arrival cannot restore deleted evidence.
Later master arrival cannot restore deleted evidence.
An API principal is not a customer-master reference.
An API principal is not a customer-master reference.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Quality referential integrity、custom SQL、workflow retryの公式説明を確認する。
What to confirm
参照エラーの無条件補完・削除と、保留して再検査する設計を区別できる。
Key points
- Referential integrity
- Orphan key
- Late arrival
- Hold queue
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Time consistency
Compare facts and master data for the same processing window and define the delay tolerance.
Replay
Recheck held rows after the master arrives and record final success or failure.