SnowPro Associate: Platform Question 277
Single answer● Use Snowsight to load dataA data analyst needs to quickly load a local CSV file into an existing Snowflake table using Snowsight. The table already exists, and the analyst wants Snowflake to infer the file format from the file during the guided load process. Which action in Snowsight best meets this requirement?
- A
Use Snowsight's Data » Databases » select the target table » Load Data, then upload the local CSV file and review the detected file format settings before loading.
- B
Create an external stage with SQL, manually define a file format object, and then run COPY INTO; Snowsight cannot upload local files for loading.
- C
Use Snowsight to open a worksheet and run PUT to upload the file directly to the internal stage associated with the target table.
- D
Use Snowpipe Streaming from Snowsight because it is the standard method for one-time local CSV uploads into existing tables.
Show answer and explanation
Correct answer: A
Explanation
For a one-time or ad hoc load of a local file into an existing table, Snowsight provides a guided Load Data experience that is appropriate and efficient. In this workflow, a user can navigate to the target table, choose to load data, upload a local file, and review inferred parsing options such as delimiter, header rows, and other file format settings before executing the load. This is a common best practice for simple interactive loads. By contrast, SQL-based methods using stages and COPY INTO are more flexible for repeatable pipelines, and SnowSQL's PUT is used outside Snowsight for local file uploads to internal stages. Snowpipe Streaming is designed for streaming ingestion use cases rather than manual file uploads. See Snowflake documentation for loading data with Snowsight and for distinctions between Snowsight loading, COPY INTO, PUT, and Snowpipe/Snowpipe Streaming.
- A. Correct.
Correct. In Snowsight, you can load data into an existing table through the guided Load Data workflow. For local files such as CSV, Snowsight supports uploading the file, detecting or allowing review of file format settings, and then loading the data into the selected table. This is the most direct approach for a quick, UI-driven load.
- B. Incorrect.
Incorrect. While creating stages, file formats, and using COPY INTO is a valid SQL-based loading approach, it is not required here and does not best match the requirement to use Snowsight's guided process for a quick local file load. The statement that Snowsight cannot upload local files is false.
- C. Incorrect.
Incorrect. PUT is a SnowSQL command used to upload files from a local machine to an internal stage; it is not executed in Snowsight worksheets for local file transfer in the same way. This option reflects a common misconception between SnowSQL command-line capabilities and Snowsight UI-based loading.
- D. Incorrect.
Incorrect. Snowpipe Streaming is intended for continuous low-latency ingestion from applications, not for a one-time manual upload of a local CSV file through Snowsight. Using it here would be unnecessarily complex and not aligned with the scenario.