Configuring AWS Glue Crawler for Daily Catalog Updates

Automate data processing by using AWS services.

Answer Correct answer: B — Create an IAM role with AWSGlueServiceRole, specify the S3 source, schedule the crawler, and define the database name for output.

A company stores daily records of the financial performance of investment portfolios in .csv format in an Amazon S3 bucket. A data engineer uses AWS Glue crawlers to crawl the S3 data. The data engineer must make the S3 data accessible daily in the AWS Glue Data Catalog. Which solution will meet these requirements?

Create an IAM role that includes the AmazonS3FullAccess policy. Associate the role with the crawler. Specify the S3 bucket path of the source data as the crawler's data store. Create a daily schedule to run the crawler. Configure the output destination to a new path in the existing S3 bucket.
Create an IAM role that includes the AWSGlueServiceRole policy. Associate the role with the crawler. Specify the S3 bucket path of the source data as the crawler's data store. Create a daily schedule to run the crawler. Specify a database name for the output. Correct Answer
Create an IAM role that includes the AmazonS3FullAccess policy. Associate the role with the crawler. Specify the S3 bucket path of the source data as the crawler's data store. Allocate data processing units (DPUs) to run the crawler every day. Specify a database name for the output.
Create an IAM role that includes the AWSGlueServiceRole policy. Associate the role with the crawler. Specify the S3 bucket path of the source data as the crawler's data store. Allocate data processing units (DPUs) to run the crawler every day. Configure the output destination to a new path in the existing S3 bucket.

Community Votes

100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The core concept is configuring a serverless AWS Glue Crawler; the common trap is confusing Glue Crawlers with Spark ETL jobs by incorrectly allocating DPUs or specifying S3 output destinations.

This question addresses how to automate the ingestion of CSV data from S3 into the AWS Glue Data Catalog using scheduled crawlers. It establishes that serverless crawlers require specific IAM roles and database targets, not DPU allocations or S3 output paths.

Option D is a common distractor because it includes DPUs, which are used for provisioned Glue ETL jobs, not for serverless crawlers that scale automatically without manual resource allocation.

Community Discussion (5 comments)

TonyStark0122 👍 8

B. Create an IAM role that includes the AWSGlueServiceRole policy. Associate the role with the crawler. Specify the S3 bucket path of the source data as the crawler's data store. Create a daily schedule to run the crawler. Specify a database name for the output. Explanation: Option B correctly sets up the IAM role with the necessary permissions using the AWSGlueServiceRole policy, which is designed for use with AWS Glue. It specifies the S3 bucket path of the source data as the crawler's data store and creates a daily schedule to run the crawler. Additionally, it specifies a database name for the output, ensuring that the crawled data is properly cataloged in the AWS Glue Data Catalog.

plutonash 👍 2 Selected: B

answer B is incomplete. Even we include AWSGlueServiceRole policy on IAM role, S3 access is not garantee

LrdKanien 👍 1

How does Glue get access to S3 if you don't do B?

k350Secops 👍 4 Selected: B

Glue Crawlers are serverless. Assigning DPUs is the point where i decided it option B

GiorgioGss 👍 4 Selected: B

A,C are wrong because you use don't need full S3 access. D is wrong because you don't need to provision DPU and the destination should be a database, not an s3 bucket. so it's B

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Option B is the correct solution because it utilizes the AWSGlueServiceRole policy, which grants the necessary permissions for the crawler to read from S3 and write metadata to the Glue Data Catalog. Specifying a database name is required as the output destination for the schema information. Creating a daily schedule ensures the catalog is updated with new records as requested.

Why the Other Options Are Wrong

Options A and C suggest using AmazonS3FullAccess, which is overly permissive and violates least-privilege principles compared to the managed AWSGlueServiceRole. Furthermore, Option A configures an S3 output path, which is incorrect as crawlers update the Data Catalog, not S3 files. Options C and D mention allocating Data Processing Units (DPUs); this is incorrect because Glue Crawlers are serverless and do not require manual DPU provisioning like Glue ETL jobs do.

Community Comment Notes

Community members largely agreed on B, with one user noting that assigning DPUs was the deciding factor against other options. Another commenter clarified that while AWSGlueServiceRole is sufficient, some users questioned if explicit S3 permissions were needed, but the service role handles this integration securely.

Exam Strategy

When dealing with AWS Glue, always distinguish between 'Crawlers' (serverless, no DPU selection) and 'ETL Jobs' (can be serverless or provisioned with DPUs). For crawlers, focus on the IAM role and the Data Catalog database target.

Frequently Asked Questions

Do Glue Crawlers require DPUs?

No. Glue Crawlers are serverless and scale automatically. DPUs are only allocated for provisioned Glue ETL jobs.

Why not use AmazonS3FullAccess?

It violates least-privilege security. The AWSGlueServiceRole provides the specific permissions needed for S3 access and Data Catalog updates.

More DEA-C01 FAQ →

Related Analysis

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide