A sales analysis needs only age band and region.
Do not copy names, email addresses, or detailed addresses to the analytics environment.
Which governance approach is most appropriate?
Extract only purpose-required columns and granularity, and aggregate or anonymize the analytical dataset.
Detailed explanation
Changing labels leaves the sensitive values intact.
Changing labels leaves the sensitive values intact.
The exposed data and permissions are reduced before sharing.
The exposed data and permissions are reduced before sharing.
Audit after copying does not minimize the dataset.
Audit after copying does not minimize the dataset.
A notice does not prevent misuse or leakage.
A notice does not prevent misuse or leakage.
Check official documentation
Compare the following points with the official documentation.
AWS data minimization、Macie、Lake Formation column permissionsの公式説明を確認する。
What to confirm
注意書き・列名変更と、実データを減らす最小化の違いを説明できる。
Key points
- Data minimization
- Anonymization
- Aggregation
- Purpose limitation
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Re-identification risk
Rare combinations of geography or attributes may still identify someone.
Retention
Delete derived analytical data when its purpose ends.