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 10

Question 90

A test plan evaluates: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. Which evidence should be required before release?

  1. The selected retention setting is accepted without unsupported edition assumptions.
  2. The chosen permanent table has documented Fail-safe coverage while transient test tables do not.
  3. The reporting warehouse completes the sample dashboard while cloud services metadata operations remain unaffected.
  4. Time-filtered SQL queries prune eligible partitions without user-maintained folder partition definitions.

Explanation

Correct Answer

D:

Time-filtered SQL queries prune eligible partitions without user-maintained folder partition definitions. This validates the relevant action: Rely on Snowflake-managed micro-partitions and design predicates or clustering strategy appropriately. The underlying Snowflake behavior is: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

Incorrect Answers

A:

The selected retention setting is accepted without unsupported edition assumptions. This evidence tests a DIFFERENT situation: A team increases Time Travel retention to 90 days on a Standard Edition account without checking edition limits. The correction required in this case is: Rely on Snowflake-managed micro-partitions and design predicates or clustering strategy appropriately.

B:

The chosen permanent table has documented Fail-safe coverage while transient test tables do not. This evidence tests a DIFFERENT situation: A staging team creates transient tables for reproducible data but expects the seven-day Fail-safe recovery of permanent tables. The correction required in this case is: Rely on Snowflake-managed micro-partitions and design predicates or clustering strategy appropriately.

C:

The reporting warehouse completes the sample dashboard while cloud services metadata operations remain unaffected. This evidence tests a DIFFERENT situation: A reporting dashboard slows during warehouse saturation, and an analyst proposes resizing cloud services instead of compute. The correction required in this case is: Rely on Snowflake-managed micro-partitions and design predicates or clustering strategy appropriately.

Question 91

A Snowflake incident report notes: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. What underlying mechanism explains the behavior?

  1. Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.
  2. Snowflake historical queries can use the current table or view schema even when querying earlier data.
  3. Micro-partition metadata enables pruning when values allow partitions to be excluded from the scan.
  4. Some metadata and orchestration work is handled by cloud services, distinct from warehouse data processing.

Explanation

Correct Answer

A:

Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions. This explains the condition: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. The corrective response is: Rely on Snowflake-managed micro-partitions and design predicates or clustering strategy appropriately.

Incorrect Answers

B:

Snowflake historical queries can use the current table or view schema even when querying earlier data. That mechanism explains a DIFFERENT Snowflake problem: A finance audit expects a Time Travel historical query to reproduce every former schema definition after a column rename. Here the relevant mechanism instead is: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

C:

Micro-partition metadata enables pruning when values allow partitions to be excluded from the scan. That mechanism explains a DIFFERENT Snowflake problem: A table scan touches most rows even though a predicate selects one month, and clustering metadata shows overlapping date ranges. Here the relevant mechanism instead is: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

D:

Some metadata and orchestration work is handled by cloud services, distinct from warehouse data processing. That mechanism explains a DIFFERENT Snowflake problem: An application requires a low-latency metadata operation, but operations assumes every SQL statement must start a warehouse. Here the relevant mechanism instead is: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

Question 92

A platform governance committee considers: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. What preventive check should be standardized?

  1. Record scope and lifetime requirements in object design reviews.
  2. Review actual pruning evidence instead of imposing inherited file-partition assumptions.
  3. Capture incident timestamps and retention deadlines when recovering data changes.
  4. Review total billable runtime and query delay together when tuning suspend settings.

Explanation

Correct Answer

B:

Review actual pruning evidence instead of imposing inherited file-partition assumptions. This reduces recurrence of: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions. The verification should demonstrate: Time-filtered SQL queries prune eligible partitions without user-maintained folder partition definitions.

Incorrect Answers

A:

Record scope and lifetime requirements in object design reviews. That safeguard is aimed at ANOTHER risk: A data engineer expects a temporary table created in one session to remain visible after the session ends. It is less targeted than the control for: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

C:

Capture incident timestamps and retention deadlines when recovering data changes. That safeguard is aimed at ANOTHER risk: A team wants a historical snapshot of a supported table at the state before a mistaken DELETE within retention. It is less targeted than the control for: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

D:

Review total billable runtime and query delay together when tuning suspend settings. That safeguard is aimed at ANOTHER risk: A recurring report finishes in two minutes but its warehouse auto-suspends after an extremely short idle timeout between closely spaced queries. It is less targeted than the control for: Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

Question 93

An engineering team investigates the following Snowflake issue: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. Which configuration or processing decision is most appropriate?

  1. Store raw semi-structured payloads in VARIANT where appropriate and derive typed fields for analytic use.
  2. Choose a UDF for expression-style reusable computation and a procedure where supported procedural operations are required.
  3. Design regular Snowflake tables using platform-managed columnar storage instead of direct file-level management.
  4. Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors.

Explanation

Correct Answer

D:

Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors. This directly addresses the described Snowflake condition: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. The mechanism is: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules. Verify success using: A test query resolves the intended object using the documented naming convention.

Incorrect Answers

