An S3 prefix contains raw, processed, and _temporary paths.
The crawler should scan only raw data and avoid registering work-in-progress files.
Which configuration is most appropriate?
Set the crawler's S3 target and exclusion patterns so temporary prefixes are outside the discovery scope.
Detailed explanation
A query filter runs after catalog discovery and does not control crawler scope.
A query filter runs after catalog discovery and does not control crawler scope.
The crawler can limit its scan to raw paths and exclude temporary objects before cataloging.
The crawler can limit its scan to raw paths and exclude temporary objects before cataloging.
Object protection does not exclude a path from crawler discovery.
Object protection does not exclude a path from crawler discovery.
Public access does not constrain the scan and can expose unwanted data.
Public access does not constrain the scan and can expose unwanted data.
Check official documentation
Compare the following points with the official documentation.
AWS Glue CrawlerのS3 target、Exclusions、RecrawlPolicyの公式説明を確認する。
What to confirm
Catalog登録前のスキャン範囲とクエリ時の行フィルタを区別できる。
Key points
- S3 target
- Exclusion pattern
- Crawler scope
- Recrawl policy
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Scope before query
Crawler scope controls registration; an Athena predicate only controls returned rows.
Temporary-data hygiene
Keep work-in-progress files outside the discovery path or exclude them explicitly.