Question 40
For a public-sector reporting unit, this issue must not recur: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. Which review control fits best?
Explanation
Correct Answer
Validate stage upload and permissions separately from table loading. This reduces recurrence of: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files. The verification should demonstrate: The stage lists the expected file and COPY INTO can read it with the intended format.
Incorrect Answers
Add negative file fixtures to every new file-format rollout. That safeguard is aimed at ANOTHER risk: A data engineer needs to inspect malformed rows before committing a bulk load into the finance table. It is less targeted than the control for: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.
Validate representative nested arrays, nulls and malformed JSON before production loads. That safeguard is aimed at ANOTHER risk: An engineer sets JSON FILE FORMAT to CSV and loads a nested event record into a one-column raw table. It is less targeted than the control for: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.
Version output schemas and run consumer compatibility tests after format changes. That safeguard is aimed at ANOTHER risk: A business partner receives unloaded numeric fields as unexpected strings because the agreed file encoding differs from the Snowflake unload format. It is less targeted than the control for: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.