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 23

Question 220

A platform governance committee considers: A team needs the latest event per customer, but SELECT DISTINCT keeps multiple records with different timestamps. What preventive check should be standardized?

  1. Alert when new categories appear outside approved reporting dimensions.
  2. Require deterministic tie-breakers for latest-record deduplication.
  3. Include empty-array and missing-key cases in flattening tests.
  4. Require performance and cost evidence rather than raw elapsed time alone.

Explanation

Correct Answer

B:

Require deterministic tie-breakers for latest-record deduplication. This reduces recurrence of: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values. The verification should demonstrate: The result returns one predictable most-recent event for each customer.

Incorrect Answers

A:

Alert when new categories appear outside approved reporting dimensions. That safeguard is aimed at ANOTHER risk: An analyst pivots event records to monthly metrics but assumes unexpected new event categories appear automatically in a fixed static pivot. It is less targeted than the control for: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values.

C:

Include empty-array and missing-key cases in flattening tests. That safeguard is aimed at ANOTHER risk: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. It is less targeted than the control for: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values.

D:

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: Window ranking selects rows by partition and order, unlike DISTINCT over complete row values.

Question 221

An engineering team investigates the following Snowflake issue: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. Which configuration or processing decision is most appropriate?

  1. Use a dynamic table or streams-and-tasks pipeline for the required multi-step SQL transformation.
  2. Measure view refresh cost and query utilization, removing unproductive maintained results.
  3. Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values.
  4. Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions.

Explanation

Correct Answer

D:

Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions. This directly addresses the described Snowflake condition: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. The mechanism is: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results. Verify success using: Profile data-cache behavior changes with warehouse lifecycle while identical eligible SQL may use result reuse.

Incorrect Answers

A:

Use a dynamic table or streams-and-tasks pipeline for the required multi-step SQL transformation. That is suitable for a DIFFERENT Snowflake situation: A developer proposes a materialized view using complex multi-table joins and procedural steps that its supported definition cannot express. It does not directly resolve the current requirement: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses.

B:

Measure view refresh cost and query utilization, removing unproductive maintained results. That is suitable for a DIFFERENT Snowflake situation: An organization enables multiple materialized views for rarely used reports and sees maintenance charges rising above query savings. It does not directly resolve the current requirement: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses.

C:

Cast nested JSON values to the correct numeric SQL type with safe validation of malformed values. That is suitable for a DIFFERENT Snowflake situation: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. It does not directly resolve the current requirement: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses.

Question 222

For a telecommunications provider, the original problem was: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. What observation confirms success?

  1. Profile data-cache behavior changes with warehouse lifecycle while identical eligible SQL may use result reuse.
  2. A repeated eligible query reuses its persisted result when result-cache conditions are satisfied.
  3. The chosen pipeline computes the expected join output under supported refresh semantics.
  4. The corrected query returns the expected business grain without explosive intermediate row counts.

Explanation

Correct Answer

A:

Profile data-cache behavior changes with warehouse lifecycle while identical eligible SQL may use result reuse. This validates the relevant action: Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions. The underlying Snowflake behavior is: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

Incorrect Answers

B:

A repeated eligible query reuses its persisted result when result-cache conditions are satisfied. This evidence tests a DIFFERENT situation: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time. The correction required in this case is: Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions.

C:

The chosen pipeline computes the expected join output under supported refresh semantics. This evidence tests a DIFFERENT situation: A developer proposes a materialized view using complex multi-table joins and procedural steps that its supported definition cannot express. The correction required in this case is: Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions.

D:

The corrected query returns the expected business grain without explosive intermediate row counts. This evidence tests a DIFFERENT situation: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. The correction required in this case is: Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions.

Question 223

In a case affecting a telecommunications provider, this issue appears: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. What explains it?

  1. Materialized view definition constraints differ from general declarative dynamic tables and procedural tasks.
  2. Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.
  3. Search optimization and clustering solve different access patterns and maintenance trade-offs.
  4. Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

Explanation

Correct Answer

B:

Warehouse-local data cache belongs to a compute environment, unlike global persisted query results. This explains the condition: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. The corrective response is: Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions.

Incorrect Answers

A:

Materialized view definition constraints differ from general declarative dynamic tables and procedural tasks. That mechanism explains a DIFFERENT Snowflake problem: A developer proposes a materialized view using complex multi-table joins and procedural steps that its supported definition cannot express. Here the relevant mechanism instead is: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

C:

Search optimization and clustering solve different access patterns and maintenance trade-offs. That mechanism explains a DIFFERENT Snowflake problem: A selective point lookup needs acceleration but an engineer wants to recluster an entire table without measuring existing pruning. Here the relevant mechanism instead is: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

D:

Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic. That mechanism explains a DIFFERENT Snowflake problem: An analyst sums values extracted from a VARIANT JSON payload but obtains string concatenation or conversion errors. Here the relevant mechanism instead is: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

Question 224

