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 17

Question 160

After remediating the Snowflake issue, the team reviews: A reader account query bill rises unexpectedly and the consuming partner assumes its own organization pays the Snowflake compute. Which recurring control is most targeted?

  1. Schedule consumer-perspective access and policy regression tests for every data product change.
  2. Review approved computations, thresholds and privacy tests before partner onboarding.
  3. Set reader-account spend alerts and usage agreements before giving access.
  4. Document cost ownership in each sharing agreement.

Explanation

Correct Answer

C:

Set reader-account spend alerts and usage agreements before giving access. This reduces recurrence of: The provider manages and pays reader-account resources, unlike ordinary full-account direct-share consumers. The verification should demonstrate: Cost reports identify reader account workload billed to the provider under agreed limits.

Incorrect Answers

A:

Schedule consumer-perspective access and policy regression tests for every data product change. That safeguard is aimed at ANOTHER risk: A company publishes an analytics dataset to collaborators but never checks whether shared policies expose new sensitive columns. It is less targeted than the control for: The provider manages and pays reader-account resources, unlike ordinary full-account direct-share consumers.

B:

Review approved computations, thresholds and privacy tests before partner onboarding. That safeguard is aimed at ANOTHER risk: Two healthcare organizations want joint analysis of patient-overlap statistics but must avoid exposing identifiable source records directly. It is less targeted than the control for: The provider manages and pays reader-account resources, unlike ordinary full-account direct-share consumers.

D:

Document cost ownership in each sharing agreement. That safeguard is aimed at ANOTHER risk: A provider expects that consumer queries on shared data will be billed entirely to the provider's compute warehouse. It is less targeted than the control for: The provider manages and pays reader-account resources, unlike ordinary full-account direct-share consumers.

Question 161

At a subscription SaaS business, a Snowflake implementation review finds: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. Which action best addresses this requirement?

  1. Route ETL and BI workloads to separate appropriately sized warehouses sharing the same persisted data.
  2. Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing.
  3. Include relevant Snowflake serverless usage views and billing categories in the cost attribution model.
  4. Use a permanent or transient table if the intermediate results must outlive the session.

Explanation

Correct Answer

A:

Route ETL and BI workloads to separate appropriately sized warehouses sharing the same persisted data. This directly addresses the described Snowflake condition: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. The mechanism is: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies. Verify success using: BI latency improves during scheduled ETL while both warehouses query the same tables.

Incorrect Answers

B:

Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing. That is suitable for a DIFFERENT Snowflake situation: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. It does not directly resolve the current requirement: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays.

C:

Include relevant Snowflake serverless usage views and billing categories in the cost attribution model. That is suitable for a DIFFERENT Snowflake situation: A cost report attributes every platform charge to user warehouse credit meters, leaving serverless processing unaccounted for. It does not directly resolve the current requirement: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays.

D:

Use a permanent or transient table if the intermediate results must outlive the session. That is suitable for a DIFFERENT Snowflake situation: A data engineer expects a temporary table created in one session to remain visible after the session ends. It does not directly resolve the current requirement: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays.

Question 162

After the approved change, engineers revisit: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. Which result establishes the intended state?

  1. Metadata-only inspection completes without a warehouse running when the operation is eligible.
  2. BI latency improves during scheduled ETL while both warehouses query the same tables.
  3. The client resolves to the intended account, not a similarly named account in another region.
  4. At low demand one cluster runs; during queued demand extra clusters start within the configured maximum.

Explanation

Correct Answer

B:

BI latency improves during scheduled ETL while both warehouses query the same tables. This validates the relevant action: Route ETL and BI workloads to separate appropriately sized warehouses sharing the same persisted data. The underlying Snowflake behavior is: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.

Incorrect Answers

A:

Metadata-only inspection completes without a warehouse running when the operation is eligible. This evidence tests a DIFFERENT situation: An application requires a low-latency metadata operation, but operations assumes every SQL statement must start a warehouse. The correction required in this case is: Route ETL and BI workloads to separate appropriately sized warehouses sharing the same persisted data.

C:

The client resolves to the intended account, not a similarly named account in another region. This evidence tests a DIFFERENT situation: An application connects from a new region and assumes account-level identifiers are globally interchangeable across Snowflake organizations. The correction required in this case is: Route ETL and BI workloads to separate appropriately sized warehouses sharing the same persisted data.

D:

At low demand one cluster runs; during queued demand extra clusters start within the configured maximum. This evidence tests a DIFFERENT situation: A team sets MAX_CLUSTER_COUNT to four but leaves MIN_CLUSTER_COUNT at one and expects four clusters to run continuously. The correction required in this case is: Route ETL and BI workloads to separate appropriately sized warehouses sharing the same persisted data.

Question 163

A root-cause investigation considers: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. What is the most applicable explanation?

  1. Snowflake manages physical data storage and micro-partition organization for standard internal tables.
  2. Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.
  3. Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.
  4. Text-to-SQL accuracy depends on controlled semantic definitions and database permissions.

Explanation

Correct Answer

C:

Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies. This explains the condition: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. The corrective response is: Route ETL and BI workloads to separate appropriately sized warehouses sharing the same persisted data.

Incorrect Answers

A:

Snowflake manages physical data storage and micro-partition organization for standard internal tables. That mechanism explains a DIFFERENT Snowflake problem: A customer migrates an on-prem database and wants to manage underlying Snowflake storage files directly for normal tables. Here the relevant mechanism instead is: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.

B:

Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables. That mechanism explains a DIFFERENT Snowflake problem: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. Here the relevant mechanism instead is: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.

D:

Text-to-SQL accuracy depends on controlled semantic definitions and database permissions. That mechanism explains a DIFFERENT Snowflake problem: A business team asks an LLM to answer revenue questions but the model frequently invents column names and joins. Here the relevant mechanism instead is: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.

Question 164

During operational handoff for this problem: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. Which guardrail should be included?

  1. Review Query History and warehouse load before adjusting warehouse size.
  2. Benchmark realistic transactional and analytic workloads before warehouse consolidation.
  3. Test scheduled automation after warehouse property changes.
  4. Track per-workload warehouses and ownership to prevent resource contention returning.

Explanation

Correct Answer

D:

Track per-workload warehouses and ownership to prevent resource contention returning. This reduces recurrence of: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies. The verification should demonstrate: BI latency improves during scheduled ETL while both warehouses query the same tables.

Incorrect Answers

A:

Review Query History and warehouse load before adjusting warehouse size. That safeguard is aimed at ANOTHER risk: A reporting dashboard slows during warehouse saturation, and an analyst proposes resizing cloud services instead of compute. It is less targeted than the control for: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.

B:

Benchmark realistic transactional and analytic workloads before warehouse consolidation. That safeguard is aimed at ANOTHER risk: A pipeline architect puts transactional row mutation processing on an ad hoc BI query warehouse with no workload isolation. It is less targeted than the control for: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.

C:

Test scheduled automation after warehouse property changes. That safeguard is aimed at ANOTHER risk: A team changes AUTO_RESUME to FALSE on a suspended report warehouse and then schedules automatic queries without explicit starts. It is less targeted than the control for: Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.

Question 165

A data-platform team must resolve: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries. Which technical change most directly solves it?

  1. Explain and configure the supported multi-cluster scaling policy based on concurrent demand and minimum capacity.
  2. Test a larger warehouse and inspect memory/spillage metrics rather than adding only more clusters.
  3. Measure cold-start or warehouse cache effects, then tune resume scheduling or caching expectations.
  4. Rely on Snowflake-managed micro-partitions and design predicates or clustering strategy appropriately.

Explanation

Correct Answer

B:

Test a larger warehouse and inspect memory/spillage metrics rather than adding only more clusters. This directly addresses the described Snowflake condition: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries. The mechanism is: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand. Verify success using: The same transformation reduces local and remote spill and improves runtime within the cost budget.

Incorrect Answers

A:

Explain and configure the supported multi-cluster scaling policy based on concurrent demand and minimum capacity. That is suitable for a DIFFERENT Snowflake situation: A team sets MAX_CLUSTER_COUNT to four but leaves MIN_CLUSTER_COUNT at one and expects four clusters to run continuously. It does not directly resolve the current requirement: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries.

