SnowPro Core · 13% of the exam

Snowflake connectivity: free practice questions

5 sample questions from our 33-question bank for this domain — answers and explanations included. These are the same scenario-based style as the real Snowflake exam.

1. A BI tool that only integrates with generic JDBC-compliant data sources needs to connect to Snowflake. What must typically be configured for this connection to work correctly?

  • A. The Snowflake JDBC driver JAR must be installed/registered with the tool, along with a correctly formed JDBC connection URL specifying account identifier and connection parameters✓ Correct
  • B. The BI tool must instead be reconfigured to use SnowSQL exclusively
  • C. JDBC connections to Snowflake are not supported by any BI tooling
  • D. Only ODBC-based BI tools can ever connect to Snowflake
Explanation

For a JDBC-compliant BI tool to connect to Snowflake, the Snowflake JDBC driver needs to be made available to the tool (as a JAR/library), and a properly formed JDBC connection URL (including the account identifier and relevant parameters like warehouse, database, role) must be configured — standard JDBC integration practice. Option B is unnecessary and incorrect; SnowSQL is a separate CLI tool, not a substitute for JDBC integration within a BI product. Option C is false — Snowflake explicitly supports JDBC connectivity, which is exactly why the driver exists. Option D is false; both JDBC and ODBC (among other clients) are supported, not just ODBC.

2. An administrator wants to view query performance details, including the graphical Query Profile, for a query run by another user in the account. Where can they do this?

  • A. In Snowsight, under the Activity / Query History section, which shows account-wide query history (subject to role privileges) with an accessible Query Profile view✓ Correct
  • B. Only by asking the other user to screen-share their session
  • C. Query Profile is not available in Snowsight, only in SnowSQL
  • D. Only the ACCOUNTADMIN role can ever view any query's profile, regardless of who ran it
Explanation

Snowsight's Activity/Query History area lets appropriately privileged users browse account-wide (not just their own) query history and open the graphical Query Profile for a selected query, which is the standard way to investigate performance. Option B is an unnecessary workaround. Option C is false — Query Profile is a Snowsight (and classic web UI) feature, not something limited to SnowSQL, which is command-line only and has no graphical profile view. Option D overstates ACCOUNTADMIN exclusivity; visibility depends on privileges/role, not solely on being ACCOUNTADMIN.

3. What is a key limitation to keep in mind about Partner Connect when planning a production BI tool rollout?

  • A. Partner Connect primarily streamlines initial trial/evaluation setup with select partners; production-grade configuration, licensing, and ongoing administration of the partner tool are still typically handled outside of Partner Connect itself✓ Correct
  • B. Partner Connect guarantees unlimited free usage of every partner tool forever
  • C. Once used, Partner Connect permanently locks the account to that one partner tool exclusively
  • D. Partner Connect requires disabling all other authentication methods in the account
Explanation

Partner Connect's role is centered on lowering friction for initial trial/evaluation setup with supported partners; it isn't intended to be the ongoing administration surface for a fully licensed production deployment of that partner tool, which is generally managed through the partner's own product and licensing relationship. Option B is false — trial provisioning is not the same as guaranteed unlimited free usage in perpetuity. Option C is false; using Partner Connect for one tool doesn't lock the account out of using others or from disconnecting it later. Option D is a fabricated and false restriction with no basis in how Partner Connect works.

4. A new Snowflake customer wants to quickly try out a data integration or BI partner tool (e.g., a visualization tool) with a pre-configured trial account and minimal manual setup. Which Snowflake feature is designed to streamline this?

  • A. Partner Connect, which provides guided workflows to set up trial accounts with select technology partners and auto-configures elements like the connection to the customer's Snowflake account✓ Correct
  • B. SnowSQL's --trial flag
  • C. Manually creating a new Snowflake account from scratch for the trial
  • D. A resource monitor configured for the partner's usage
Explanation

Partner Connect is specifically built to streamline onboarding with select ecosystem partner tools by offering guided flows that can, for many partners, provision a trial account and pre-configure the connection to the customer's own Snowflake account with minimal manual setup. Option B invents a nonexistent SnowSQL flag. Option C (manually creating a brand-new Snowflake account) misses the point of Partner Connect, which is specifically about partner tool trials, not new core Snowflake accounts. Option D (resource monitor) governs credit usage, unrelated to onboarding partner tools.

5. Which of these connectors is most appropriate for continuous, low-latency ingestion of individual streaming events, versus batch-oriented, large-scale distributed data processing jobs?

  • A. Kafka connector for the streaming ingestion use case; Spark connector for the batch/distributed processing use case✓ Correct
  • B. Spark connector for streaming ingestion; Kafka connector for distributed batch processing
  • C. Both connectors are functionally interchangeable with no meaningful distinction in intended use case
  • D. Neither connector is intended for data movement; both are purely for account administration
Explanation

The Kafka connector is designed around continuous, event-by-event streaming ingestion from Kafka topics into Snowflake, while the Spark connector is designed for large-scale, distributed batch (or micro-batch) data processing workloads reading from and writing to Snowflake. Option B reverses their actual intended use cases. Option C ignores the real, purpose-driven design differences between the two connectors. Option D is entirely incorrect; both connectors exist specifically for data movement/processing, not account administration.

28 more questions in this domain

Practice the full bank with instant grading, flashcards, and a timed mock exam.

Start practicing free
Snowflake connectivity — Free SnowPro Core Practice Questions | DataCertPrep — Certification Prep