DEA-C02 Data Movement 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.

• ✗

  Use the PATTERN option to match only files with a specific prefix or regex that includes the current date, and update the pipe definition daily.

  Why it's wrong here

  While PATTERN can filter files, dynamically updating it daily is operationally complex and error-prone. It also does not prevent reprocessing of files that match the pattern if they were already loaded. The load history is the primary mechanism to avoid duplicates. This approach adds unnecessary maintenance and does not guarantee the requirement.

• ✗

  Rely on Snowpipe's default behavior, which automatically tracks file modification times and skips files older than the pipe creation time.

  Why it's wrong here

  Snowpipe does not automatically skip files based on modification times relative to pipe creation. It uses a load history to avoid reprocessing files already loaded, but if files are added later with older timestamps, they may still be loaded if not in history. This option incorrectly assumes a time-based filter that does not exist. The engineer needs a more explicit mechanism.

• ✗

  Configure the pipe with a MODIFIED_AFTER parameter set to a timestamp that is updated after each load.

  Why it's wrong here

  MODIFIED_AFTER is not a valid Snowpipe parameter. Snowpipe does not support a parameter to filter by modification time. The load history automatically tracks which files have been loaded, regardless of modification time. This option is based on a non-existent feature, so it cannot be implemented.

• ✓

  Ensure the pipe uses the load history to track processed files; Snowpipe automatically skips files that have already been loaded, even if they appear again.

  Why this is correct

  Snowpipe maintains a load history for each pipe, recording which files have been processed. When new files are detected, it checks the history and skips any file that has already been loaded. This prevents reprocessing of old files, even if they are in existing partitions. This is the default and correct behavior, requiring no additional configuration.