DEA-C01 Exam - Question 108

Question

A data engineer needs to debug an AWS Glue job that reads from Amazon S3 and writes to Amazon Redshift. The data engineer enabled the bookmark feature for the AWS Glue job.

The data engineer has set the maximum concurrency for the AWS Glue job to 1.

The AWS Glue job is successfully writing the output to Amazon Redshift. However, the Amazon S3 files that were loaded during previous runs of the AWS Glue job are being reprocessed by subsequent runs.

What is the likely reason the AWS Glue job is reprocessing the files?

Examice · Accepted Answer

The likely reason the AWS Glue job is reprocessing the files is because the AWS Glue job does not have a required commit statement. Without the commit statement, AWS Glue cannot track which files were processed successfully in the last run, resulting in the reprocessing of the data from Amazon S3 in subsequent runs. This is necessary to ensure that the job bookmarks are working correctly and that previously processed files are not included in future runs.

Bmaster · Answer

D is good

https://docs.aws.amazon.com/glue/latest/dg/glue-troubleshooting-errors.html#error-job-bookmarks-reprocess-data

lool · Answer

https://docs.aws.amazon.com/glue/latest/dg/glue-troubleshooting-errors.html#error-job-bookmarks-reprocess-data

Alagong · Answer

The commit statement (Option D) is not required for AWS Glue jobs. AWS Glue commits any open transactions to the database when all the script statements finish running.

HunkyBunky · Answer

For me - D looks correct

andrologin · Answer

AWS Glue Job requires the commit statement to save the last successful run/processing

DEA-C01 Exam - Question 108

Discussion