Several teams publish datasets that must be found by owner, quality, and intended use.
Prevent similarly named data from being selected without understanding its meaning and restrictions.
Which design is most appropriate?
Register business and technical metadata in a catalog so users can discover ownership, quality, classification, and usage conditions.
Detailed explanation
A common format does not make business ownership or quality discoverable.
A common format does not make business ownership or quality discoverable.
A path name does not capture ownership, quality, freshness, or sensitivity.
A path name does not capture ownership, quality, freshness, or sensitivity.
Searchable metadata helps users understand and compare a dataset before reusing it.
Searchable metadata helps users understand and compare a dataset before reusing it.
API actors do not describe data meaning, quality, or business ownership.
API actors do not describe data meaning, quality, or business ownership.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Catalog、Amazon SageMaker Catalog、data discoveryの公式説明を確認する。
What to confirm
データ形式・S3キー・監査ログと、検索用カタログメタデータを区別できる。
Key points
- Data catalog
- Metadata
- Ownership
- Data quality
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Business and technical context
A useful catalog combines schema details with business definitions and usage conditions.
Governance
Classification and access conditions help users decide whether reuse is permitted.