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 15

Question 140

A platform governance committee considers: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. What preventive check should be standardized?

  1. Document expected tie behavior in analytic report requirements.
  2. Include empty-array and missing-key cases in flattening tests.
  3. Use boundary and late-arriving data tests for rolling aggregate SQL.
  4. Track query-hit frequency and refresh credits for every materialized view.

Explanation

Correct Answer

B:

Include empty-array and missing-key cases in flattening tests. This reduces recurrence of: FLATTEN expands nested semi-structured arrays into relational rows. The verification should demonstrate: The output includes one row per intended order line while preserving source order identifiers.

Incorrect Answers

A:

Document expected tie behavior in analytic report requirements. That safeguard is aimed at ANOTHER risk: A finance report uses RANK to assign unique row numbers but produces ties and gaps in the sequence. It is less targeted than the control for: FLATTEN expands nested semi-structured arrays into relational rows.

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: FLATTEN expands nested semi-structured arrays into relational rows.

D:

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: FLATTEN expands nested semi-structured arrays into relational rows.

Question 141

An engineering team investigates the following Snowflake issue: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. 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. Evaluate a supported materialized view matching a frequently repeated single-table aggregation.
  3. Benchmark multiple warehouse sizes and calculate credits per successful workload with equal input sizes.
  4. Allow Snowflake to reexecute or invalidate cached results when underlying data freshness requirements change.

Explanation

Correct Answer

D:

Allow Snowflake to reexecute or invalidate cached results when underlying data freshness requirements change. This directly addresses the described Snowflake condition: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. The mechanism is: Persisted result reuse is subject to data freshness and other cache eligibility conditions. Verify success using: The dashboard reflects committed updates rather than relying on stale cached output.

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 dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid.

B:

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 dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid.

C:

Benchmark multiple warehouse sizes and calculate credits per successful workload with equal input sizes. That is suitable for a DIFFERENT Snowflake situation: A data engineer expects a larger warehouse always to reduce a query's credit cost even if runtime barely changes. It does not directly resolve the current requirement: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid.

Question 142

For an e-commerce operations team, the original problem was: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. What observation confirms success?

  1. The dashboard reflects committed updates rather than relying on stale cached output.
  2. The chosen pipeline computes the expected join output under supported refresh semantics.
  3. Net compute and storage costs improve while frequently used reports retain acceptable latency.
  4. A representative source update reaches the materialized result within the agreed target lag and refresh status is visible.

Explanation

Correct Answer

A:

The dashboard reflects committed updates rather than relying on stale cached output. This validates the relevant action: Allow Snowflake to reexecute or invalidate cached results when underlying data freshness requirements change. The underlying Snowflake behavior is: Persisted result reuse is subject to data freshness and other cache eligibility conditions.

Incorrect Answers

B:

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: Allow Snowflake to reexecute or invalidate cached results when underlying data freshness requirements change.

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: Allow Snowflake to reexecute or invalidate cached results when underlying data freshness requirements change.

D:

A representative source update reaches the materialized result within the agreed target lag and refresh status is visible. This evidence tests a DIFFERENT situation: A data team maintains a SQL-based bronze-to-silver transformation with fixed freshness targets but writes complicated manual MERGE scheduling code. The correction required in this case is: Allow Snowflake to reexecute or invalidate cached results when underlying data freshness requirements change.

Question 143

In a case affecting an e-commerce operations team, this issue appears: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. What explains it?

  1. Warehouse-local data cache belongs to a compute environment, unlike global persisted query results.
  2. Persisted result reuse is subject to data freshness and other cache eligibility conditions.
  3. Materialized view definition constraints differ from general declarative dynamic tables and procedural tasks.
  4. Materialized pipeline freshness depends on successful refresh and compatible source definitions.

Explanation

Correct Answer

B:

Persisted result reuse is subject to data freshness and other cache eligibility conditions. This explains the condition: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. The corrective response is: Allow Snowflake to reexecute or invalidate cached results when underlying data freshness requirements change.

Incorrect Answers

A:

Warehouse-local data cache belongs to a compute environment, unlike global persisted query results. That mechanism explains a DIFFERENT Snowflake problem: A warehouse suspends between reporting sessions and analysts incorrectly assume its local disk cache is shared with other warehouses. Here the relevant mechanism instead is: Persisted result reuse is subject to data freshness and other cache eligibility conditions.

C:

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: Persisted result reuse is subject to data freshness and other cache eligibility conditions.

D:

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: Persisted result reuse is subject to data freshness and other cache eligibility conditions.

Question 144

After remediating the Snowflake issue, the team reviews: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. Which recurring control is most targeted?

  1. Compare query savings against maintenance cost and supported SQL limitations.
  2. Track query-hit frequency and refresh credits for every materialized view.
  3. Test post-update reporting freshness whenever enabling report cache assumptions.
  4. Use query linting and controlled row-count assertions for production joins.

Explanation

Correct Answer

C:

Test post-update reporting freshness whenever enabling report cache assumptions. This reduces recurrence of: Persisted result reuse is subject to data freshness and other cache eligibility conditions. The verification should demonstrate: The dashboard reflects committed updates rather than relying on stale cached output.

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: Persisted result reuse is subject to data freshness and other cache eligibility conditions.

B:

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 result reuse is subject to data freshness and other cache eligibility conditions.

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: Persisted result reuse is subject to data freshness and other cache eligibility conditions.

Question 145

At a retail analytics group, a Snowflake implementation review finds: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. Which action best addresses this requirement?

  1. Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection.
  2. Resume the authorized root task and verify warehouse or serverless configuration plus graph prerequisites.
  3. Create a suitable stream over the source and a controlled downstream task to process tracked changes.
  4. Inspect query profile compilation versus execution and limit excessive dynamic SQL statement variation where feasible.

Explanation

Correct Answer

A:

Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection. This directly addresses the described Snowflake condition: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. The mechanism is: Stream offsets advance through committed consuming DML rather than ordinary inspection queries. Verify success using: A committed consumer updates the downstream target and advances the stream's tracked offset.

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: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently.

C:

Create a suitable stream over the source and a controlled downstream task to process tracked changes. That is suitable for a DIFFERENT Snowflake situation: An ETL process needs to react to changed rows, but it rereads an entire source table every hour. It does not directly resolve the current requirement: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently.

D:

Inspect query profile compilation versus execution and limit excessive dynamic SQL statement variation where feasible. That is suitable for a DIFFERENT Snowflake situation: A performance report shows high compilation time but almost zero actual execution time for repeated short statements. It does not directly resolve the current requirement: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently.

Question 146

After the approved change, engineers revisit: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. Which result establishes the intended state?

  1. Alerting detects a lagging consumer early and a replay drill recovers from an approved source when needed.
  2. A committed consumer updates the downstream target and advances the stream's tracked offset.
  3. A representative source update reaches the materialized result within the agreed target lag and refresh status is visible.
  4. The chosen warehouse meets latency requirements at a measured economical credit cost.

Explanation

Correct Answer

B:

A committed consumer updates the downstream target and advances the stream's tracked offset. This validates the relevant action: Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection. The underlying Snowflake behavior is: Stream offsets advance through committed consuming DML rather than ordinary inspection queries.

Incorrect Answers

A:

Alerting detects a lagging consumer early and a replay drill recovers from an approved source when needed. This evidence tests a DIFFERENT situation: An ingest pipeline uses a stream and task but falls behind for days beyond the underlying change-tracking retention period. The correction required in this case is: Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection.

C:

A representative source update reaches the materialized result within the agreed target lag and refresh status is visible. This evidence tests a DIFFERENT situation: A data team maintains a SQL-based bronze-to-silver transformation with fixed freshness targets but writes complicated manual MERGE scheduling code. The correction required in this case is: Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection.

D:

The chosen warehouse meets latency requirements at a measured economical credit cost. This evidence tests a DIFFERENT situation: A data engineer expects a larger warehouse always to reduce a query's credit cost even if runtime barely changes. The correction required in this case is: Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection.

Question 147

A root-cause investigation considers: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. What is the most applicable explanation?

  1. Task dependencies express sequencing more reliably than coincident wall-clock schedules.
  2. Dynamic tables describe relational queries and are not a general procedural workflow engine.
  3. Stream offsets advance through committed consuming DML rather than ordinary inspection queries.
  4. An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them.

Explanation

Correct Answer

C:

Stream offsets advance through committed consuming DML rather than ordinary inspection queries. This explains the condition: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. The corrective response is: Consume the stream in an appropriate committed DML transaction rather than relying on read-only inspection.

Incorrect Answers

A:

Task dependencies express sequencing more reliably than coincident wall-clock schedules. That mechanism explains a DIFFERENT Snowflake problem: A task DAG should perform cleansing only after an ingest task succeeds, but the team schedules both independently at the same minute. Here the relevant mechanism instead is: Stream offsets advance through committed consuming DML rather than ordinary inspection queries.

B:

Dynamic tables describe relational queries and are not a general procedural workflow engine. That mechanism explains a DIFFERENT Snowflake problem: A task needs to call external APIs conditionally and loop through records, but developers choose a dynamic table as if it ran procedural code. Here the relevant mechanism instead is: Stream offsets advance through committed consuming DML rather than ordinary inspection queries.

D:

An ambiguous many-to-many effective-date join duplicates fact rows rather than refining them. That mechanism explains a DIFFERENT Snowflake problem: A transformation joins sales to a dimension table with two overlapping effective-date records and duplicates revenues. Here the relevant mechanism instead is: Stream offsets advance through committed consuming DML rather than ordinary inspection queries.

Question 148

During operational handoff for this problem: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. Which guardrail should be included?

  1. Monitor refresh lag and cost when replacing manual pipelines.
  2. Include root task state and graph status in deployment checks.
  3. Include profile-based pruning checks in important report code reviews.
  4. Test rollback and replay behavior for each stream consumer.

Explanation

Correct Answer

D:

Test rollback and replay behavior for each stream consumer. This reduces recurrence of: Stream offsets advance through committed consuming DML rather than ordinary inspection queries. The verification should demonstrate: A committed consumer updates the downstream target and advances the stream's tracked offset.

Incorrect Answers

A:

Monitor refresh lag and cost when replacing manual pipelines. That safeguard is aimed at ANOTHER risk: A data team maintains a SQL-based bronze-to-silver transformation with fixed freshness targets but writes complicated manual MERGE scheduling code. It is less targeted than the control for: Stream offsets advance through committed consuming DML rather than ordinary inspection queries.

B:

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: Stream offsets advance through committed consuming DML rather than ordinary inspection queries.

C:

Include profile-based pruning checks in important report code reviews. That safeguard is aimed at ANOTHER risk: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. It is less targeted than the control for: Stream offsets advance through committed consuming DML rather than ordinary inspection queries.

Question 149

A data-platform team must resolve: A data provider creates a direct share but the consumer cannot see a secure view because underlying reference privileges are incomplete. Which technical change most directly solves it?

  1. Keep shared objects read-only and use an approved local table copy if independent transformations are required.
  2. Configure the supported secure view sharing prerequisites and necessary database/object share grants.
  3. Model the shared-data consumer's own warehouse compute and the provider's ongoing storage responsibilities separately.
  4. Use compatibility checks, versioned interfaces and a change-notification process for listed data products.

Explanation

Correct Answer

B:

Configure the supported secure view sharing prerequisites and necessary database/object share grants. This directly addresses the described Snowflake condition: A data provider creates a direct share but the consumer cannot see a secure view because underlying reference privileges are incomplete. The mechanism is: Shared secure views must satisfy supported object and dependency rules, not only a view name grant. Verify success using: The consumer can query the shared secure view without direct access to unapproved underlying tables.

Incorrect Answers

A:

Keep shared objects read-only and use an approved local table copy if independent transformations are required. That is suitable for a DIFFERENT Snowflake situation: A consuming team tries to UPDATE a shared sales table and reports an authorization failure despite having read access. It does not directly resolve the current requirement: A data provider creates a direct share but the consumer cannot see a secure view because underlying reference privileges are incomplete.

C:

Model the shared-data consumer's own warehouse compute and the provider's ongoing storage responsibilities separately. That is suitable for a DIFFERENT Snowflake situation: A provider expects that consumer queries on shared data will be billed entirely to the provider's compute warehouse. It does not directly resolve the current requirement: A data provider creates a direct share but the consumer cannot see a secure view because underlying reference privileges are incomplete.

D:

Use compatibility checks, versioned interfaces and a change-notification process for listed data products. That is suitable for a DIFFERENT Snowflake situation: A data provider changes a shared table schema in a listed data product and breaks downstream customer queries. It does not directly resolve the current requirement: A data provider creates a direct share but the consumer cannot see a secure view because underlying reference privileges are incomplete.

Question 150

A Snowflake acceptance test follows this incident: A data provider creates a direct share but the consumer cannot see a secure view because underlying reference privileges are incomplete. What evidence most directly proves the correction?

  1. A consumer in the remote region obtains the governed listing through supported fulfillment, not a same-region-only direct share.
  2. A consumer role can query only the added approved object after the share grant is applied.
  3. The consumer can query the shared secure view without direct access to unapproved underlying tables.
  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 secure view without direct access to unapproved underlying tables. This validates the relevant action: Configure the supported secure view sharing prerequisites and necessary database/object share grants. The underlying Snowflake behavior is: Shared secure views must satisfy supported object and dependency rules, not only a view name grant.

Incorrect Answers

A:

A consumer in the remote region obtains the governed listing through supported fulfillment, not a same-region-only direct share. This evidence tests a DIFFERENT situation: Two Snowflake accounts are in different regions and a provider assumes a direct share can be added across the regions immediately. The correction required in this case is: Configure the supported secure view sharing prerequisites and necessary database/object share grants.

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: Configure the supported secure view sharing prerequisites and necessary database/object share grants.

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: Configure the supported secure view sharing prerequisites and necessary database/object share grants.