After remediating the Snowflake issue, the team reviews: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. Which recurring control is most targeted?

  1. Compare query savings against maintenance cost and supported SQL limitations.
  2. Reevaluate predicate selectivity and credit impact after query pattern changes.
  3. Track cache layer and warehouse lifecycle in benchmark reports.
  4. Use query linting and controlled row-count assertions for production joins.

Explanation

Correct Answer

C:

Track cache layer and warehouse lifecycle in benchmark reports. This reduces recurrence of: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results. The verification should demonstrate: Profile data-cache behavior changes with warehouse lifecycle while identical eligible SQL may use result reuse.

Incorrect Answers

A:

Compare query savings against maintenance cost and supported SQL limitations. That safeguard is aimed at ANOTHER risk: An analyst wants transparently faster aggregate queries over one large fact table without rewriting every dashboard. It is less targeted than the control for: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

B:

Reevaluate predicate selectivity and credit impact after query pattern changes. That safeguard is aimed at ANOTHER risk: A selective point lookup needs acceleration but an engineer wants to recluster an entire table without measuring existing pruning. It is less targeted than the control for: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

D:

Use query linting and controlled row-count assertions for production joins. That safeguard is aimed at ANOTHER risk: A query uses a comma-separated FROM list and a missing join predicate multiplies rows, inflating sales totals. It is less targeted than the control for: Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.

Question 225

At a consumer marketplace, a Snowflake implementation review finds: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. Which action best addresses this requirement?

  1. Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites.
  2. Use streams and tasks with supported stored procedures or other permitted procedural components.
  3. Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection.
  4. Diagnose queued load and evaluate workload isolation or multi-cluster concurrency before blindly rewriting SQL.

Explanation

Correct Answer

A:

Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites. This directly addresses the described Snowflake condition: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. The mechanism is: Tasks require correct resume state and execution configuration independently of their SQL body. Verify success using: Task history records successful runs under the intended schedule and active task state.

Incorrect Answers

B:

Use streams and tasks with supported stored procedures or other permitted procedural components. That is suitable for a DIFFERENT Snowflake situation: A task needs to call external APIs conditionally and loop through records, but developers choose a dynamic table as if it ran procedural code. It does not directly resolve the current requirement: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph.

C:

Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection. That is suitable for a DIFFERENT Snowflake situation: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. It does not directly resolve the current requirement: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph.

D:

Diagnose queued load and evaluate workload isolation or multi-cluster concurrency before blindly rewriting SQL. That is suitable for a DIFFERENT Snowflake situation: A warehouse runs a complex query quickly when alone but users see high queued overload during peak BI hours. It does not directly resolve the current requirement: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph.

Question 226

After the approved change, engineers revisit: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. Which result establishes the intended state?

  1. Refresh history returns to healthy state and downstream rows reflect the current approved source schema.
  2. Task history records successful runs under the intended schedule and active task state.
  3. A committed consumer updates the downstream target and advances the stream's tracked offset.
  4. After an appropriate improvement, comparable queries scan fewer relevant partitions with correct row results.

Explanation

Correct Answer

B:

Task history records successful runs under the intended schedule and active task state. This validates the relevant action: Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites. The underlying Snowflake behavior is: Tasks require correct resume state and execution configuration independently of their SQL body.

Incorrect Answers

A:

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: Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites.

C:

A committed consumer updates the downstream target and advances the stream's tracked offset. This evidence tests a DIFFERENT situation: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. The correction required in this case is: Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites.

D:

After an appropriate improvement, comparable queries scan fewer relevant partitions with correct row results. This evidence tests a DIFFERENT situation: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. The correction required in this case is: Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites.

Question 227

A root-cause investigation considers: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. What is the most applicable explanation?

  1. Materialized pipeline freshness depends on successful refresh and compatible source definitions.
  2. Dynamic tables express maintained SQL transformations declaratively, whereas manual streams/tasks expose procedural control.
  3. Tasks require correct resume state and execution configuration independently of their SQL body.
  4. Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning.

Explanation

Correct Answer

C:

Tasks require correct resume state and execution configuration independently of their SQL body. This explains the condition: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. The corrective response is: Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites.

Incorrect Answers

A:

Materialized pipeline freshness depends on successful refresh and compatible source definitions. That mechanism explains a DIFFERENT Snowflake problem: An incremental dynamic table refresh repeatedly fails after an upstream schema change, but analysts continue trusting stale downstream data. Here the relevant mechanism instead is: Tasks require correct resume state and execution configuration independently of their SQL body.

B:

Dynamic tables express maintained SQL transformations declaratively, whereas manual streams/tasks expose procedural control. That mechanism explains a DIFFERENT Snowflake problem: A data team maintains a SQL-based bronze-to-silver transformation with fixed freshness targets but writes complicated manual MERGE scheduling code. Here the relevant mechanism instead is: Tasks require correct resume state and execution configuration independently of their SQL body.

D:

Micro-partition metadata reduces scan work only when predicates and physical value ranges allow pruning. That mechanism explains a DIFFERENT Snowflake problem: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. Here the relevant mechanism instead is: Tasks require correct resume state and execution configuration independently of their SQL body.

Question 228

During operational handoff for this problem: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. Which guardrail should be included?

  1. Monitor refresh failure signals and run schema-compatibility tests before source deployments.
  2. Check procedural feature requirements before choosing dynamic tables.
  3. Review spill metrics in expensive queries before changing multi-cluster settings.
  4. Include root task state and graph status in deployment checks.

Explanation

Correct Answer

D:

Include root task state and graph status in deployment checks. This reduces recurrence of: Tasks require correct resume state and execution configuration independently of their SQL body. The verification should demonstrate: Task history records successful runs under the intended schedule and active task state.

Incorrect Answers

A:

Monitor refresh failure signals and run schema-compatibility tests before source deployments. That safeguard is aimed at ANOTHER risk: An incremental dynamic table refresh repeatedly fails after an upstream schema change, but analysts continue trusting stale downstream data. It is less targeted than the control for: Tasks require correct resume state and execution configuration independently of their SQL body.

B:

Check procedural feature requirements before choosing dynamic tables. That safeguard is aimed at ANOTHER risk: A task needs to call external APIs conditionally and loop through records, but developers choose a dynamic table as if it ran procedural code. It is less targeted than the control for: Tasks require correct resume state and execution configuration independently of their SQL body.

C:

Review spill metrics in expensive queries before changing multi-cluster settings. That safeguard is aimed at ANOTHER risk: A large aggregation is spilling heavily to remote storage, but its warehouse has no concurrency queue. It is less targeted than the control for: Tasks require correct resume state and execution configuration independently of their SQL body.

Question 229

A data-platform team must resolve: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access. Which technical change most directly solves it?

  1. Configure the supported secure view sharing prerequisites and necessary database/object share grants.
  2. Keep shared objects read-only and use an approved local table copy if independent transformations are required.
  3. Evaluate a supported cross-region listing with auto-fulfillment or approved replication-based sharing strategy.
  4. Assign cost controls and monitor the provider-owned reader account's compute usage.

Explanation

Correct Answer

B:

Keep shared objects read-only and use an approved local table copy if independent transformations are required. This directly addresses the described Snowflake condition: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access. The mechanism is: Standard secure shares grant consumers read access, not write ownership of provider tables. Verify success using: The consumer can query the shared table and can modify only its own separate local derived data.

Incorrect Answers

A:

Configure the supported secure view sharing prerequisites and necessary database/object share grants. That is suitable for a DIFFERENT Snowflake situation: A data provider creates a direct share but the consumer cannot see a secure view because underlying reference privileges are incomplete. It does not directly resolve the current requirement: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access.

C:

Evaluate a supported cross-region listing with auto-fulfillment or approved replication-based sharing strategy. That is suitable for a DIFFERENT Snowflake situation: Two Snowflake accounts are in different regions and a provider assumes a direct share can be added across the regions immediately. It does not directly resolve the current requirement: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access.

D:

Assign cost controls and monitor the provider-owned reader account's compute usage. That is suitable for a DIFFERENT Snowflake situation: A reader account query bill rises unexpectedly and the consuming partner assumes its own organization pays the Snowflake compute. It does not directly resolve the current requirement: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access.

Question 230

A Snowflake acceptance test follows this incident: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access. What evidence most directly proves the correction?

  1. Usage reports attribute consumer query compute and provider source storage to their respective accounts.
  2. New direct queries fail, while the exported-file inventory is handled by separate data lifecycle procedures.
  3. The consumer can query the shared table and can modify only its own separate local derived data.
  4. A pilot consumer can find the approved listing metadata and request or acquire access as designed.

Explanation

Correct Answer

C:

The consumer can query the shared table and can modify only its own separate local derived data. This validates the relevant action: Keep shared objects read-only and use an approved local table copy if independent transformations are required. The underlying Snowflake behavior is: Standard secure shares grant consumers read access, not write ownership of provider tables.

Incorrect Answers

A:

Usage reports attribute consumer query compute and provider source storage to their respective accounts. This evidence tests a DIFFERENT situation: A provider expects that consumer queries on shared data will be billed entirely to the provider's compute warehouse. The correction required in this case is: Keep shared objects read-only and use an approved local table copy if independent transformations are required.

B:

New direct queries fail, while the exported-file inventory is handled by separate data lifecycle procedures. This evidence tests a DIFFERENT situation: A provider revokes a partner's access to a direct share but expects the partner's previously exported CSV files to vanish. The correction required in this case is: Keep shared objects read-only and use an approved local table copy if independent transformations are required.

D:

A pilot consumer can find the approved listing metadata and request or acquire access as designed. This evidence tests a DIFFERENT situation: A commercial dataset needs pricing, product descriptions and usage discovery, but its provider uses only an internal direct share. The correction required in this case is: Keep shared objects read-only and use an approved local table copy if independent transformations are required.