An owning account exposes S3 tables to analytics accounts through a shared catalog.
Detect schema changes and update the shared definition without removing consumers' controlled access.
Which two design choices are appropriate?
Manage schema metadata in Glue Data Catalog and use Lake Formation sharing with Resource Links for cross-account access.
Detailed explanation
Changes are missed and compatibility problems are merely delayed.
Changes are missed and compatibility problems are merely delayed.
Changes in the data can be reflected in searchable table and partition metadata.
Changes in the data can be reflected in searchable table and partition metadata.
The data boundary and table-level authorization are lost, causing overexposure.
The data boundary and table-level authorization are lost, causing overexposure.
Definitions drift and changes require duplicated maintenance.
Definitions drift and changes require duplicated maintenance.
Catalog and access boundaries can be managed across accounts without unrestricted data copies.
Catalog and access boundaries can be managed across accounts without unrestricted data copies.
Check official documentation
Compare the following points with the official documentation.
Glue Data Catalog、Crawler、Lake Formation cross-account sharingの公式説明を確認する。
What to confirm
カタログ更新とクロスアカウント認可を、データ複製や公開設定と区別できる。
Key points
- Data Catalog
- Glue Crawler
- Resource Link
- Cross-account sharing
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Metadata
Keep schema and partition definitions discoverable and versioned separately from object copies.
Authorization
Use Lake Formation permissions to define which principals can consume the shared catalog resource.