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 7

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.

Question 61

An engineering team investigates the following Snowflake issue: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time. Which configuration or processing decision is most appropriate?

  1. Evaluate a supported materialized view matching a frequently repeated single-table aggregation.
  2. Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions.
  3. Use ROW_NUMBER over customer partitions with a deterministic ORDER BY and filter via QUALIFY or a subquery.
  4. Inspect query result-cache reuse and execution metrics before attributing the query to active compute.

Explanation

Correct Answer

D:

Inspect query result-cache reuse and execution metrics before attributing the query to active compute. This directly addresses the described Snowflake condition: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time. The mechanism is: Persisted query result caching is distinct from warehouse-local data caching. Verify success using: A repeated eligible query reuses its persisted result when result-cache conditions are satisfied.

Incorrect Answers

A:

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: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time.

B:

Differentiate warehouse-local cache from persisted result cache and test warm versus cold executions. That is suitable for a DIFFERENT Snowflake situation: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. It does not directly resolve the current requirement: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time.

C:

Use ROW_NUMBER over customer partitions with a deterministic ORDER BY and filter via QUALIFY or a subquery. That is suitable for a DIFFERENT Snowflake situation: A team needs the latest event per customer, but SELECT DISTINCT keeps multiple records with different timestamps. It does not directly resolve the current requirement: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time.

Question 62

For a global logistics company, the original problem was: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time. What observation confirms success?

  1. A repeated eligible query reuses its persisted result when result-cache conditions are satisfied.
  2. The chosen design accelerates the targeted lookup with acceptable service-maintenance cost.
  3. Net compute and storage costs improve while frequently used reports retain acceptable latency.
  4. The test selective lookup improves under the approved feature without incorrect results.

Explanation

Correct Answer

A:

A repeated eligible query reuses its persisted result when result-cache conditions are satisfied. This validates the relevant action: Inspect query result-cache reuse and execution metrics before attributing the query to active compute. The underlying Snowflake behavior is: Persisted query result caching is distinct from warehouse-local data caching.

Incorrect Answers

B:

The chosen design accelerates the targeted lookup with acceptable service-maintenance cost. This evidence tests a DIFFERENT situation: A selective point lookup needs acceleration but an engineer wants to recluster an entire table without measuring existing pruning. The correction required in this case is: Inspect query result-cache reuse and execution metrics before attributing the query to active compute.

C:

Net compute and storage costs improve while frequently used reports retain acceptable latency. This evidence tests a DIFFERENT situation: An organization enables multiple materialized views for rarely used reports and sees maintenance charges rising above query savings. The correction required in this case is: Inspect query result-cache reuse and execution metrics before attributing the query to active compute.

D:

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: Inspect query result-cache reuse and execution metrics before attributing the query to active compute.

Question 63

In a case affecting a global logistics company, this issue appears: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time. What explains it?

  1. Search optimization and clustering solve different access patterns and maintenance trade-offs.
  2. Persisted query result caching is distinct from warehouse-local data caching.
  3. Materialized views can maintain precomputed results for eligible single-table queries.
  4. Static pivot category definitions cannot automatically represent every newly appearing dimension value.

Explanation

Correct Answer

B:

Persisted query result caching is distinct from warehouse-local data caching. This explains the condition: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time. The corrective response is: Inspect query result-cache reuse and execution metrics before attributing the query to active compute.

Incorrect Answers

A:

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: Persisted query result caching is distinct from warehouse-local data caching.

C:

Materialized views can maintain precomputed results for eligible single-table queries. That mechanism explains a DIFFERENT Snowflake problem: An analyst wants transparently faster aggregate queries over one large fact table without rewriting every dashboard. Here the relevant mechanism instead is: Persisted query result caching is distinct from warehouse-local data caching.

D:

Static pivot category definitions cannot automatically represent every newly appearing dimension value. That mechanism explains a DIFFERENT Snowflake problem: An analyst pivots event records to monthly metrics but assumes unexpected new event categories appear automatically in a fixed static pivot. Here the relevant mechanism instead is: Persisted query result caching is distinct from warehouse-local data caching.

Question 64

After remediating the Snowflake issue, the team reviews: A frequently repeated report returns instant results, and its owner claims a warehouse ran and earned cache credit savings each time. Which recurring control is most targeted?

  1. Track query-hit frequency and refresh credits for every materialized view.
  2. Compare query savings against maintenance cost and supported SQL limitations.
  3. Record result-cache eligibility and query changes when reporting performance claims.
  4. Include NULL fixtures in transformation and business-rule regression tests.

Explanation

Correct Answer

C:

Record result-cache eligibility and query changes when reporting performance claims. This reduces recurrence of: Persisted query result caching is distinct from warehouse-local data caching. The verification should demonstrate: A repeated eligible query reuses its persisted result when result-cache conditions are satisfied.

Incorrect Answers

A:

Track query-hit frequency and refresh credits for every materialized view. That safeguard is aimed at ANOTHER risk: An organization enables multiple materialized views for rarely used reports and sees maintenance charges rising above query savings. It is less targeted than the control for: Persisted query result caching is distinct from warehouse-local data caching.

B:

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: Persisted query result caching is distinct from warehouse-local data caching.

D:

Include NULL fixtures in transformation and business-rule regression tests. That safeguard is aimed at ANOTHER risk: A customer segmentation query uses CASE in multiple branches without handling NULL values and classifies unknown regions incorrectly. It is less targeted than the control for: Persisted query result caching is distinct from warehouse-local data caching.

Question 65

At a subscription SaaS business, a Snowflake implementation review finds: An ETL process needs to react to changed rows, but it rereads an entire source table every hour. Which action best addresses this requirement?

  1. Create a suitable stream over the source and a controlled downstream task to process tracked changes.
  2. Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites.
  3. Evaluate dynamic tables with supported TARGET_LAG and refresh semantics for the declarative transformation.
  4. Implement explicit NULL handling with CASE/COALESCE and business-approved fallback categories.

Explanation

Correct Answer

A:

Create a suitable stream over the source and a controlled downstream task to process tracked changes. This directly addresses the described Snowflake condition: An ETL process needs to react to changed rows, but it rereads an entire source table every hour. The mechanism is: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them. Verify success using: The consumer processes new changes without rescanning unchanged historical rows every cycle.

Incorrect Answers

B:

Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites. That is suitable for a DIFFERENT Snowflake situation: A scheduled task references a warehouse that is suspended and does not execute after an administrator forgets to resume the task graph. It does not directly resolve the current requirement: An ETL process needs to react to changed rows, but it rereads an entire source table every hour.

C:

Evaluate dynamic tables with supported TARGET_LAG and refresh semantics for the declarative transformation. That is suitable for a DIFFERENT Snowflake situation: A data team maintains a SQL-based bronze-to-silver transformation with fixed freshness targets but writes complicated manual MERGE scheduling code. It does not directly resolve the current requirement: An ETL process needs to react to changed rows, but it rereads an entire source table every hour.

D:

Implement explicit NULL handling with CASE/COALESCE and business-approved fallback categories. That is suitable for a DIFFERENT Snowflake situation: A customer segmentation query uses CASE in multiple branches without handling NULL values and classifies unknown regions incorrectly. It does not directly resolve the current requirement: An ETL process needs to react to changed rows, but it rereads an entire source table every hour.

Question 66

After the approved change, engineers revisit: An ETL process needs to react to changed rows, but it rereads an entire source table every hour. Which result establishes the intended state?

  1. Task history shows cleansing begins only after upstream success according to graph semantics.
  2. The consumer processes new changes without rescanning unchanged historical rows every cycle.
  3. The workflow executes its conditional operations and produces auditable task outcomes.
  4. The rewritten query returns the same rows and scans fewer micro-partitions.

Explanation

Correct Answer

B:

The consumer processes new changes without rescanning unchanged historical rows every cycle. This validates the relevant action: Create a suitable stream over the source and a controlled downstream task to process tracked changes. The underlying Snowflake behavior is: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.

Incorrect Answers

A:

Task history shows cleansing begins only after upstream success according to graph semantics. This evidence tests a DIFFERENT situation: A task DAG should perform cleansing only after an ingest task succeeds, but the team schedules both independently at the same minute. The correction required in this case is: Create a suitable stream over the source and a controlled downstream task to process tracked changes.

C:

The workflow executes its conditional operations and produces auditable task outcomes. This evidence tests a DIFFERENT 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. The correction required in this case is: Create a suitable stream over the source and a controlled downstream task to process tracked changes.

D:

The rewritten query returns the same rows and scans fewer micro-partitions. This evidence tests a DIFFERENT situation: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. The correction required in this case is: Create a suitable stream over the source and a controlled downstream task to process tracked changes.

Question 67

A root-cause investigation considers: An ETL process needs to react to changed rows, but it rereads an entire source table every hour. What is the most applicable explanation?

  1. Dynamic tables express maintained SQL transformations declaratively, whereas manual streams/tasks expose procedural control.
  2. Stream offsets advance through committed consuming DML rather than ordinary inspection queries.
  3. Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.
  4. Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.

Explanation

Correct Answer

C:

Streams maintain change-tracking offsets for a source object, separate from the task that consumes them. This explains the condition: An ETL process needs to react to changed rows, but it rereads an entire source table every hour. The corrective response is: Create a suitable stream over the source and a controlled downstream task to process tracked changes.

Incorrect Answers

A:

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: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.

B:

Stream offsets advance through committed consuming DML rather than ordinary inspection queries. That mechanism explains a DIFFERENT Snowflake problem: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. Here the relevant mechanism instead is: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.

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: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.

Question 68

During operational handoff for this problem: An ETL process needs to react to changed rows, but it rereads an entire source table every hour. Which guardrail should be included?

  1. Set freshness alerts and recovery playbooks for every critical stream.
  2. Monitor refresh failure signals and run schema-compatibility tests before source deployments.
  3. Measure maintenance credits and candidate query selectivity before enabling optimization.
  4. Monitor stream staleness and processing lag to avoid missing retention windows.

Explanation

Correct Answer

D:

Monitor stream staleness and processing lag to avoid missing retention windows. This reduces recurrence of: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them. The verification should demonstrate: The consumer processes new changes without rescanning unchanged historical rows every cycle.

Incorrect Answers

A:

Set freshness alerts and recovery playbooks for every critical stream. That safeguard is aimed at ANOTHER risk: An ingest pipeline uses a stream and task but falls behind for days beyond the underlying change-tracking retention period. It is less targeted than the control for: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.

B:

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: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.

C:

Measure maintenance credits and candidate query selectivity before enabling optimization. That safeguard is aimed at ANOTHER risk: An analytics query searches a small customer ID set in a giant table with no selective access optimization. It is less targeted than the control for: Streams maintain change-tracking offsets for a source object, separate from the task that consumes them.

Question 69

A data-platform team must resolve: A supplier needs to query a Snowflake dataset in the same region but should not receive exported duplicate files each week. Which technical change most directly solves it?

  1. Grant the newly approved table or secure view to the relevant share and verify consumer database visibility.
  2. Create a controlled direct secure share exposing approved objects and grant it to the authorized consumer account.
  3. Revoke the share entitlement and separately manage any exported data under contractual retention controls.
  4. Evaluate an approved Snowflake Data Clean Room analysis with permitted templates and privacy policies.

Explanation

Correct Answer

B:

Create a controlled direct secure share exposing approved objects and grant it to the authorized consumer account. This directly addresses the described Snowflake condition: A supplier needs to query a Snowflake dataset in the same region but should not receive exported duplicate files each week. The mechanism is: Direct secure sharing exposes governed read-only objects without copying the provider's source table storage. Verify success using: The consumer creates an imported database and sees updates to permitted data without file transfers.

Incorrect Answers

A:

Grant the newly approved table or secure view to the relevant share and verify consumer database visibility. That is suitable for a DIFFERENT Snowflake situation: A partner can see a shared database but cannot find a newly added table that the provider assumed would appear automatically. It does not directly resolve the current requirement: A supplier needs to query a Snowflake dataset in the same region but should not receive exported duplicate files each week.

C:

Revoke the share entitlement and separately manage any exported data under contractual retention controls. That is suitable for a DIFFERENT Snowflake situation: A provider revokes a partner's access to a direct share but expects the partner's previously exported CSV files to vanish. It does not directly resolve the current requirement: A supplier needs to query a Snowflake dataset in the same region but should not receive exported duplicate files each week.

D:

Evaluate an approved Snowflake Data Clean Room analysis with permitted templates and privacy policies. That is suitable for a DIFFERENT Snowflake situation: Two healthcare organizations want joint analysis of patient-overlap statistics but must avoid exposing identifiable source records directly. It does not directly resolve the current requirement: A supplier needs to query a Snowflake dataset in the same region but should not receive exported duplicate files each week.

Question 70

A Snowflake acceptance test follows this incident: A supplier needs to query a Snowflake dataset in the same region but should not receive exported duplicate files each week. What evidence most directly proves the correction?

  1. Usage reports attribute consumer query compute and provider source storage to their respective accounts.
  2. A consumer role can query only the added approved object after the share grant is applied.
  3. The consumer creates an imported database and sees updates to permitted data without file transfers.
  4. The approved aggregate overlap metric is returned while raw patient identities remain inaccessible to the partner role.

Explanation

Correct Answer

C:

The consumer creates an imported database and sees updates to permitted data without file transfers. This validates the relevant action: Create a controlled direct secure share exposing approved objects and grant it to the authorized consumer account. The underlying Snowflake behavior is: Direct secure sharing exposes governed read-only objects without copying the provider's source table storage.

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: Create a controlled direct secure share exposing approved objects and grant it to the authorized consumer account.

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: Create a controlled direct secure share exposing approved objects and grant it to the authorized consumer account.

D:

The approved aggregate overlap metric is returned while raw patient identities remain inaccessible to the partner role. This evidence tests a DIFFERENT situation: Two healthcare organizations want joint analysis of patient-overlap statistics but must avoid exposing identifiable source records directly. The correction required in this case is: Create a controlled direct secure share exposing approved objects and grant it to the authorized consumer account.