When users search the Glue Catalog, show the owning team, sensitivity class, and refresh frequency.
Keep these operational attributes separate from the physical schema.
Which feature is most appropriate?
Use Glue Catalog table parameters and tags to store operational metadata without changing column definitions.
Detailed explanation
Mixing operational metadata with schema names harms downstream contracts and queries.
Mixing operational metadata with schema names harms downstream contracts and queries.
One timestamp cannot express owner, classification, and refresh policy.
One timestamp cannot express owner, classification, and refresh policy.
Parameters and tags attach searchable ownership and classification metadata separately from the schema.
Parameters and tags attach searchable ownership and classification metadata separately from the schema.
Read history does not define the owning team or data classification.
Read history does not define the owning team or data classification.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Catalog Table Parameters、Tags、Lake Formation LF-Tagの公式説明を確認する。
What to confirm
列スキーマ・オブジェクト時刻・監査イベントと補助メタデータを区別できる。
Key points
- Table parameters
- Tags
- LF-Tag
- Operational metadata
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Schema versus metadata
Columns describe the data structure; parameters and tags describe how the asset is managed.
Searchable governance
Consistent owner and classification labels support discovery and access review.