Datasets grow across departments and nobody knows who approves quality, access, or retention changes.
Make responsibility and contact information discoverable.
Which governance approach is most appropriate?
Record owner, steward, purpose, and SLA in Catalog metadata and track approvals by role or team.
Detailed explanation
Turnover and departmental accountability are not handled.
Turnover and departmental accountability are not handled.
The latest operator is not necessarily the business owner.
The latest operator is not necessarily the business owner.
Names do not model multiple roles or survive renames well.
Names do not model multiple roles or survive renames well.
Each asset has searchable responsibility and approval context.
Each asset has searchable responsibility and approval context.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Catalog metadata、data governance、Lake Formationの公式説明を確認する。
What to confirm
利用者・操作主体と、データの業務所有者・管理担当の違いを説明できる。
Key points
- Owner
- Steward
- Data Catalog
- SLA
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Continuity
Use team roles and durable contacts so responsibility survives staff changes.
Approval
Identify who approves access, classification, retention, and quality exceptions.