AWS Glue Crawler Single Table Configuration
A finance company receives data from third-party data providers and stores the data as objects in an Amazon S3 bucket. The company ran an AWS Glue crawler on the objects to create a data catalog. The AWS Glue crawler created multiple tables. However, the company expected that the crawler would create only one table. The company needs a solution that will ensure the AVS Glue crawler creates only one table. Which combination of solutions will meet this requirement? (Choose two.)
Community Votes
83% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Glue crawlers infer schemas from file content; inconsistent formats or schemas across files cause multiple tables, while consistent prefixes group objects logically.
Learn how to configure AWS Glue crawlers to create a single table by ensuring consistent object format, schema, and S3 prefix structure for data stored in Amazon S3.
Many candidates choose AB, believing compression type must be consistent, but Glue handles different compression types within the same format (e.g., .gz, .snappy) if the base format is uniform.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To ensure the AWS Glue crawler creates only one table, the underlying data must present a uniform schema and file structure that Glue can interpret as a single dataset. Option A ensures that the object format (e.g., Parquet), compression type, and schema are identical, which guarantees Glue sees a homogeneous dataset. Option D ensures the structure of the S3 object prefix is consistent, which helps Glue treat the objects as part of a single logical partition or dataset rather than separate entities based on path variations.Why the Other Options Are Wrong
Option B excludes compression consistency, which might lead to issues if Glue cannot handle mixed compressions for the same format seamlessly in all contexts, though less critical than schema. However, Option A is stricter and safer. Option C suggests not enforcing file format consistency, which would definitely cause multiple tables if files were mixed CSV/JSON. Option E is vague; "similar pattern" is insufficient compared to the structural consistency required in D.Community Comment Notes
Community consensus strongly supports AD. As user teo2157 noted, "Consistent Object Format... Schema, and Prefix Structure" are key. User Salam9 confirmed this matches official practical exam answers. Some users like kailu questioned D, arguing prefix affects partitioning, but in the context of creating a single table vs multiple, consistent prefixing prevents Glue from splitting data into separate tables based on path anomalies.Exam Strategy
When configuring Glue Crawlers for single-table ingestion, prioritize schema and format uniformity. Always verify that your S3 data layout uses consistent prefixes to avoid unintended table segmentation.
Frequently Asked Questions
Why does compression type matter for Glue crawlers?
While Glue often handles common compressions, strict consistency in A ensures no ambiguity, especially for custom or less common codecs.
Does S3 prefix structure affect table creation?
Yes, inconsistent prefixes can lead Glue to treat objects as separate datasets or partitions, potentially resulting in multiple inferred tables if schema differs across paths.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →
s3://your-bucket/path/to/data/).