Question 410
A Snowflake platform team receives the following requirement: A team reruns COPY INTO from the same staged filenames expecting all rows to append again but Snowflake reports files already loaded. Which condition explains why the current approach fails?
Explanation
Correct Answer
The described symptoms indicate that file-load metadata can prevent unchanged staged files from being loaded repeatedly. The appropriate resolution is: Inspect load history and use an intentional approved reprocessing workflow only when necessary. Confirm with: The test either skips already-loaded files or reloads through the documented controlled method.
Incorrect Answers
The destination naming and overwrite policy does not ensure safe export versioning. “Adopt unique run-specific output prefixes or an approved controlled replacement strategy” would address that alternative cause, not the condition in this question: file-load metadata can prevent unchanged staged files from being loaded repeatedly.
“Configure an authorized external stage with a scoped storage integration and permitted cloud trust” responds to this separate finding: the external storage integration has not been configured for governed access. This question instead needs “Inspect load history and use an intentional approved reprocessing workflow only when necessary”, so the alternative does not meet the stated condition.
The command targets table ingestion rather than the supported unload-to-stage operation. “Use COPY INTO a permitted stage location FROM an approved SELECT query with an explicit file format” applies to that separate problem. The observed case is a team reruns COPY INTO from the same staged filenames expecting all rows to append again but Snowflake reports files already loaded; choosing this alternative would address the wrong failure mode.