Question 200
For a regulated healthcare organization, this issue must not recur: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. Which review control fits best?
Explanation
Correct Answer
Review FORCE and PURGE options during production code changes. This reduces recurrence of: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files. The verification should demonstrate: Running the same unchanged file twice through the normal procedure does not create duplicate target rows.
Incorrect Answers
Test schema drift and reordered source files before each upstream release. That safeguard is aimed at ANOTHER risk: An operations analyst assumes COPY INTO will map reordered source columns correctly solely because target columns have matching names. It is less targeted than the control for: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.
Record recommended file sizing and compression for each data producer. That safeguard is aimed at ANOTHER risk: An ingest job loads multi-gigabyte compressed files serially and expects maximum parallelism from the warehouse alone. It is less targeted than the control for: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.
Freeze export contracts with round-trip parser tests. That safeguard is aimed at ANOTHER risk: A CSV unload intended for downstream SQL ingestion contains headers in some files and not others. It is less targeted than the control for: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.