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 30

Question 290

After the approved change, engineers revisit: A service account imports data via a storage integration but its cloud IAM policy allows access to an entire organization bucket. Which result establishes the intended state?

  1. The pipeline loads representative events with measured latency and manageable operational overhead.
  2. The approved source loads, while an unrelated prefix read is denied in the controlled test.
  3. The connector's role context and query results remain correct after default-role changes.
  4. Smaller supported files reach the table with predictable latency and tracked completeness.

Explanation

Correct Answer

B:

The approved source loads, while an unrelated prefix read is denied in the controlled test. This validates the relevant action: Reduce allowed cloud storage locations and integration permissions to the approved prefixes. The underlying Snowflake behavior is: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.

Incorrect Answers

A:

The pipeline loads representative events with measured latency and manageable operational overhead. This evidence tests a DIFFERENT situation: A data app needs to ingest events from Kafka but engineers build one file per message and a new warehouse COPY for each row. The correction required in this case is: Reduce allowed cloud storage locations and integration permissions to the approved prefixes.

C:

The connector's role context and query results remain correct after default-role changes. This evidence tests a DIFFERENT situation: A partner uses an ODBC reporting connector with a role that changes silently after an administrator modifies user defaults. The correction required in this case is: Reduce allowed cloud storage locations and integration permissions to the approved prefixes.

D:

Smaller supported files reach the table with predictable latency and tracked completeness. This evidence tests a DIFFERENT situation: A Snowpipe ingestion shows increasing time-to-availability after upstream sends huge compressed archives once daily. The correction required in this case is: Reduce allowed cloud storage locations and integration permissions to the approved prefixes.

Question 291

A root-cause investigation considers: A service account imports data via a storage integration but its cloud IAM policy allows access to an entire organization bucket. What is the most applicable explanation?

  1. Account identification and cloud region routing are connection configuration dependencies.
  2. Connector-based streaming ingestion can be a better fit than per-event staged-file bulk COPY.
  3. Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.
  4. Unload file format and header settings determine how external consumers parse records.

Explanation

Correct Answer

C:

Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate. This explains the condition: A service account imports data via a storage integration but its cloud IAM policy allows access to an entire organization bucket. The corrective response is: Reduce allowed cloud storage locations and integration permissions to the approved prefixes.

Incorrect Answers

A:

Account identification and cloud region routing are connection configuration dependencies. That mechanism explains a DIFFERENT Snowflake problem: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. Here the relevant mechanism instead is: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.

B:

Connector-based streaming ingestion can be a better fit than per-event staged-file bulk COPY. That mechanism explains a DIFFERENT Snowflake problem: A data app needs to ingest events from Kafka but engineers build one file per message and a new warehouse COPY for each row. Here the relevant mechanism instead is: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.

D:

Unload file format and header settings determine how external consumers parse records. That mechanism explains a DIFFERENT Snowflake problem: A CSV unload intended for downstream SQL ingestion contains headers in some files and not others. Here the relevant mechanism instead is: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.

Question 292

During operational handoff for this problem: A service account imports data via a storage integration but its cloud IAM policy allows access to an entire organization bucket. Which guardrail should be included?

  1. Review endpoint allowlists and secret rotation for external function integrations.
  2. Benchmark actual event rate and failure recovery when selecting ingestion architecture.
  3. Review source folder conventions and patterns for overlapping feeds.
  4. Review integration and cloud policies when new bucket prefixes are added.

Explanation

Correct Answer

D:

Review integration and cloud policies when new bucket prefixes are added. This reduces recurrence of: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate. The verification should demonstrate: The approved source loads, while an unrelated prefix read is denied in the controlled test.

Incorrect Answers

A:

Review endpoint allowlists and secret rotation for external function integrations. That safeguard is aimed at ANOTHER risk: An external UDF sends public data to an API, but the security review discovers its request uses an unrestricted outbound network rule. It is less targeted than the control for: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.

B:

Benchmark actual event rate and failure recovery when selecting ingestion architecture. That safeguard is aimed at ANOTHER risk: A data app needs to ingest events from Kafka but engineers build one file per message and a new warehouse COPY for each row. It is less targeted than the control for: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.

C:

Review source folder conventions and patterns for overlapping feeds. That safeguard is aimed at ANOTHER risk: A staged directory contains many unrelated feeds and COPY loads data intended for another department. It is less targeted than the control for: Storage integration trust must be scoped to intended cloud resources rather than a whole storage estate.

Question 293

A data-platform team must resolve: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. Which technical change most directly solves it?

  1. Evaluate a consolidated transformation or approved precomputed result for repeated expensive work.
  2. Rewrite predicates to use supported sargable timestamp ranges aligned with stored values.
  3. Compare Query Profile, partition counts and data distribution before attributing regression to compute.
  4. Evaluate a supported materialized view matching a frequently repeated single-table aggregation.

Explanation

Correct Answer

B:

Rewrite predicates to use supported sargable timestamp ranges aligned with stored values. This directly addresses the described Snowflake condition: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. The mechanism is: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges. Verify success using: The rewritten query returns the same rows and scans fewer micro-partitions.

Incorrect Answers

A:

Evaluate a consolidated transformation or approved precomputed result for repeated expensive work. That is suitable for a DIFFERENT Snowflake situation: A nightly transformation consumes excessive time because the same large staging table is scanned multiple times in separate jobs. It does not directly resolve the current requirement: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range.

C:

Compare Query Profile, partition counts and data distribution before attributing regression to compute. That is suitable for a DIFFERENT Snowflake situation: A query suddenly slows after a large table changed, yet the team looks only at warehouse size changes. It does not directly resolve the current requirement: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range.

D:

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 report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range.

Question 294

A Snowflake acceptance test follows this incident: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. What evidence most directly proves the correction?

  1. A controlled larger-memory or optimized query run reduces remote spill and improves runtime.
  2. The chosen warehouse meets latency requirements at a measured economical credit cost.
  3. The rewritten query returns the same rows and scans fewer micro-partitions.
  4. A committed consumer updates the downstream target and advances the stream's tracked offset.

Explanation

Correct Answer

C:

The rewritten query returns the same rows and scans fewer micro-partitions. This validates the relevant action: Rewrite predicates to use supported sargable timestamp ranges aligned with stored values. The underlying Snowflake behavior is: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

Incorrect Answers

A:

A controlled larger-memory or optimized query run reduces remote spill and improves runtime. This evidence tests a DIFFERENT situation: A large aggregation is spilling heavily to remote storage, but its warehouse has no concurrency queue. The correction required in this case is: Rewrite predicates to use supported sargable timestamp ranges aligned with stored values.

B:

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: Rewrite predicates to use supported sargable timestamp ranges aligned with stored values.

D:

A committed consumer updates the downstream target and advances the stream's tracked offset. This evidence tests a DIFFERENT situation: A stream shows pending changes, but the engineer assumes a SELECT against the stream will advance the offset permanently. The correction required in this case is: Rewrite predicates to use supported sargable timestamp ranges aligned with stored values.

Question 295

The data-platform team observes: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. Which architectural or processing fact matters most?

  1. Repeated source scans can waste compute even if individual SQL statements are valid.
  2. Large intermediate state can exceed available memory, causing costly spill to storage.
  3. Stream offsets advance through committed consuming DML rather than ordinary inspection queries.
  4. Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

Explanation

Correct Answer

D:

Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges. This explains the condition: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. The corrective response is: Rewrite predicates to use supported sargable timestamp ranges aligned with stored values.

Incorrect Answers

A:

Repeated source scans can waste compute even if individual SQL statements are valid. That mechanism explains a DIFFERENT Snowflake problem: A nightly transformation consumes excessive time because the same large staging table is scanned multiple times in separate jobs. Here the relevant mechanism instead is: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

B:

Large intermediate state can exceed available memory, causing costly spill to storage. That mechanism explains a DIFFERENT Snowflake problem: A large aggregation is spilling heavily to remote storage, but its warehouse has no concurrency queue. Here the relevant mechanism instead is: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

C:

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: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

Question 296

For a regulated healthcare organization, this issue must not recur: A report SELECT filters a timestamp column using a function that prevents efficient pruning of the underlying date range. Which review control fits best?

  1. Include profile-based pruning checks in important report code reviews.
  2. Require performance and cost evidence rather than raw elapsed time alone.
  3. Track partitions scanned versus total across representative filter queries.
  4. Set freshness alerts and recovery playbooks for every critical stream.

Explanation

Correct Answer

A:

Include profile-based pruning checks in important report code reviews. This reduces recurrence of: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges. The verification should demonstrate: The rewritten query returns the same rows and scans fewer micro-partitions.

Incorrect Answers

B:

Require performance and cost evidence rather than raw elapsed time alone. That safeguard is aimed at ANOTHER risk: A data engineer expects a larger warehouse always to reduce a query's credit cost even if runtime barely changes. It is less targeted than the control for: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

C:

Track partitions scanned versus total across representative filter queries. That safeguard is aimed at ANOTHER risk: A filtered sales query scans nearly every micro-partition despite selecting one narrow order-date interval. It is less targeted than the control for: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

D:

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: Functions wrapping filter columns may weaken effective partition pruning compared with direct ranges.

Question 297

In a governed Snowflake environment, the reported condition is: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. What should be implemented first?

  1. Use LATERAL FLATTEN over the intended array path and select child elements with parent keys.
  2. Replace implicit cross joins with explicit intended JOIN conditions and validate expected relationship cardinality.
  3. Define an explicit ordered window frame covering only the intended preceding periods.
  4. Measure view refresh cost and query utilization, removing unproductive maintained results.

Explanation

Correct Answer

C:

Define an explicit ordered window frame covering only the intended preceding periods. This directly addresses the described Snowflake condition: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. The mechanism is: Window frames set which rows participate in each rolling calculation. Verify success using: A fixture's early months are unaffected by events occurring after their timestamp.

Incorrect Answers

A:

Use LATERAL FLATTEN over the intended array path and select child elements with parent keys. That is suitable for a DIFFERENT Snowflake situation: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. It does not directly resolve the current requirement: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics.

B:

Replace implicit cross joins with explicit intended JOIN conditions and validate expected relationship cardinality. That is suitable for a DIFFERENT Snowflake situation: A query uses a comma-separated FROM list and a missing join predicate multiplies rows, inflating sales totals. It does not directly resolve the current requirement: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics.

D:

Measure view refresh cost and query utilization, removing unproductive maintained results. That is suitable for a DIFFERENT Snowflake situation: An organization enables multiple materialized views for rarely used reports and sees maintenance charges rising above query savings. It does not directly resolve the current requirement: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics.

Question 298

A test plan evaluates: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. Which evidence should be required before release?

  1. A new event category follows the documented behavior rather than silently corrupting existing columns.
  2. The joined result counts each sales event once and resolves the intended dimension version.
  3. The dashboard reflects committed updates rather than relying on stale cached output.
  4. A fixture's early months are unaffected by events occurring after their timestamp.

Explanation

Correct Answer

D:

A fixture's early months are unaffected by events occurring after their timestamp. This validates the relevant action: Define an explicit ordered window frame covering only the intended preceding periods. The underlying Snowflake behavior is: Window frames set which rows participate in each rolling calculation.

Incorrect Answers

A:

A new event category follows the documented behavior rather than silently corrupting existing columns. This evidence tests a DIFFERENT situation: An analyst pivots event records to monthly metrics but assumes unexpected new event categories appear automatically in a fixed static pivot. The correction required in this case is: Define an explicit ordered window frame covering only the intended preceding periods.

B:

The joined result counts each sales event once and resolves the intended dimension version. This evidence tests a DIFFERENT situation: A transformation joins sales to a dimension table with two overlapping effective-date records and duplicates revenues. The correction required in this case is: Define an explicit ordered window frame covering only the intended preceding periods.

C:

The dashboard reflects committed updates rather than relying on stale cached output. This evidence tests a DIFFERENT situation: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. The correction required in this case is: Define an explicit ordered window frame covering only the intended preceding periods.

Question 299

A Snowflake incident report notes: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. What underlying mechanism explains the behavior?

  1. Window frames set which rows participate in each rolling calculation.
  2. Semi-structured extraction produces typed VARIANT expressions that require deliberate conversion for arithmetic.
  3. SQL NULL propagates differently from ordinary string comparisons and equality conditions.
  4. Materialized view definition constraints differ from general declarative dynamic tables and procedural tasks.

Explanation

Correct Answer

A:

Window frames set which rows participate in each rolling calculation. This explains the condition: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. The corrective response is: Define an explicit ordered window frame covering only the intended preceding periods.

Incorrect Answers

B:

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: Window frames set which rows participate in each rolling calculation.

C:

SQL NULL propagates differently from ordinary string comparisons and equality conditions. That mechanism explains a DIFFERENT Snowflake problem: A customer segmentation query uses CASE in multiple branches without handling NULL values and classifies unknown regions incorrectly. Here the relevant mechanism instead is: Window frames set which rows participate in each rolling calculation.

D:

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: Window frames set which rows participate in each rolling calculation.

Question 300

A platform governance committee considers: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. What preventive check should be standardized?

  1. Use query linting and controlled row-count assertions for production joins.
  2. Use boundary and late-arriving data tests for rolling aggregate SQL.
  3. Test idempotent replay and multiple-source-match conflicts before release.
  4. Reevaluate predicate selectivity and credit impact after query pattern changes.

Explanation

Correct Answer

B:

Use boundary and late-arriving data tests for rolling aggregate SQL. This reduces recurrence of: Window frames set which rows participate in each rolling calculation. The verification should demonstrate: A fixture's early months are unaffected by events occurring after their timestamp.

Incorrect Answers

A:

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: Window frames set which rows participate in each rolling calculation.

C:

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: Window frames set which rows participate in each rolling calculation.

D:

Reevaluate predicate selectivity and credit impact after query pattern changes. That safeguard is aimed at ANOTHER risk: A selective point lookup needs acceleration but an engineer wants to recluster an entire table without measuring existing pruning. It is less targeted than the control for: Window frames set which rows participate in each rolling calculation.