A Data Engineer made modifications to staged files and re-staged them. A pipe is running but the changed data is not appearing in the table. What step should the Engineer take in order to see the…

Question

Options

• ARun the or syntax.
• BRe-run the pipe by using the RELOAD PIPE syntax.
• CRe-run the pipe by using the ONLY_CHANGES syntax.
• DCreate new files with the changed data.

• A
  9% (2)
• B
  4% (1)
• C
  13% (3)
• D
  74% (17)

Explanation

Snowpipe tracks ingested files by name/path to prevent duplicates - once a file has been loaded, the pipe will not re-process it, even if its contents change. Creating new files with the changed data (D) gives the pipe a new, untracked file to detect and load automatically, which is the only way to surface updated data without triggering duplicate records.

Why the distractors are wrong:

• A is incomplete/garbled in the question stem and references no valid Snowflake syntax.
• B is wrong because RELOAD PIPE is not a valid Snowflake command - pipes cannot be "reloaded" this way.
• C is wrong because ONLY_CHANGES is not a valid Snowpipe syntax; change tracking in Snowflake is handled via Streams, not pipes.

Memory tip: Think of Snowpipe as a "one-stamp-per-file" system - once a file is stamped as ingested, that stamp never expires. If the data changes, you need a brand-new file to get a new stamp.

No community discussion yet for this question.