An anonymized aggregate is produced from a PII source table.
Verify that a deletion request reaches derived data.
Which governance approach is most appropriate?
Maintain lineage from source through jobs and manifests to derived tables so impact and regeneration can be determined.
Detailed explanation
Access history does not describe transformation relationships.
Access history does not describe transformation relationships.
Names do not capture transformations or copies reliably.
Names do not capture transformations or copies reliably.
PII may remain in derived tables, caches, or backups.
PII may remain in derived tables, caches, or backups.
Source-to-output relationships identify all affected derived assets.
Source-to-output relationships identify all affected derived assets.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Catalog、data lineage、Lake Formationの公式説明を確認する。
What to confirm
派生表名と、変換関係を追跡できるデータリネージの違いを説明できる。
Key points
- Data lineage
- Derived data
- Impact analysis
- Deletion request
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Propagation
Follow aggregates, caches, backups, and feature stores that may retain a personal value.
Regeneration
Rebuild derived data with corrected input and retire the prior version.