McAfee-Secured Website

Exam Bundle

Exam Code: SnowPro Core

Exam Name SnowPro Core

Certification Provider: Snowflake

Corresponding Certification: SnowPro Core

Snowflake SnowPro Core Bundle $44.99

100% Snowflake SnowPro Core Guaranteed Success With Testking Training Materials

Get Real SnowPro Core Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    SnowPro Core Questions & Answers

    703 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual SnowPro Core exam while allowing you to hone and measure every aspect of your test-taking ability.

  • SnowPro Core Video Course

    SnowPro Core Video Course

    92 Video Lectures

    SnowPro Core Video Course is developed by Snowflake Professionals to help you pass the SnowPro Core exam.

    Description

    This course will improve your knowledge and skills required to pass SnowPro Core exam.
  • Study Guide

    SnowPro Core Study Guide

    413 PDF Pages

    Developed by industry experts, this 413-page guide spells out in painstaking detail all of the information you need to ace SnowPro Core exam.

SnowPro Core Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    703 Questions

    $124.99
  • SnowPro Core Video Course

    Video Course

    92 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    413 PDF Pages

    $29.99

Snowflake SnowPro Core Practice Test 6

Question 50

After the approved change, engineers revisit: A BI tool connects using an outdated driver and sees unsupported authentication failures after a platform security update. Which result establishes the intended state?

  1. The pipeline loads representative events with measured latency and manageable operational overhead.
  2. The updated client establishes an authorized session and runs the same controlled query.
  3. The connector's role context and query results remain correct after default-role changes.
  4. Multiple appropriately sized staged files increase effective parallel processing under the chosen warehouse.

Explanation

Correct Answer

B:

The updated client establishes an authorized session and runs the same controlled query. This validates the relevant action: Upgrade to a supported Snowflake connector or driver version and configure its approved authentication method. The underlying Snowflake behavior is: Client drivers implement authentication and protocol compatibility, not just SQL formatting.

Incorrect Answers

A:

The pipeline loads representative events with measured latency and manageable operational overhead. This evidence tests a DIFFERENT situation: A data app needs to ingest events from Kafka but engineers build one file per message and a new warehouse COPY for each row. The correction required in this case is: Upgrade to a supported Snowflake connector or driver version and configure its approved authentication method.

C:

The connector's role context and query results remain correct after default-role changes. This evidence tests a DIFFERENT situation: A partner uses an ODBC reporting connector with a role that changes silently after an administrator modifies user defaults. The correction required in this case is: Upgrade to a supported Snowflake connector or driver version and configure its approved authentication method.

D:

Multiple appropriately sized staged files increase effective parallel processing under the chosen warehouse. This evidence tests a DIFFERENT situation: An ingest job loads multi-gigabyte compressed files serially and expects maximum parallelism from the warehouse alone. The correction required in this case is: Upgrade to a supported Snowflake connector or driver version and configure its approved authentication method.

Question 51

A root-cause investigation considers: A BI tool connects using an outdated driver and sees unsupported authentication failures after a platform security update. What is the most applicable explanation?

  1. Event source configuration is independent of merely having a valid COPY statement inside the pipe.
  2. External access integration controls outbound network destinations and secret access boundaries.
  3. Client drivers implement authentication and protocol compatibility, not just SQL formatting.
  4. Transport replay semantics and business-level uniqueness are separate concerns.

Explanation

Correct Answer

C:

Client drivers implement authentication and protocol compatibility, not just SQL formatting. This explains the condition: A BI tool connects using an outdated driver and sees unsupported authentication failures after a platform security update. The corrective response is: Upgrade to a supported Snowflake connector or driver version and configure its approved authentication method.

Incorrect Answers

A:

Event source configuration is independent of merely having a valid COPY statement inside the pipe. That mechanism explains a DIFFERENT Snowflake problem: A cloud storage event notification invokes Snowpipe from a test bucket, but production bucket events point to a stale integration identifier. Here the relevant mechanism instead is: Client drivers implement authentication and protocol compatibility, not just SQL formatting.

B:

External access integration controls outbound network destinations and secret access boundaries. That mechanism explains a DIFFERENT Snowflake problem: An external UDF sends public data to an API, but the security review discovers its request uses an unrestricted outbound network rule. Here the relevant mechanism instead is: Client drivers implement authentication and protocol compatibility, not just SQL formatting.

D:

Transport replay semantics and business-level uniqueness are separate concerns. That mechanism explains a DIFFERENT Snowflake problem: Streaming events are delivered at least once, and an application assumes each row is a new financial transaction. Here the relevant mechanism instead is: Client drivers implement authentication and protocol compatibility, not just SQL formatting.

Question 52

During operational handoff for this problem: A BI tool connects using an outdated driver and sees unsupported authentication failures after a platform security update. Which guardrail should be included?

  1. Keep environment-specific account identifiers out of source-code assumptions.
  2. Maintain integration inventory across test and production storage environments.
  3. Implement idempotent downstream merge keys and replay tests.
  4. Maintain supported connector versions and regression-test authentication changes.

Explanation

Correct Answer

D:

Maintain supported connector versions and regression-test authentication changes. This reduces recurrence of: Client drivers implement authentication and protocol compatibility, not just SQL formatting. The verification should demonstrate: The updated client establishes an authorized session and runs the same controlled query.

Incorrect Answers

A:

Keep environment-specific account identifiers out of source-code assumptions. That safeguard is aimed at ANOTHER risk: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. It is less targeted than the control for: Client drivers implement authentication and protocol compatibility, not just SQL formatting.

B:

Maintain integration inventory across test and production storage environments. That safeguard is aimed at ANOTHER risk: A cloud storage event notification invokes Snowpipe from a test bucket, but production bucket events point to a stale integration identifier. It is less targeted than the control for: Client drivers implement authentication and protocol compatibility, not just SQL formatting.

C:

Implement idempotent downstream merge keys and replay tests. That safeguard is aimed at ANOTHER risk: A data team uses Snowpipe to load raw events but expects it to automatically merge updates into existing customer rows. It is less targeted than the control for: Client drivers implement authentication and protocol compatibility, not just SQL formatting.

Question 53

A data-platform team must resolve: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. Which technical change most directly solves it?

  1. Disable or account for result caching in controlled benchmarking and compare equivalent execution paths.
  2. Inspect Query Profile partition pruning and clustering information before considering targeted reclustering.
  3. Rewrite predicates to use supported sargable timestamp ranges aligned with stored values.
  4. Compare search optimization, normal clustering and materialization against actual lookup workload.

Explanation

Correct Answer

B:

Inspect Query Profile partition pruning and clustering information before considering targeted reclustering. This directly addresses the described Snowflake condition: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. The mechanism is: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning. Verify success using: After an appropriate improvement, comparable queries scan fewer relevant partitions with correct row results.

Incorrect Answers

A:

Disable or account for result caching in controlled benchmarking and compare equivalent execution paths. That is suitable for a DIFFERENT Snowflake situation: A team compares two Query Profiles but one run retrieved a cached result without scanning source tables. It does not directly resolve the current requirement: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval.

C:

Rewrite predicates to use supported sargable timestamp ranges aligned with stored values. That is suitable for a DIFFERENT Snowflake situation: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. It does not directly resolve the current requirement: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval.

D:

Compare search optimization, normal clustering and materialization against actual lookup workload. That is suitable for a DIFFERENT Snowflake situation: A selective point lookup needs acceleration but an engineer wants to recluster an entire table without measuring existing pruning. It does not directly resolve the current requirement: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval.

Question 54

A Snowflake acceptance test follows this incident: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. What evidence most directly proves the correction?

  1. Small-table queries remain within target performance without recurring reclustering credits.
  2. Both comparison runs execute comparable underlying work rather than one reusing a previous result.
  3. After an appropriate improvement, comparable queries scan fewer relevant partitions with correct row results.
  4. Refresh history returns to healthy state and downstream rows reflect the current approved source schema.

Explanation

Correct Answer

C:

After an appropriate improvement, comparable queries scan fewer relevant partitions with correct row results. This validates the relevant action: Inspect Query Profile partition pruning and clustering information before considering targeted reclustering. The underlying Snowflake behavior is: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

Incorrect Answers

A:

Small-table queries remain within target performance without recurring reclustering credits. This evidence tests a DIFFERENT situation: An engineer adds a clustering key to every small table although Query Profile shows already efficient pruning. The correction required in this case is: Inspect Query Profile partition pruning and clustering information before considering targeted reclustering.

B:

Both comparison runs execute comparable underlying work rather than one reusing a previous result. This evidence tests a DIFFERENT situation: A team compares two Query Profiles but one run retrieved a cached result without scanning source tables. The correction required in this case is: Inspect Query Profile partition pruning and clustering information before considering targeted reclustering.

D:

Refresh history returns to healthy state and downstream rows reflect the current approved source schema. This evidence tests a DIFFERENT situation: An incremental dynamic table refresh repeatedly fails after an upstream schema change, but analysts continue trusting stale downstream data. The correction required in this case is: Inspect Query Profile partition pruning and clustering information before considering targeted reclustering.

Question 55

The data-platform team observes: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. Which architectural or processing fact matters most?

  1. Data growth, clustering drift or cardinality changes can alter query work with unchanged warehouse size.
  2. Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.
  3. Missing join predicates create Cartesian multiplication even with syntactically valid SQL.
  4. Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

Explanation

Correct Answer

D:

Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning. This explains the condition: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. The corrective response is: Inspect Query Profile partition pruning and clustering information before considering targeted reclustering.

Incorrect Answers

A:

Data growth, clustering drift or cardinality changes can alter query work with unchanged warehouse size. That mechanism explains a DIFFERENT Snowflake problem: A query suddenly slows after a large table changed, yet the team looks only at warehouse size changes. Here the relevant mechanism instead is: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

B:

Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges. That mechanism explains a DIFFERENT Snowflake problem: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. Here the relevant mechanism instead is: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

C:

Missing join predicates create Cartesian multiplication even with syntactically valid SQL. That mechanism explains a DIFFERENT Snowflake problem: A query uses a comma-separated FROM list and a missing join predicate multiplies rows, inflating sales totals. Here the relevant mechanism instead is: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

Question 56

For a regulated healthcare organization, this issue must not recur: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. Which review control fits best?

  1. Track partitions scanned versus total across representative filter queries.
  2. Include profile-based pruning checks in important report code reviews.
  3. Require performance and cost evidence rather than raw elapsed time alone.
  4. Validate uniqueness and date-range integrity for type-2 dimensions.

Explanation

Correct Answer

A:

Track partitions scanned versus total across representative filter queries. This reduces recurrence of: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning. The verification should demonstrate: After an appropriate improvement, comparable queries scan fewer relevant partitions with correct row results.

Incorrect Answers

B:

Include profile-based pruning checks in important report code reviews. That safeguard is aimed at ANOTHER risk: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. It is less targeted than the control for: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

C:

Require performance and cost evidence rather than raw elapsed time alone. That safeguard is aimed at ANOTHER risk: A data engineer expects a larger warehouse always to reduce a query's credit cost even if runtime barely changes. It is less targeted than the control for: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

D:

Validate uniqueness and date-range integrity for type-2 dimensions. That safeguard is aimed at ANOTHER risk: A transformation joins sales to a dimension table with two overlapping effective-date records and duplicates revenues. It is less targeted than the control for: Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

Question 57

In a governed Snowflake environment, the reported condition is: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. What should be implemented first?

  1. Use supported MERGE with stable business keys and explicit update/insert branches for true upsert behavior.
  2. Enforce non-overlapping validity intervals or select the correct effective-dated dimension row.
  3. Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values.
  4. Evaluate a supported materialized view matching a frequently repeated single-table aggregation.

Explanation

Correct Answer

C:

Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values. This directly addresses the described Snowflake condition: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. The mechanism is: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic. Verify success using: A fixture with numeric and invalid payloads yields expected sums and explicit rejected or null values.

Incorrect Answers

A:

Use supported MERGE with stable business keys and explicit update/insert branches for true upsert behavior. That is suitable for a DIFFERENT Snowflake situation: A developer wants to update target customer records from daily source changes but uses INSERT for every delivery. It does not directly resolve the current requirement: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors.

B:

Enforce non-overlapping validity intervals or select the correct effective-dated dimension row. That is suitable for a DIFFERENT Snowflake situation: A transformation joins sales to a dimension table with two overlapping effective-date records and duplicates revenues. It does not directly resolve the current requirement: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors.

D:

Evaluate a supported materialized view matching a frequently repeated single-table aggregation. That is suitable for a DIFFERENT Snowflake situation: An analyst wants transparently faster aggregate queries over one large fact table without rewriting every dashboard. It does not directly resolve the current requirement: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors.

Question 58

A test plan evaluates: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. Which evidence should be required before release?

  1. A repeated source batch updates existing targets instead of inserting duplicate customer keys.
  2. A controlled tie fixture shows precisely the required ranking behavior.
  3. The test selective lookup improves under the approved feature without incorrect results.
  4. A fixture with numeric and invalid payloads yields expected sums and explicit rejected or null values.

Explanation

Correct Answer

D:

A fixture with numeric and invalid payloads yields expected sums and explicit rejected or null values. This validates the relevant action: Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values. The underlying Snowflake behavior is: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

Incorrect Answers

A:

A repeated source batch updates existing targets instead of inserting duplicate customer keys. This evidence tests a DIFFERENT situation: A developer wants to update target customer records from daily source changes but uses INSERT for every delivery. The correction required in this case is: Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values.

B:

A controlled tie fixture shows precisely the required ranking behavior. This evidence tests a DIFFERENT situation: A finance report uses RANK to assign unique row numbers but produces ties and gaps in the sequence. The correction required in this case is: Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values.

C:

The test selective lookup improves under the approved feature without incorrect results. This evidence tests a DIFFERENT situation: An analytics query searches a small customer ID set in a giant table with no selective access optimization. The correction required in this case is: Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values.

Question 59

A Snowflake incident report notes: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. What underlying mechanism explains the behavior?

  1. Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.
  2. Missing join predicates create Cartesian multiplication even with syntactically valid SQL.
  3. An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them.
  4. Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

Explanation

Correct Answer

A:

Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic. This explains the condition: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. The corrective response is: Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values.

Incorrect Answers

B:

Missing join predicates create Cartesian multiplication even with syntactically valid SQL. That mechanism explains a DIFFERENT Snowflake problem: A query uses a comma-separated FROM list and a missing join predicate multiplies rows, inflating sales totals. Here the relevant mechanism instead is: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

C:

An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them. That mechanism explains a DIFFERENT Snowflake problem: A transformation joins sales to a dimension table with two overlapping effective-date records and duplicates revenues. Here the relevant mechanism instead is: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

D:

Warehouse-local data cache belongs to a compute environment, unlike global persisted query results. That mechanism explains a DIFFERENT Snowflake problem: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. Here the relevant mechanism instead is: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

Question 60

A platform governance committee considers: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. What preventive check should be standardized?

  1. Test idempotent replay and multiple-source-match conflicts before release.
  2. Add data-type assertions for common JSON attributes in transformation tests.
  3. Use boundary and late-arriving data tests for rolling aggregate SQL.
  4. Include root task state and graph status in deployment checks.

Explanation

Correct Answer

B:

Add data-type assertions for common JSON attributes in transformation tests. This reduces recurrence of: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic. The verification should demonstrate: A fixture with numeric and invalid payloads yields expected sums and explicit rejected or null values.

Incorrect Answers

A:

Test idempotent replay and multiple-source-match conflicts before release. That safeguard is aimed at ANOTHER risk: A developer wants to update target customer records from daily source changes but uses INSERT for every delivery. It is less targeted than the control for: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

C:

Use boundary and late-arriving data tests for rolling aggregate SQL. That safeguard is aimed at ANOTHER risk: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. It is less targeted than the control for: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

D:

Include root task state and graph status in deployment checks. That safeguard is aimed at ANOTHER risk: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. It is less targeted than the control for: Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.