DEA-C01 Data Operations and Support Practice Question
A data engineer is troubleshooting an AWS Glue crawler that is not correctly inferring the schema of CSV files stored in Amazon S3. The files have headers, but the crawler is treating the header row as data. The crawler is configured with a custom classifier that has a CSV classifier with 'Column header' set to 'Use first row as header'. What is the most likely reason the crawler is not recognizing the header?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The CSV classifier's 'Quote symbol' setting does not match the files.
The CSV classifier's 'Quote symbol' setting must match the files. If the files do not use quotes, but the classifier expects a quote symbol (e.g., double quotes), the classifier may fail to match, causing the crawler to fall back to default behavior and treat the header row as data. Option B is wrong because a varying number of columns would cause schema issues, not header misrecognition. Option C is wrong because the delimiter is unrelated to header detection; a custom delimiter can be set separately. Option D is wrong because case of header text does not affect the crawler's ability to recognize headers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The CSV classifier's 'Quote symbol' setting does not match the files.
Why this is correct
If the classifier expects a quote symbol but the files have none, the classifier may not apply, causing the crawler to treat header as data.
- ✗
The CSV files have a varying number of columns across rows.
Why it's wrong here
Varying columns might cause schema issues but not header detection.
- ✗
The CSV files have a different delimiter than the default comma.
Why it's wrong here
The delimiter is configurable in the classifier.
- ✗
The header row contains uppercase letters.
Why it's wrong here
Case does not affect header recognition.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This DEA-C01 question is part of Courseiva's 1,711-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DEA-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DEA-C01 exam.