A:

Store raw semi-structured payloads in VARIANT where appropriate and derive typed fields for analytic use. That is suitable for a DIFFERENT Snowflake situation: A developer wants to store variable nested JSON documents but designs dozens of nullable columns for unknown future properties. It does not directly resolve the current requirement: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions.

B:

Choose a UDF for expression-style reusable computation and a procedure where supported procedural operations are required. That is suitable for a DIFFERENT Snowflake situation: A SQL reporting team mixes SQL UDFs and stored procedures as though both have identical invocation and side effects. It does not directly resolve the current requirement: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions.

C:

Design regular Snowflake tables using platform-managed columnar storage instead of direct file-level management. That is suitable for a DIFFERENT Snowflake situation: A customer migrates an on-prem database and wants to manage underlying Snowflake storage files directly for normal tables. It does not directly resolve the current requirement: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions.

Question 94

For an e-commerce operations team, the original problem was: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. What observation confirms success?

  1. A test query resolves the intended object using the documented naming convention.
  2. The table refreshes toward the declared lag rather than requiring the team to rerun a one-time insert.
  3. A nested key extraction returns a typed expected value from a valid JSON fixture.
  4. Queuing decreases in a realistic concurrent run, with cluster count rising within the configured range.

Explanation

Correct Answer

A:

A test query resolves the intended object using the documented naming convention. This validates the relevant action: Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors. The underlying Snowflake behavior is: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

Incorrect Answers

B:

The table refreshes toward the declared lag rather than requiring the team to rerun a one-time insert. This evidence tests a DIFFERENT situation: An engineer creates a dynamic table with a SELECT query and assumes it behaves like a normal manually written snapshot table. The correction required in this case is: Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors.

C:

A nested key extraction returns a typed expected value from a valid JSON fixture. This evidence tests a DIFFERENT situation: A migration tool defines a table column as VARCHAR then assumes all JSON path operators will work on it without conversion. The correction required in this case is: Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors.

D:

Queuing decreases in a realistic concurrent run, with cluster count rising within the configured range. This evidence tests a DIFFERENT situation: A customer reports long query queues when 40 dashboard users connect, yet each individual query runs quickly alone. The correction required in this case is: Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors.

Question 95

In a case affecting an e-commerce operations team, this issue appears: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. What explains it?

  1. VARIANT can store and query semi-structured content while schema-on-read extracts nested attributes.
  2. Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.
  3. Views can provide a controlled logical interface over underlying table data.
  4. Vector similarity is numerical and model-dependent rather than lexicographic string comparison.

Explanation

Correct Answer

B:

Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules. This explains the condition: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. The corrective response is: Use consistent normal identifiers or quote case-sensitive identifiers deliberately in SQL and connectors.

Incorrect Answers

A:

VARIANT can store and query semi-structured content while schema-on-read extracts nested attributes. That mechanism explains a DIFFERENT Snowflake problem: A developer wants to store variable nested JSON documents but designs dozens of nullable columns for unknown future properties. Here the relevant mechanism instead is: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

C:

Views can provide a controlled logical interface over underlying table data. That mechanism explains a DIFFERENT Snowflake problem: An analyst uses SELECT * from a view to expose sensitive fields that should remain hidden from general users. Here the relevant mechanism instead is: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

D:

Vector similarity is numerical and model-dependent rather than lexicographic string comparison. That mechanism explains a DIFFERENT Snowflake problem: An application stores vector embeddings but a developer expects standard string comparison to rank semantic similarity automatically. Here the relevant mechanism instead is: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

Question 96

After remediating the Snowflake issue, the team reviews: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. Which recurring control is most targeted?

  1. Establish typed projection and data-quality rules for important JSON attributes.
  2. Audit object grants at database, schema and object levels.
  3. Adopt consistent identifier casing and quoting conventions in migration standards.
  4. Review total billable runtime and query delay together when tuning suspend settings.

Explanation

Correct Answer

C:

Adopt consistent identifier casing and quoting conventions in migration standards. This reduces recurrence of: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules. The verification should demonstrate: A test query resolves the intended object using the documented naming convention.

Incorrect Answers

A:

Establish typed projection and data-quality rules for important JSON attributes. That safeguard is aimed at ANOTHER risk: A developer wants to store variable nested JSON documents but designs dozens of nullable columns for unknown future properties. It is less targeted than the control for: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

B:

Audit object grants at database, schema and object levels. That safeguard is aimed at ANOTHER risk: A report author creates a database object but a new role cannot see the schema despite permission on one table. It is less targeted than the control for: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

D:

Review total billable runtime and query delay together when tuning suspend settings. That safeguard is aimed at ANOTHER risk: A recurring report finishes in two minutes but its warehouse auto-suspends after an extremely short idle timeout between closely spaced queries. It is less targeted than the control for: Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.

Question 97

At a retail analytics group, a Snowflake implementation review finds: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. Which action best addresses this requirement?

  1. Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata.
  2. Apply Snowflake governance policies to the source datasets and verify the model-access role's permitted rows and columns.
  3. Use supported Snowpark ML or in-account transformations appropriate for the workload and governance policy.
  4. Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing.

