Explanation:
AWS Glue job bookmarks track data that has already been processed during previous runs. For bookmarks to work, the job must successfully commit the bookmark at the end of the run using job.commit(). If this statement is missing, the bookmark state is not updated, and previous files are reprocessed.
Ultimate access to all questions.
Question 25
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?
A
The AWS Glue job does not have the s3:GetObjectAcl permission that is required for bookmarks to work correctly.
B
The maximum concurrency for the AWS Glue job is set to 1.
C
The data engineer incorrectly specified an older version of AWS Glue for the Glue job.
D
The AWS Glue job does not have a required commit statement.
No comments yet.