Question 360
For this Snowflake situation — A data engineer needs to load daily CSV files from a shared Snowflake-managed staging area into a target table. — the team adopts: Create a named internal stage with the correct file format and use COPY INTO the target table. Which ongoing practice BEST limits the same problem recurring?
Explanation
Correct Answer
The relevant ongoing safeguard is: Validate file format settings and row counts after each ingestion change. It controls the recurring exposure associated with this mechanism: COPY INTO loads compatible staged files into a table using a defined file format and appropriate privileges. The original action, create a named internal stage with the correct file format and use COPY INTO the target table., still needs operational checks when the environment or workload changes.
Incorrect Answers
This routine guards against another mechanism: Directory tables expose file inventory information from staged object storage for supported workflows. The recurring exposure in the current case is: COPY INTO loads compatible staged files into a table using a defined file format and appropriate privileges. The matching preventive check is “Validate file format settings and row counts after each ingestion change”.
The suggested review tracks a different technical risk: A target-lag setting is an objective, not a guarantee independent of query and resource performance. Here the sustained control must address: COPY INTO loads compatible staged files into a table using a defined file format and appropriate privileges. Choose “Validate file format settings and row counts after each ingestion change”.
That safeguard is relevant to: Snowpipe auto-ingest depends on arriving file notifications as well as a valid target and pipe definition. The current failure instead follows from: COPY INTO loads compatible staged files into a table using a defined file format and appropriate privileges. Its prevention measure is “Validate file format settings and row counts after each ingestion change”.