C:

Measure cold-start or warehouse cache effects, then tune resume scheduling or caching expectations. That is suitable for a DIFFERENT Snowflake situation: An ETL warehouse repeatedly takes time to warm up after long pauses, and users blame a stored-data corruption issue. It does not directly resolve the current requirement: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries.

D:

Rely on Snowflake-managed micro-partitions and design predicates or clustering strategy appropriately. That is suitable for a DIFFERENT Snowflake situation: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. It does not directly resolve the current requirement: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries.

Question 166

A Snowflake acceptance test follows this incident: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries. What evidence most directly proves the correction?

  1. A scheduled query starts without a manual operator action when automatic resume is enabled.
  2. Overnight cluster usage reduces while peak-time workloads still scale within limits.
  3. The same transformation reduces local and remote spill and improves runtime within the cost budget.
  4. The pilot stays inside an approved spend envelope while representative outputs remain useful.

Explanation

Correct Answer

C:

The same transformation reduces local and remote spill and improves runtime within the cost budget. This validates the relevant action: Test a larger warehouse and inspect memory/spillage metrics rather than adding only more clusters. The underlying Snowflake behavior is: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

Incorrect Answers

A:

A scheduled query starts without a manual operator action when automatic resume is enabled. This evidence tests a DIFFERENT situation: A team changes AUTO_RESUME to FALSE on a suspended report warehouse and then schedules automatic queries without explicit starts. The correction required in this case is: Test a larger warehouse and inspect memory/spillage metrics rather than adding only more clusters.

B:

Overnight cluster usage reduces while peak-time workloads still scale within limits. This evidence tests a DIFFERENT situation: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. The correction required in this case is: Test a larger warehouse and inspect memory/spillage metrics rather than adding only more clusters.

D:

The pilot stays inside an approved spend envelope while representative outputs remain useful. This evidence tests a DIFFERENT situation: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. The correction required in this case is: Test a larger warehouse and inspect memory/spillage metrics rather than adding only more clusters.

Question 167

The data-platform team observes: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries. Which architectural or processing fact matters most?

  1. A suspended warehouse with auto-resume disabled does not automatically wake for a query.
  2. An unsuspended warehouse can consume compute credits while no SQL is actively running.
  3. Fail-safe is not user-accessible historical querying; it is a Snowflake-managed recovery period.
  4. Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

Explanation

Correct Answer

D:

Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand. This explains the condition: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries. The corrective response is: Test a larger warehouse and inspect memory/spillage metrics rather than adding only more clusters.

Incorrect Answers

A:

A suspended warehouse with auto-resume disabled does not automatically wake for a query. That mechanism explains a DIFFERENT Snowflake problem: A team changes AUTO_RESUME to FALSE on a suspended report warehouse and then schedules automatic queries without explicit starts. Here the relevant mechanism instead is: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

B:

An unsuspended warehouse can consume compute credits while no SQL is actively running. That mechanism explains a DIFFERENT Snowflake problem: A scheduled workload runs briefly every hour, but its dedicated warehouse remains running between jobs. Here the relevant mechanism instead is: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

C:

Fail-safe is not user-accessible historical querying; it is a Snowflake-managed recovery period. That mechanism explains a DIFFERENT Snowflake problem: An analyst expects to run SELECT AT a historical timestamp after Time Travel retention has expired into Fail-safe. Here the relevant mechanism instead is: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

Question 168

For a university data platform, this issue must not recur: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries. Which review control fits best?

  1. Separate memory-intensive query tuning from queuing mitigation reviews.
  2. Document data consistency separately from performance cache behavior.
  3. Review autoscaling behavior with both idle and busy workload test cases.
  4. Test input parsing and malformed payload handling in ingestion contracts.

Explanation

Correct Answer

A:

Separate memory-intensive query tuning from queuing mitigation reviews. This reduces recurrence of: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand. The verification should demonstrate: The same transformation reduces local and remote spill and improves runtime within the cost budget.

