ExamPark
Course menuDEA-C01

Exams / DEA-C01 / Transformation with AWS Glue / Question 1

DEA-C01 practice question: Transformation with AWS Glue (1 of 3)

Data Ingestion and Transformation A free question from our original DEA-C01 practice exam. Try it, then open the answer to see why each option is right or wrong.

Last verified against current AWS documentation ·How we write our questions

A logistics broker runs a nightly AWS Glue job that reads new carrier-invoice files from an S3 prefix and writes them to a curated table. Each night the job reprocesses every invoice file since launch, so the runtime keeps growing and some invoices are loaded twice.

The team wants each run to process only files that arrived since the previous successful run, and it wants to keep the same job script with minimal changes.

Which change meets these requirements?

Choose one answer.

  1. A. Add a step that deletes the curated table at the start of each run, and then reprocess every invoice file from the beginning.
  2. B. Move the job to an AWS Lambda function triggered once a day, and have the function read the whole prefix into memory before writing.
  3. C. Run an AWS Glue crawler before each job so that the job can see new partitions, and keep the job's source reads unchanged.
  4. D. Turn on job bookmarks, and give each source read a transformation_ctx name so that Glue tracks which files were processed.
Show the answer and explanation

Answer: D

  • A. Wrong: Rebuilding everything each night still reprocesses the full history, which is the problem the team wants to remove. The table would also be empty during every run.
  • B. Wrong: A daily function that reads the full prefix repeats the same work and keeps no record of what it has processed. Lambda's memory and runtime limits also make it a poor fit for a growing invoice history.
  • C. Wrong: A crawler updates catalog metadata, but it does not track which files the job has already read. The job would still process the whole prefix every night.
  • D. Right: Correct. Job bookmarks store the state of each run, so later runs process only new data for supported sources such as S3. Each source needs a transformation_ctx name, which ties its bookmark state to that read. Learn more: Tracking processed data using job bookmarks (opens in a new tab)

Explanation

Job bookmarks let a Glue job remember what it has already processed, so each run handles only new data. Enabling them and naming each source with transformation_ctx keeps the existing script almost unchanged. Deleting and rebuilding, moving to a timed function, or running a crawler do not track processed files.

Study

Keep practicing

Answer questions with a score at the end, or practice just this topic with the explanation after each one. No sign-up needed.

Take the free DEA-C01 practice examPractice Transformation with AWS GlueAll Transformation with AWS Glue questions

Want more on Transformation with AWS Glue? The 5 full-length practice sets have 10 more Transformation with AWS Glue questions, 325 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets