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 14

Question 130

After the approved change, engineers revisit: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. Which result establishes the intended state?

  1. The function reaches only its approved host, while an unrelated outbound request is denied.
  2. Session metadata shows the intended target account and query history records the application job.
  3. An authorized production test object produces a corresponding pipe load-history event.
  4. A dry-run or test load includes only source files for the approved business feed.

Explanation

Correct Answer

B:

Session metadata shows the intended target account and query history records the application job. This validates the relevant action: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context. The underlying Snowflake behavior is: Account identification and cloud region routing are connection configuration dependencies.

Incorrect Answers

A:

The function reaches only its approved host, while an unrelated outbound request is denied. This evidence tests a DIFFERENT situation: An external UDF sends public data to an API, but the security review discovers its request uses an unrestricted outbound network rule. The correction required in this case is: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context.

C:

An authorized production test object produces a corresponding pipe load-history event. This evidence tests a DIFFERENT situation: A cloud storage event notification invokes Snowpipe from a test bucket, but production bucket events point to a stale integration identifier. The correction required in this case is: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context.

D:

A dry-run or test load includes only source files for the approved business feed. This evidence tests a DIFFERENT situation: A staged directory contains many unrelated feeds and COPY loads data intended for another department. The correction required in this case is: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context.

Question 131

A root-cause investigation considers: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. What is the most applicable explanation?

  1. Event source configuration is independent of merely having a valid COPY statement inside the pipe.
  2. Client session role configuration can override or inherit defaults and affects object access.
  3. Account identification and cloud region routing are connection configuration dependencies.
  4. COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

Explanation

Correct Answer

C:

Account identification and cloud region routing are connection configuration dependencies. This explains the condition: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. The corrective response is: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context.

Incorrect Answers

A:

Event source configuration is independent of merely having a valid COPY statement inside the pipe. That mechanism explains a DIFFERENT Snowflake problem: A cloud storage event notification invokes Snowpipe from a test bucket, but production bucket events point to a stale integration identifier. Here the relevant mechanism instead is: Account identification and cloud region routing are connection configuration dependencies.

B:

Client session role configuration can override or inherit defaults and affects object access. That mechanism explains a DIFFERENT Snowflake problem: A partner uses an ODBC reporting connector with a role that changes silently after an administrator modifies user defaults. Here the relevant mechanism instead is: Account identification and cloud region routing are connection configuration dependencies.

D:

COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files. That mechanism explains a DIFFERENT Snowflake problem: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. Here the relevant mechanism instead is: Account identification and cloud region routing are connection configuration dependencies.

Question 132

During operational handoff for this problem: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. Which guardrail should be included?

  1. Include role attribution in connector acceptance tests and audits.
  2. Maintain integration inventory across test and production storage environments.
  3. Review FORCE and PURGE options during production code changes.
  4. Keep environment-specific account identifiers out of source-code assumptions.

Explanation

Correct Answer

D:

Keep environment-specific account identifiers out of source-code assumptions. This reduces recurrence of: Account identification and cloud region routing are connection configuration dependencies. The verification should demonstrate: Session metadata shows the intended target account and query history records the application job.

Incorrect Answers

A:

Include role attribution in connector acceptance tests and audits. That safeguard is aimed at ANOTHER risk: A partner uses an ODBC reporting connector with a role that changes silently after an administrator modifies user defaults. It is less targeted than the control for: Account identification and cloud region routing are connection configuration dependencies.

B:

Maintain integration inventory across test and production storage environments. That safeguard is aimed at ANOTHER risk: A cloud storage event notification invokes Snowpipe from a test bucket, but production bucket events point to a stale integration identifier. It is less targeted than the control for: Account identification and cloud region routing are connection configuration dependencies.

C:

Review FORCE and PURGE options during production code changes. That safeguard is aimed at ANOTHER risk: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. It is less targeted than the control for: Account identification and cloud region routing are connection configuration dependencies.

Question 133

A data-platform team must resolve: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. Which technical change most directly solves it?

  1. Inspect query profile compilation versus execution and limit excessive dynamic SQL statement variation where feasible.
  2. Correct join keys or preaggregate at the intended grain before increasing warehouse size.
  3. Compare Search Optimization Service suitability with clustering and ordinary pruning for this selective lookup pattern.
  4. Implement explicit NULL handling with CASE/COALESCE and business-approved fallback categories.

Explanation

Correct Answer

B:

Correct join keys or preaggregate at the intended grain before increasing warehouse size. This directly addresses the described Snowflake condition: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. The mechanism is: High join cardinality can multiply intermediate rows and dominate execution cost. Verify success using: The corrected query returns the expected business grain without explosive intermediate row counts.

Incorrect Answers

A:

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 critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join.

C:

Compare Search Optimization Service suitability with clustering and ordinary pruning for this selective lookup pattern. That is suitable for a DIFFERENT Snowflake situation: An analytics query searches a small customer ID set in a giant table with no selective access optimization. It does not directly resolve the current requirement: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join.

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: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join.

Question 134

A Snowflake acceptance test follows this incident: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. What evidence most directly proves the correction?

  1. A controlled larger-memory or optimized query run reduces remote spill and improves runtime.
  2. Peak concurrent query queue time reduces while per-query results remain stable.
  3. The corrected query returns the expected business grain without explosive intermediate row counts.
  4. Alerting detects a lagging consumer early and a replay drill recovers from an approved source when needed.

Explanation

Correct Answer

C:

The corrected query returns the expected business grain without explosive intermediate row counts. This validates the relevant action: Correct join keys or preaggregate at the intended grain before increasing warehouse size. The underlying Snowflake behavior is: High join cardinality can multiply intermediate rows and dominate execution cost.

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: Correct join keys or preaggregate at the intended grain before increasing warehouse size.

B:

Peak concurrent query queue time reduces while per-query results remain stable. This evidence tests a DIFFERENT situation: A warehouse runs a complex query quickly when alone but users see high queued overload during peak BI hours. The correction required in this case is: Correct join keys or preaggregate at the intended grain before increasing warehouse size.

D:

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: Correct join keys or preaggregate at the intended grain before increasing warehouse size.

Question 135

The data-platform team observes: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. Which architectural or processing fact matters most?

  1. Large intermediate state can exceed available memory, causing costly spill to storage.
  2. Repeated source scans can waste compute even if individual SQL statements are valid.
  3. Persisted result reuse is subject to data freshness and other cache eligibility conditions.
  4. High join cardinality can multiply intermediate rows and dominate execution cost.

Explanation

Correct Answer

D:

High join cardinality can multiply intermediate rows and dominate execution cost. This explains the condition: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. The corrective response is: Correct join keys or preaggregate at the intended grain before increasing warehouse size.

Incorrect Answers

A:

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: High join cardinality can multiply intermediate rows and dominate execution cost.

B:

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: High join cardinality can multiply intermediate rows and dominate execution cost.

C:

Persisted result reuse is subject to data freshness and other cache eligibility conditions. That mechanism explains a DIFFERENT Snowflake problem: A dashboard runs the same query after base-table data changes and expects the previous persisted result to remain valid. Here the relevant mechanism instead is: High join cardinality can multiply intermediate rows and dominate execution cost.

Question 136

For a public-sector reporting unit, this issue must not recur: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. Which review control fits best?

  1. Review source uniqueness assumptions and test counts for joins on business keys.
  2. Measure maintenance credits and candidate query selectivity before enabling optimization.
  3. Graph queue duration and execution duration separately over business-hour peaks.
  4. Include NULL fixtures in transformation and business-rule regression tests.

Explanation

Correct Answer

A:

Review source uniqueness assumptions and test counts for joins on business keys. This reduces recurrence of: High join cardinality can multiply intermediate rows and dominate execution cost. The verification should demonstrate: The corrected query returns the expected business grain without explosive intermediate row counts.

Incorrect Answers

B:

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: High join cardinality can multiply intermediate rows and dominate execution cost.

C:

Graph queue duration and execution duration separately over business-hour peaks. That safeguard is aimed at ANOTHER risk: A warehouse runs a complex query quickly when alone but users see high queued overload during peak BI hours. It is less targeted than the control for: High join cardinality can multiply intermediate rows and dominate execution cost.

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: High join cardinality can multiply intermediate rows and dominate execution cost.

Question 137

In a governed Snowflake environment, the reported condition is: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. What should be implemented first?

  1. Use supported MERGE with stable business keys and explicit update/insert branches for true upsert behavior.
  2. Define an explicit ordered window frame covering only the intended preceding periods.
  3. Use LATERAL FLATTEN over the intended array path and select child elements with parent keys.
  4. Correct join keys or preaggregate at the intended grain before increasing warehouse size.

Explanation

Correct Answer

C:

Use LATERAL FLATTEN over the intended array path and select child elements with parent keys. This directly addresses the described Snowflake condition: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. The mechanism is: FLATTEN expands nested semi-structured arrays into relational rows. Verify success using: The output includes one row per intended order line while preserving source order identifiers.

Incorrect Answers

A:

Use supported MERGE with stable business keys and explicit update/insert branches for true upsert behavior. That is suitable for a DIFFERENT Snowflake situation: A developer wants to update target customer records from daily source changes but uses INSERT for every delivery. It does not directly resolve the current requirement: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item.

B:

Define an explicit ordered window frame covering only the intended preceding periods. That is suitable for a DIFFERENT Snowflake situation: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. It does not directly resolve the current requirement: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item.

D:

Correct join keys or preaggregate at the intended grain before increasing warehouse size. That is suitable for a DIFFERENT Snowflake situation: A critical join query is slow, and Query Profile reveals enormous intermediate rows caused by a many-to-many join. It does not directly resolve the current requirement: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item.

Question 138

A test plan evaluates: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. Which evidence should be required before release?

  1. A repeated source batch updates existing targets instead of inserting duplicate customer keys.
  2. A fixture's early months are unaffected by events occurring after their timestamp.
  3. The rewritten query returns the same rows and scans fewer micro-partitions.
  4. The output includes one row per intended order line while preserving source order identifiers.

Explanation

Correct Answer

D:

The output includes one row per intended order line while preserving source order identifiers. This validates the relevant action: Use LATERAL FLATTEN over the intended array path and select child elements with parent keys. The underlying Snowflake behavior is: FLATTEN expands nested semi-structured arrays into relational rows.

Incorrect Answers

A:

A repeated source batch updates existing targets instead of inserting duplicate customer keys. This evidence tests a DIFFERENT situation: A developer wants to update target customer records from daily source changes but uses INSERT for every delivery. The correction required in this case is: Use LATERAL FLATTEN over the intended array path and select child elements with parent keys.

B:

A fixture's early months are unaffected by events occurring after their timestamp. This evidence tests a DIFFERENT situation: An analyst calculates monthly moving averages but an unbounded window includes later months and changes historical metrics. The correction required in this case is: Use LATERAL FLATTEN over the intended array path and select child elements with parent keys.

C:

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: Use LATERAL FLATTEN over the intended array path and select child elements with parent keys.

Question 139

A Snowflake incident report notes: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. What underlying mechanism explains the behavior?

  1. FLATTEN expands nested semi-structured arrays into relational rows.
  2. SQL NULL propagates differently from ordinary string comparisons and equality conditions.
  3. MERGE applies conditional matched and not-matched actions, while unconditional INSERT does not deduplicate.
  4. Automatic clustering introduces maintenance work that might outweigh gains on small tables.

Explanation

Correct Answer

A:

FLATTEN expands nested semi-structured arrays into relational rows. This explains the condition: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. The corrective response is: Use LATERAL FLATTEN over the intended array path and select child elements with parent keys.

Incorrect Answers

B:

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

C:

MERGE applies conditional matched and not-matched actions, while unconditional INSERT does not deduplicate. That mechanism explains a DIFFERENT Snowflake problem: A developer wants to update target customer records from daily source changes but uses INSERT for every delivery. Here the relevant mechanism instead is: FLATTEN expands nested semi-structured arrays into relational rows.

D:

Automatic clustering introduces maintenance work that might outweigh gains on small tables. That mechanism explains a DIFFERENT Snowflake problem: An engineer adds a clustering key to every small table although Query Profile shows already efficient pruning. Here the relevant mechanism instead is: FLATTEN expands nested semi-structured arrays into relational rows.

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.