COF-C03 Question 12
Single answer1.2 Use Snowflake Interfaces and toolsA data engineer needs to load a local CSV file into a Snowflake table and wants to preview the data first, create the table with a SQL worksheet, and then use a guided interface to load the file without writing a full COPY INTO command manually. Which Snowflake interface is the best fit for completing this end-to-end task?
- A
Snowsight, using a worksheet to create the table and the data loading wizard to upload and load the file
- B
SnowSQL only, because file loading from a local machine requires a command-line client
- C
Classic Console only, because Snowsight does not support loading local files into tables
- D
The Snowflake Python Connector only, because creating tables and loading files must be automated through code
Show answer and explanation
Correct answer: A
Explanation
The best answer is Snowsight. For SnowPro Core, candidates should understand the role of Snowflake interfaces and tools, including when to use Snowsight, SnowSQL, connectors, and drivers. Snowsight is Snowflake's modern web UI and includes worksheets for writing and executing SQL, object exploration, query history, and guided data loading experiences. This makes it well suited to an end-to-end workflow where a user wants to create a table and interactively load a local file. SnowSQL and connectors remain important for scripting, automation, and external integrations, but they are not the best fit when the requirement emphasizes a UI-based, guided process. This aligns with Snowflake documentation describing Snowsight as the primary interface for SQL development and common administrative/data tasks, including loading data through the web interface.
- A. Correct.
Correct. Snowsight supports SQL worksheets for creating database objects such as tables, and it also provides a guided data loading experience that allows users to load files from a local machine into Snowflake. In practice, a user can preview the file structure, select or create the destination table, and complete the load through the UI without manually composing the full COPY INTO statement.
- B. Incorrect.
Incorrect. SnowSQL can load files and run SQL, but it is not required for this scenario. The misconception is that local file loading must be done through a CLI. Snowflake supports loading local files through Snowsight's UI workflow as well, making SnowSQL unnecessary when the goal is an interactive, guided process.
- C. Incorrect.
Incorrect. This reflects an outdated understanding of Snowflake interfaces. Snowsight is the primary web interface and supports data loading workflows. The Classic Console has been superseded for many tasks, and saying Snowsight does not support local file loading is factually incorrect.
- D. Incorrect.
Incorrect. The Python Connector can certainly automate table creation and loading tasks, but automation is not required here. The scenario explicitly asks for a guided interface and a worksheet-based experience, which aligns better with Snowsight than with programmatic access through Python.