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 48

Question 470

A Snowflake acceptance test follows this incident: A provider expects that consumer queries on shared data will be billed entirely to the provider's compute warehouse. What evidence most directly proves the correction?

  1. The consumer can query the shared table and can modify only its own separate local derived data.
  2. A consumer role can query only the added approved object after the share grant is applied.
  3. Usage reports attribute consumer query compute and provider source storage to their respective accounts.
  4. A representative consumer query remains valid through an approved schema evolution release.

Explanation

Correct Answer

C:

Usage reports attribute consumer query compute and provider source storage to their respective accounts. This validates the relevant action: Model the shared-data consumer's own warehouse compute and the provider's ongoing storage responsibilities separately. The underlying Snowflake behavior is: Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

Incorrect Answers

A:

The consumer can query the shared table and can modify only its own separate local derived data. This evidence tests a DIFFERENT situation: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access. The correction required in this case is: Model the shared-data consumer's own warehouse compute and the provider's ongoing storage responsibilities separately.

B:

A consumer role can query only the added approved object after the share grant is applied. This evidence tests a DIFFERENT situation: A partner can see a shared database but cannot find a newly added table that the provider assumed would appear automatically. The correction required in this case is: Model the shared-data consumer's own warehouse compute and the provider's ongoing storage responsibilities separately.

D:

A representative consumer query remains valid through an approved schema evolution release. This evidence tests a DIFFERENT situation: A data provider changes a shared table schema in a listed data product and breaks downstream customer queries. The correction required in this case is: Model the shared-data consumer's own warehouse compute and the provider's ongoing storage responsibilities separately.

Question 471

The data-platform team observes: A provider expects that consumer queries on shared data will be billed entirely to the provider's compute warehouse. Which architectural or processing fact matters most?

  1. Direct secure sharing exposes governed read-only objects without copying the provider's source table storage.
  2. Direct shares are region-scoped; cross-region sharing needs a supported different distribution mechanism.
  3. Secure shares expose read-only data, while application distribution can require different packaging and permissions.
  4. Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

Explanation

Correct Answer

D:

Secure sharing allows consumers to query their own compute while data storage remains provider-managed. This explains the condition: A provider expects that consumer queries on shared data will be billed entirely to the provider's compute warehouse. The corrective response is: Model the shared-data consumer's own warehouse compute and the provider's ongoing storage responsibilities separately.

Incorrect Answers

A:

Direct secure sharing exposes governed read-only objects without copying the provider's source table storage. That mechanism explains a DIFFERENT Snowflake problem: A supplier needs to query a Snowflake dataset in the same region but should not receive exported duplicate files each week. Here the relevant mechanism instead is: Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

B:

Direct shares are region-scoped; cross-region sharing needs a supported different distribution mechanism. That mechanism explains a DIFFERENT Snowflake problem: Two Snowflake accounts are in different regions and a provider assumes a direct share can be added across the regions immediately. Here the relevant mechanism instead is: Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

C:

Secure shares expose read-only data, while application distribution can require different packaging and permissions. That mechanism explains a DIFFERENT Snowflake problem: A provider shares a static dataset with a consumer but later learns that the partner needs a governed application, not only tables. Here the relevant mechanism instead is: Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

Question 472

For a public-sector reporting unit, this issue must not recur: A provider expects that consumer queries on shared data will be billed entirely to the provider's compute warehouse. Which review control fits best?

  1. Document cost ownership in each sharing agreement.
  2. Include derived and exported data disposition in partner offboarding.
  3. Document read-only semantics in producer-consumer data contracts.
  4. Require legal, security and billing approval before publishing priced data products.

Explanation

Correct Answer

A:

Document cost ownership in each sharing agreement. This reduces recurrence of: Secure sharing allows consumers to query their own compute while data storage remains provider-managed. The verification should demonstrate: Usage reports attribute consumer query compute and provider source storage to their respective accounts.

Incorrect Answers

B:

Include derived and exported data disposition in partner offboarding. That safeguard is aimed at ANOTHER risk: A provider revokes a partner's access to a direct share but expects the partner's previously exported CSV files to vanish. It is less targeted than the control for: Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

C:

Document read-only semantics in producer-consumer data contracts. That safeguard is aimed at ANOTHER risk: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access. It is less targeted than the control for: Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

D:

Require legal, security and billing approval before publishing priced data products. That safeguard is aimed at ANOTHER risk: A commercial dataset needs pricing, product descriptions and usage discovery, but its provider uses only an internal direct share. It is less targeted than the control for: Secure sharing allows consumers to query their own compute while data storage remains provider-managed.

Question 473

In a governed Snowflake environment, the reported condition is: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. What should be implemented first?

  1. Show the three layers separately: managed storage, virtual warehouse compute, and cloud services coordination.
  2. Include relevant Snowflake serverless usage views and billing categories in the cost attribution model.
  3. Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing.
  4. Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors.

Explanation

Correct Answer

C:

Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing. This directly addresses the described Snowflake condition: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. The mechanism is: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables. Verify success using: A before-and-after cost model changes compute allocation while table storage volume remains independent.

Incorrect Answers

A:

Show the three layers separately: managed storage, virtual warehouse compute, and cloud services coordination. That is suitable for a DIFFERENT Snowflake situation: An architecture slide describes Snowflake's services layer as storing every table's raw compressed micro-partitions. It does not directly resolve the current requirement: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables.

B:

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: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables.

D:

Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors. That is suitable for a DIFFERENT Snowflake situation: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. It does not directly resolve the current requirement: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables.

Question 474

A test plan evaluates: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. Which evidence should be required before release?

  1. Reconciled totals include serverless ingestion or task credits in addition to warehouse credits.
  2. The reporting warehouse completes the sample dashboard while cloud services metadata operations remain unaffected.
  3. The snapshot contains pre-delete rows while the current table retains its later changes.
  4. A before-and-after cost model changes compute allocation while table storage volume remains independent.

Explanation

Correct Answer

D:

A before-and-after cost model changes compute allocation while table storage volume remains independent. This validates the relevant action: Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing. The underlying Snowflake behavior is: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.

Incorrect Answers

A:

Reconciled totals include serverless ingestion or task credits in addition to warehouse credits. This evidence tests a DIFFERENT situation: A cost report attributes every platform charge to user warehouse credit meters, leaving serverless processing unaccounted for. The correction required in this case is: Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing.

B:

The reporting warehouse completes the sample dashboard while cloud services metadata operations remain unaffected. This evidence tests a DIFFERENT situation: A reporting dashboard slows during warehouse saturation, and an analyst proposes resizing cloud services instead of compute. The correction required in this case is: Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing.

C:

The snapshot contains pre-delete rows while the current table retains its later changes. This evidence tests a DIFFERENT situation: A team wants a historical snapshot of a supported table at the state before a mistaken DELETE within retention. The correction required in this case is: Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing.

Question 475

A Snowflake incident report notes: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. What underlying mechanism explains the behavior?

  1. Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.
  2. Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies.
  3. Snowflake accounts have region and organization context that matters for connection routing.
  4. Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

Explanation

Correct Answer

A:

Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables. This explains the condition: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. The corrective response is: Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing.

Incorrect Answers

B:

Independent compute warehouses can access common Snowflake-managed storage without duplicate table copies. That mechanism explains a DIFFERENT Snowflake problem: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. Here the relevant mechanism instead is: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.

C:

Snowflake accounts have region and organization context that matters for connection routing. That mechanism explains a DIFFERENT Snowflake problem: An application connects from a new region and assumes account-level identifiers are globally interchangeable across Snowflake organizations. Here the relevant mechanism instead is: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.

D:

Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules. That mechanism explains a DIFFERENT Snowflake problem: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. Here the relevant mechanism instead is: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.

Question 476

A platform governance committee considers: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. What preventive check should be standardized?

  1. Track per-workload warehouses and ownership to prevent resource contention returning.
  2. Review billing dimensions separately for storage, compute and serverless services.
  3. Review Query History and warehouse load before adjusting warehouse size.
  4. Review total billable runtime and query delay together when tuning suspend settings.

Explanation

Correct Answer

B:

Review billing dimensions separately for storage, compute and serverless services. This reduces recurrence of: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables. The verification should demonstrate: A before-and-after cost model changes compute allocation while table storage volume remains independent.

Incorrect Answers

A:

Track per-workload warehouses and ownership to prevent resource contention returning. That safeguard is aimed at ANOTHER risk: An ETL process consumes resources on the same warehouse as interactive BI, causing predictable reporting delays. It is less targeted than the control for: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.

C:

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: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.

D:

Review total billable runtime and query delay together when tuning suspend settings. That safeguard is aimed at ANOTHER risk: A recurring report finishes in two minutes but its warehouse auto-suspends after an extremely short idle timeout between closely spaced queries. It is less targeted than the control for: Warehouse sizing affects query compute credits, not the number of copies of shared persisted tables.

Question 477

An engineering team investigates the following Snowflake issue: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. Which configuration or processing decision is most appropriate?

  1. Evaluate multi-cluster warehouse concurrency and appropriate min/max clusters rather than only increasing one cluster size.
  2. Temporarily size the warehouse for the bulk load and restore a measured right-sized baseline afterwards.
  3. Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts.
  4. Use an appropriate AUTO_SCALE configuration and lower minimum clusters where SLAs permit.

Explanation

Correct Answer

D:

Use an appropriate AUTO_SCALE configuration and lower minimum clusters where SLAs permit. This directly addresses the described Snowflake condition: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. The mechanism is: Minimum active clusters set baseline capacity and cost even with low concurrency. Verify success using: Overnight cluster usage reduces while peak-time workloads still scale within limits.