Incorrect Answers

B:

Document data consistency separately from performance cache behavior. That safeguard is aimed at ANOTHER risk: Analysts assume moving a query to another warehouse duplicates cached results and changes the source table. It is less targeted than the control for: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

C:

Review autoscaling behavior with both idle and busy workload test cases. That safeguard is aimed at ANOTHER risk: A team sets MAX_CLUSTER_COUNT to four but leaves MIN_CLUSTER_COUNT at one and expects four clusters to run continuously. It is less targeted than the control for: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

D:

Test input parsing and malformed payload handling in ingestion contracts. That safeguard is aimed at ANOTHER risk: A migration tool defines a table column as VARCHAR then assumes all JSON path operators will work on it without conversion. It is less targeted than the control for: Warehouse size increases resources available per query; multi-cluster concurrency primarily addresses simultaneous query demand.

Question 169

In a governed Snowflake environment, the reported condition is: A developer asks to recover a table dropped yesterday within its configured retention window. What should be implemented first?

  1. Explain that historical SQL query access ends with Time Travel and use the proper support escalation only if Fail-safe applies.
  2. Verify current schema resolution rules and test historical data access with the supported historical query semantics.
  3. Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts.
  4. Evaluate an available governed Snowflake Cortex AI function for permitted text analysis after access and cost review.

Explanation

Correct Answer

C:

Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts. This directly addresses the described Snowflake condition: A developer asks to recover a table dropped yesterday within its configured retention window. The mechanism is: Time Travel supports recovery of dropped supported objects while their retention remains valid. Verify success using: Recovered table data matches the point within its permitted Time Travel retention window.

Incorrect Answers

A:

Explain that historical SQL query access ends with Time Travel and use the proper support escalation only if Fail-safe applies. That is suitable for a DIFFERENT Snowflake situation: An analyst expects to run SELECT AT a historical timestamp after Time Travel retention has expired into Fail-safe. It does not directly resolve the current requirement: A developer asks to recover a table dropped yesterday within its configured retention window.

B:

Verify current schema resolution rules and test historical data access with the supported historical query semantics. That is suitable for a DIFFERENT Snowflake situation: A finance audit expects a Time Travel historical query to reproduce every former schema definition after a column rename. It does not directly resolve the current requirement: A developer asks to recover a table dropped yesterday within its configured retention window.

D:

Evaluate an available governed Snowflake Cortex AI function for permitted text analysis after access and cost review. That is suitable for a DIFFERENT Snowflake situation: A department wants sentiment analysis in SQL but proposes shipping every customer comment to an ungoverned third-party endpoint. It does not directly resolve the current requirement: A developer asks to recover a table dropped yesterday within its configured retention window.

Question 170

A test plan evaluates: A developer asks to recover a table dropped yesterday within its configured retention window. Which evidence should be required before release?

  1. Time-filtered SQL queries prune eligible partitions without user-maintained folder partition definitions.
  2. A region-level outage drill has an independent approved recovery path rather than relying on a local clone.
  3. Execution timing and credits improve under measured query bursts without keeping the warehouse idle all day.
  4. Recovered table data matches the point within its permitted Time Travel retention window.

Explanation

Correct Answer

D:

Recovered table data matches the point within its permitted Time Travel retention window. This validates the relevant action: Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts. The underlying Snowflake behavior is: Time Travel supports recovery of dropped supported objects while their retention remains valid.

Incorrect Answers

A:

Time-filtered SQL queries prune eligible partitions without user-maintained folder partition definitions. This evidence tests a DIFFERENT situation: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. The correction required in this case is: Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts.

B:

A region-level outage drill has an independent approved recovery path rather than relying on a local clone. This evidence tests a DIFFERENT situation: A data steward uses a zero-copy clone as a replacement for a remote recovery copy in a separate cloud region. The correction required in this case is: Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts.

C:

Execution timing and credits improve under measured query bursts without keeping the warehouse idle all day. This evidence tests a DIFFERENT situation: A recurring report finishes in two minutes but its warehouse auto-suspends after an extremely short idle timeout between closely spaced queries. The correction required in this case is: Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts.