DEA-C01 Data Ingestion and Transformation Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Reduce the volume of incoming data

  Why it's wrong here

  Reducing incoming data volume changes business scope rather than fixing the job's execution; the OutOfMemory persists if partitioning and shuffle behaviour remain unchanged. It tempts as an intuitive capacity fix, but the correct approach adjusts Glue worker memory or repartitions data to relieve executor heap pressure.

• ✗

  Configure the job to use a larger memory setting

  Why it's wrong here

  Increasing memory setting raises the executor heap, but Glue OutOfMemory typically arises from skewed partitions or inefficient shuffles, so more memory only delays the failure. It tempts because it directly targets the error message, yet the correct remedy addresses data distribution or worker type configuration.

• ✗

  Use a smaller file size for input

  Why it's wrong here

  Smaller input files increase the number of objects and tasks, raising per-executor overhead rather than lowering memory pressure. It tempts as a tuning lever, but Glue's OutOfMemory stems from executor heap limits, so the fix is raising worker memory or repartitioning data, not shrinking individual files.

• ✓

  Increase the number of DPUs allocated to the Glue job

  Why this is correct

  Glue allocates memory per executor across its DPUs; OutOfMemory errors during ingestion indicate insufficient memory for the workload's partitions. Increasing DPU count adds executors and memory capacity, directly resolving the resource constraint causing the job failure.

Go deeper

Related to this question