Incorrect Answers

A:

Evaluate multi-cluster warehouse concurrency and appropriate min/max clusters rather than only increasing one cluster size. That is suitable for a DIFFERENT Snowflake situation: A customer reports long query queues when 40 dashboard users connect, yet each individual query runs quickly alone. It does not directly resolve the current requirement: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period.

B:

Temporarily size the warehouse for the bulk load and restore a measured right-sized baseline afterwards. That is suitable for a DIFFERENT Snowflake situation: A team needs rapid load experimentation but permanently sets a high warehouse size after the one-time bulk import. It does not directly resolve the current requirement: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period.

C:

Use UNDROP TABLE or supported Time Travel recovery according to object retention and name conflicts. That is suitable for a DIFFERENT Snowflake situation: A developer asks to recover a table dropped yesterday within its configured retention window. It does not directly resolve the current requirement: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period.

Question 478

For an e-commerce operations team, the original problem was: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. What observation confirms success?

  1. Overnight cluster usage reduces while peak-time workloads still scale within limits.
  2. The same transformation reduces local and remote spill and improves runtime within the cost budget.
  3. At low demand one cluster runs; during queued demand extra clusters start within the configured maximum.
  4. Billing traces storage growth to retained changed micro-partition versions rather than unrelated compute capacity.

Explanation

Correct Answer

A:

Overnight cluster usage reduces while peak-time workloads still scale within limits. This validates the relevant action: Use an appropriate AUTO_SCALE configuration and lower minimum clusters where SLAs permit. The underlying Snowflake behavior is: Minimum active clusters set baseline capacity and cost even with low concurrency.

Incorrect Answers

B:

The same transformation reduces local and remote spill and improves runtime within the cost budget. This evidence tests a DIFFERENT situation: A large transformation consistently spills intermediate data, while the warehouse has almost no queued queries. The correction required in this case is: Use an appropriate AUTO_SCALE configuration and lower minimum clusters where SLAs permit.

C:

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: Use an appropriate AUTO_SCALE configuration and lower minimum clusters where SLAs permit.

D:

Billing traces storage growth to retained changed micro-partition versions rather than unrelated compute capacity. This evidence tests a DIFFERENT situation: A storage report shows unexpected historical bytes after frequent updates to a large permanent table. The correction required in this case is: Use an appropriate AUTO_SCALE configuration and lower minimum clusters where SLAs permit.

Question 479

In a case affecting an e-commerce operations team, this issue appears: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. What explains it?

  1. An unsuspended warehouse can consume compute credits while no SQL is actively running.
  2. Minimum active clusters set baseline capacity and cost even with low concurrency.
  3. Warehouse size can be adjusted without rebuilding stored data and need not remain oversized.
  4. Fail-safe is not user-accessible historical querying; it is a Snowflake-managed recovery period.

Explanation

Correct Answer

B:

Minimum active clusters set baseline capacity and cost even with low concurrency. This explains the condition: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. The corrective response is: Use an appropriate AUTO_SCALE configuration and lower minimum clusters where SLAs permit.

Incorrect Answers

A:

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: Minimum active clusters set baseline capacity and cost even with low concurrency.

C:

Warehouse size can be adjusted without rebuilding stored data and need not remain oversized. That mechanism explains a DIFFERENT Snowflake problem: A team needs rapid load experimentation but permanently sets a high warehouse size after the one-time bulk import. Here the relevant mechanism instead is: Minimum active clusters set baseline capacity and cost even with low concurrency.

D:

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: Minimum active clusters set baseline capacity and cost even with low concurrency.

Question 480

After remediating the Snowflake issue, the team reviews: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. Which recurring control is most targeted?

  1. Correlate client-side timestamps with warehouse queued and execution metrics.
  2. Test scheduled automation after warehouse property changes.
  3. Review min and max cluster settings against real hourly demand.
  4. Review billing dimensions separately for storage, compute and serverless services.

Explanation

Correct Answer

C:

Review min and max cluster settings against real hourly demand. This reduces recurrence of: Minimum active clusters set baseline capacity and cost even with low concurrency. The verification should demonstrate: Overnight cluster usage reduces while peak-time workloads still scale within limits.

Incorrect Answers

A:

Correlate client-side timestamps with warehouse queued and execution metrics. That safeguard is aimed at ANOTHER risk: Operations increases warehouse size but sees no reduction in lock-like application-side queueing caused by upstream connection limits. It is less targeted than the control for: Minimum active clusters set baseline capacity and cost even with low concurrency.

B:

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: Minimum active clusters set baseline capacity and cost even with low concurrency.

D:

Review billing dimensions separately for storage, compute and serverless services. That safeguard is aimed at ANOTHER risk: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. It is less targeted than the control for: Minimum active clusters set baseline capacity and cost even with low concurrency.