A crawler configuration is changing, but existing tables must not disappear because an object is temporarily absent.
Approved deletion is handled by a separate process.
Which configuration is most appropriate?
Set the crawler DeleteBehavior and table-retention policy so temporary absence does not delete catalog metadata.
Detailed explanation
Removing audit evidence makes deletion harder to investigate.
Removing audit evidence makes deletion harder to investigate.
Recreation loses metadata history and does not protect dependent tables.
Recreation loses metadata history and does not protect dependent tables.
Object-history settings do not control catalog deletion behavior.
Object-history settings do not control catalog deletion behavior.
The crawler can be prevented from deleting a table when it is temporarily missing from discovery.
The crawler can be prevented from deleting a table when it is temporarily missing from discovery.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Crawler SchemaChangePolicy DeleteBehavior、Catalog削除の公式説明を確認する。
What to confirm
Catalog保護とS3版管理・監査ログの違いを説明できる。
Key points
- DeleteBehavior
- Table retention
- Crawler
- Change policy
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Protection before cleanup
Separate discovery from deletion so a transient source problem does not remove downstream metadata.
Recovery planning
If deletion is approved, preserve source data and a way to recreate the catalog definition.