Explanation

Correct Answer

A:

Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata. This directly addresses the described Snowflake condition: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. The mechanism is: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering. Verify success using: A test natural-language query retrieves relevant approved passages rather than just lexical file-name matches.

Incorrect Answers

B:

Apply Snowflake governance policies to the source datasets and verify the model-access role's permitted rows and columns. That is suitable for a DIFFERENT Snowflake situation: A developer combines customer and product records for an LLM app without considering masking policy and row restrictions. It does not directly resolve the current requirement: An AI team expects an enterprise search feature to be built by sorting all documents by their file names.

C:

Use supported Snowpark ML or in-account transformations appropriate for the workload and governance policy. That is suitable for a DIFFERENT Snowflake situation: A retailer builds an ML feature pipeline by copying full source datasets to laptops every day. It does not directly resolve the current requirement: An AI team expects an enterprise search feature to be built by sorting all documents by their file names.

D:

Separate warehouse compute consumption from storage billing when estimating cost impacts of resizing. That is suitable for a DIFFERENT Snowflake situation: A business unit expects that scaling one warehouse doubles the storage charge for all shared tables. It does not directly resolve the current requirement: An AI team expects an enterprise search feature to be built by sorting all documents by their file names.

Question 98

After the approved change, engineers revisit: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. Which result establishes the intended state?

  1. A new model version cannot bypass the documented validation and approval gate.
  2. A test natural-language query retrieves relevant approved passages rather than just lexical file-name matches.
  3. A least-privilege test session sees only authorized records while the application still performs its expected task.
  4. Time-filtered SQL queries prune eligible partitions without user-maintained folder partition definitions.

Explanation

Correct Answer

B:

A test natural-language query retrieves relevant approved passages rather than just lexical file-name matches. This validates the relevant action: Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata. The underlying Snowflake behavior is: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.

Incorrect Answers

A:

A new model version cannot bypass the documented validation and approval gate. This evidence tests a DIFFERENT situation: A team wants to trigger governance checks whenever a Snowflake model registry artifact changes but relies on manual emails. The correction required in this case is: Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata.

C:

A least-privilege test session sees only authorized records while the application still performs its expected task. This evidence tests a DIFFERENT situation: A developer combines customer and product records for an LLM app without considering masking policy and row restrictions. The correction required in this case is: Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata.

D:

Time-filtered SQL queries prune eligible partitions without user-maintained folder partition definitions. This evidence tests a DIFFERENT situation: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. The correction required in this case is: Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata.

Question 99

A root-cause investigation considers: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. What is the most applicable explanation?

  1. Managed AI feature catalogs and regional availability can differ by service and cloud region.
  2. AI function usage can create distinct consumption costs that require their own monitoring.
  3. Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.
  4. Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions.

Explanation

Correct Answer

C:

Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering. This explains the condition: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. The corrective response is: Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata.

Incorrect Answers

A:

Managed AI feature catalogs and regional availability can differ by service and cloud region. That mechanism explains a DIFFERENT Snowflake problem: A team treats Snowflake's managed AI inference as having exactly the same regional availability for every model. Here the relevant mechanism instead is: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.

B:

AI function usage can create distinct consumption costs that require their own monitoring. That mechanism explains a DIFFERENT Snowflake problem: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. Here the relevant mechanism instead is: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.

D:

Standard Snowflake tables automatically organize data into micro-partitions rather than requiring manual file partitions. That mechanism explains a DIFFERENT Snowflake problem: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. Here the relevant mechanism instead is: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.

Question 100

During operational handoff for this problem: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. Which guardrail should be included?

  1. Classify data and review function availability and charges before rollout.
  2. Test generated SQL and model semantics against finance-approved calculations.
  3. Document retention windows and restoration expectations ahead of destructive changes.
  4. Evaluate retrieval accuracy and authorization on representative document sets.

Explanation

Correct Answer

D:

Evaluate retrieval accuracy and authorization on representative document sets. This reduces recurrence of: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering. The verification should demonstrate: A test natural-language query retrieves relevant approved passages rather than just lexical file-name matches.

Incorrect Answers

A:

Classify data and review function availability and charges before rollout. That safeguard is aimed at ANOTHER risk: A department wants sentiment analysis in SQL but proposes shipping every customer comment to an ungoverned third-party endpoint. It is less targeted than the control for: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.

B:

Test generated SQL and model semantics against finance-approved calculations. That safeguard is aimed at ANOTHER risk: A business team asks an LLM to answer revenue questions but the model frequently invents column names and joins. It is less targeted than the control for: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.

C:

Document retention windows and restoration expectations ahead of destructive changes. That safeguard is aimed at ANOTHER risk: An analyst expects to run SELECT AT a historical timestamp after Time Travel retention has expired into Fail-safe. It is less targeted than the control for: Semantic retrieval uses embeddings/indexed content, not ordinary alphabetical file ordering.