COF-C03 Question 16
Single answerSnowflake CLIA data engineering team is standardizing local development for Snowflake. Developers need a command-line tool that can authenticate using a named connection profile, execute SQL non-interactively in CI pipelines, and also support managing project artifacts such as Snowflake Native App or Streamlit project files from the terminal. Which tool should the team use to meet these requirements?
- A
Snowsql, because it is the primary Snowflake command-line client for all modern project lifecycle tasks including deploying Streamlit and Native App artifacts
- B
Snowflake CLI, because it supports connection profiles, running SQL commands/scripts, and managing Snowflake project resources from the command line
- C
The Classic Console, because it can be invoked from scripts to run SQL and deploy application artifacts without interactive login
- D
Python Connector, because it is the recommended command-line interface for administrators who need profile-based SQL execution and artifact management
Show answer and explanation
Correct answer: B
Explanation
The best answer is Snowflake CLI. In real-world teams, Snowflake CLI is used to standardize local developer workflows and CI/CD automation because it supports configured connections, command-line SQL execution, and project-oriented operations beyond simple query submission. By contrast, Snowsql is primarily a SQL command-line client and is not the modern choice for broader Snowflake project management tasks. The Classic Console is browser-based, and the Python Connector is an SDK/library rather than a CLI. This aligns with Snowflake guidance that Snowflake CLI is the current command-line experience for interacting with Snowflake resources and developer projects.
- A. Incorrect.
Incorrect. Snowsql is a legacy command-line client commonly used to run SQL, but it is not the modern tool intended for broader Snowflake project lifecycle management such as working with newer project-oriented resources. A candidate might choose this option because Snowsql is well known as a Snowflake CLI tool, but the scenario explicitly requires both SQL execution and managing project artifacts from the terminal, which aligns with Snowflake CLI rather than Snowsql.
- B. Correct.
Correct. Snowflake CLI is designed to work with named connections, execute SQL from the command line, and support project-based workflows for Snowflake resources. This makes it a good fit for local development standardization and CI/CD-style automation where both SQL execution and management of project artifacts are needed.
- C. Incorrect.
Incorrect. The Classic Console is a web-based interface, not a command-line tool for non-interactive execution in CI pipelines. Someone might pick this option if they are thinking about administrative capabilities in the UI, but the question specifically asks for a command-line tool supporting scripted automation.
- D. Incorrect.
Incorrect. The Python Connector is a programming library, not a command-line interface. It can be used to build custom automation, but it does not itself serve as the Snowflake command-line tool for named-profile usage and project artifact management. This distractor targets the misconception that any API client is equivalent to a CLI.