Snowflake connectivity Study Guide — COF-C03

Snowflake Connectivity

This domain (≈13% of the exam, roughly 13–14 scored questions on a 100-question exam) tests how you get to Snowflake: which client, driver, connector, or UI to use for a given requirement, what each one can and cannot do, what it requires on the client machine, and how the connection is authenticated. Questions are overwhelmingly recall-and-recognise: exact product names (Snowsight, SnowSQL, Snowflake Connector for Python, Snowflake Connector for Kafka), which operations are client-side only (PUT/GET), which objects Partner Connect creates, which authentication method suits a service account, and which capabilities require a specific edition (private connectivity and Client Redirect require Business Critical). Nothing here requires you to write driver code — but you must recognise connection parameters such as authenticator=externalbrowser, snowflake_jwt, and sfURL.

How every client reaches Snowflake compute — all paths converge on one authenticated HTTPS endpoint.

Snowsight and the classic web UI

Snowsight is the Snowflake web interface, reached at https://app.snowflake.com or at your account URL https://<orgname>-<account_name>.snowflakecomputing.com. It requires only a supported browser — no client install, no driver, no local software. The older interface (Classic Console, historically at https://<account_locator>.<region>.snowflakecomputing.com/console) has been retired; Snowsight is the only UI you should choose on the exam unless a question explicitly asks about legacy behaviour.

Snowsight capability map (memorise the navigation nouns — distractors invent fake menu names):

Key Snowsight behaviours the exam probes:

• Worksheets are server-side objects: they autosave, keep version history, can be organised into folders, and can be shared with other users in the account. A worksheet has its own role, warehouse, database and schema context; changing the role in the worksheet header changes which objects you can see.
• Query results in a worksheet are available for 24 hours, matching the lifetime of the result cache; after that, re-running the query is required.
• Snowsight can chart a result set (line, bar, scatter, heatgrid, scorecard) and pin the chart as a dashboard tile. Dashboards support filters.
• The Load Data wizard lets you upload local files directly to a table or to a stage from the browser. The web UI upload path is limited to 50 MB per file — anything larger must go through SnowSQL/driver PUT or land in cloud storage first.
• PUT and GET SQL commands are NOT supported in worksheets. They are client-side commands, executable only from SnowSQL, the Snowflake CLI, or a driver/connector. This is one of the most frequently tested facts in the domain.
• Snowsight is where you enroll in MFA (Duo), set your default role, verify your email, and switch roles. Email verification + ACCOUNTADMIN is a prerequisite for Partner Connect.
• Snowsight supports secondary roles and role switching; it does not require a warehouse to browse metadata, but it does require a running/resumable warehouse to execute queries.

Common traps

• Choosing Snowsight for a scenario that says "upload a 2 GB local file" or "stage a local file" — the answer is SnowSQL/PUT, not the UI.
• Assuming the UI can run PUT/GET because you can type SQL there.
• Believing the web UI needs the ODBC or JDBC driver installed. It does not.
• Mixing up Query History (Monitoring) with Copy History (load history) and Account Usage views.
• Thinking worksheet results are stored indefinitely — 24 hours.
• Assuming Snowsight is a separate purchasable feature. It is included in all editions.

Worked scenario. An analyst must share a repeatable set of KPI visualisations with non-SQL business users, refreshed on open, without provisioning a BI tool. Reasoning: no third-party tool, visual output, Snowflake-native → build queries in a worksheet, create charts, pin them to a Snowsight dashboard, and share the dashboard. Partner Connect/Tableau would add licensing and is not needed.