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 66

Question 650

A test plan evaluates: An engineer creates a dynamic table with a SELECT query and assumes it behaves like a normal manually written snapshot table. Which evidence should be required before release?

  1. A sample metadata refresh or write follows the chosen catalog ownership and supported permissions.
  2. Representative varied JSON payloads load without adding a column for each optional key.
  3. A test natural-language query retrieves relevant approved passages rather than just lexical file-name matches.
  4. The table refreshes toward the declared lag rather than requiring the team to rerun a one-time insert.

Explanation

Correct Answer

D:

The table refreshes toward the declared lag rather than requiring the team to rerun a one-time insert. This validates the relevant action: Choose a dynamic table only when a target-lag refresh model suits the pipeline requirement. The underlying Snowflake behavior is: Dynamic tables maintain query-defined results through Snowflake refresh management.

Incorrect Answers

A:

A sample metadata refresh or write follows the chosen catalog ownership and supported permissions. This evidence tests a DIFFERENT situation: An application developer assumes an external Iceberg catalog table is administered identically to a native Snowflake-managed table. The correction required in this case is: Choose a dynamic table only when a target-lag refresh model suits the pipeline requirement.

B:

Representative varied JSON payloads load without adding a column for each optional key. This evidence tests a DIFFERENT situation: A developer wants to store variable nested JSON documents but designs dozens of nullable columns for unknown future properties. The correction required in this case is: Choose a dynamic table only when a target-lag refresh model suits the pipeline requirement.

C:

A test natural-language query retrieves relevant approved passages rather than just lexical file-name matches. This evidence tests a DIFFERENT situation: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. The correction required in this case is: Choose a dynamic table only when a target-lag refresh model suits the pipeline requirement.

Question 651

A Snowflake incident report notes: An engineer creates a dynamic table with a SELECT query and assumes it behaves like a normal manually written snapshot table. What underlying mechanism explains the behavior?

  1. Dynamic tables maintain query-defined results through Snowflake refresh management.
  2. Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules.
  3. Snowpark provides supported programmatic DataFrame operations against Snowflake data.
  4. Cloning shares region-local storage constructs and is not equivalent to cross-region disaster recovery.

Explanation

Correct Answer

A:

Dynamic tables maintain query-defined results through Snowflake refresh management. This explains the condition: An engineer creates a dynamic table with a SELECT query and assumes it behaves like a normal manually written snapshot table. The corrective response is: Choose a dynamic table only when a target-lag refresh model suits the pipeline requirement.

Incorrect Answers

B:

Unquoted identifiers are normalized while quoted identifiers preserve case sensitivity rules. That mechanism explains a DIFFERENT Snowflake problem: An ETL engineer uses unquoted mixed-case identifiers and expects exact case-sensitive behavior across sessions. Here the relevant mechanism instead is: Dynamic tables maintain query-defined results through Snowflake refresh management.

C:

Snowpark provides supported programmatic DataFrame operations against Snowflake data. That mechanism explains a DIFFERENT Snowflake problem: A data science app requires Python transformations close to governed Snowflake tables but engineers plan repeated external exports. Here the relevant mechanism instead is: Dynamic tables maintain query-defined results through Snowflake refresh management.

D:

Cloning shares region-local storage constructs and is not equivalent to cross-region disaster recovery. That mechanism explains a DIFFERENT Snowflake problem: A data steward uses a zero-copy clone as a replacement for a remote recovery copy in a separate cloud region. Here the relevant mechanism instead is: Dynamic tables maintain query-defined results through Snowflake refresh management.

Question 652

A platform governance committee considers: An engineer creates a dynamic table with a SELECT query and assumes it behaves like a normal manually written snapshot table. What preventive check should be standardized?

  1. Document how file references, stages and security boundaries are maintained.
  2. Monitor refresh status and costs rather than treating dynamic tables as static outputs.
  3. Test input parsing and malformed payload handling in ingestion contracts.
  4. Review token usage, call frequency and cost alerts during model pilot checkpoints.

Explanation

Correct Answer

B:

Monitor refresh status and costs rather than treating dynamic tables as static outputs. This reduces recurrence of: Dynamic tables maintain query-defined results through Snowflake refresh management. The verification should demonstrate: The table refreshes toward the declared lag rather than requiring the team to rerun a one-time insert.

Incorrect Answers

A:

Document how file references, stages and security boundaries are maintained. That safeguard is aimed at ANOTHER risk: A team stores user-uploaded images and PDFs in a regular VARCHAR column and expects Snowflake to interpret them as file objects. It is less targeted than the control for: Dynamic tables maintain query-defined results through Snowflake refresh management.

C:

Test input parsing and malformed payload handling in ingestion contracts. That safeguard is aimed at ANOTHER risk: A migration tool defines a table column as VARCHAR then assumes all JSON path operators will work on it without conversion. It is less targeted than the control for: Dynamic tables maintain query-defined results through Snowflake refresh management.

D:

Review token usage, call frequency and cost alerts during model pilot checkpoints. That safeguard is aimed at ANOTHER risk: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. It is less targeted than the control for: Dynamic tables maintain query-defined results through Snowflake refresh management.

Question 653

An engineering team investigates the following Snowflake issue: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. Which configuration or processing decision is most appropriate?

  1. Evaluate an available governed Snowflake Cortex AI function for permitted text analysis after access and cost review.
  2. Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata.
  3. Store raw semi-structured payloads in VARIANT where appropriate and derive typed fields for analytic use.
  4. Set workload budgets and monitor supported Cortex AI usage and cost meters alongside quality metrics.

Explanation

Correct Answer

D:

Set workload budgets and monitor supported Cortex AI usage and cost meters alongside quality metrics. This directly addresses the described Snowflake condition: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. The mechanism is: AI function usage can create distinct consumption costs that require their own monitoring. Verify success using: The pilot stays inside an approved spend envelope while representative outputs remain useful.

Incorrect Answers

A:

Evaluate an available governed Snowflake Cortex AI function for permitted text analysis after access and cost review. That is suitable for a DIFFERENT Snowflake situation: A department wants sentiment analysis in SQL but proposes shipping every customer comment to an ungoverned third-party endpoint. It does not directly resolve the current requirement: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges.

B:

Evaluate a supported Cortex Search service for semantic retrieval over approved document text and metadata. That is suitable for a DIFFERENT Snowflake situation: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. It does not directly resolve the current requirement: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges.

C:

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 internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges.

Question 654

For a telecommunications provider, the original problem was: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. What observation confirms success?

  1. The pilot stays inside an approved spend envelope while representative outputs remain useful.
  2. A deployment preflight succeeds in the target account or selects an approved supported alternative.
  3. A least-privilege test session sees only authorized records while the application still performs its expected task.
  4. Execution timing and credits improve under measured query bursts without keeping the warehouse idle all day.

Explanation

Correct Answer

A:

The pilot stays inside an approved spend envelope while representative outputs remain useful. This validates the relevant action: Set workload budgets and monitor supported Cortex AI usage and cost meters alongside quality metrics. The underlying Snowflake behavior is: AI function usage can create distinct consumption costs that require their own monitoring.

Incorrect Answers

B:

A deployment preflight succeeds in the target account or selects an approved supported alternative. This evidence tests a DIFFERENT situation: A team treats Snowflake's managed AI inference as having exactly the same regional availability for every model. The correction required in this case is: Set workload budgets and monitor supported Cortex AI usage and cost meters alongside quality metrics.

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: Set workload budgets and monitor supported Cortex AI usage and cost meters alongside quality metrics.

D:

Execution timing and credits improve under measured query bursts without keeping the warehouse idle all day. This evidence tests a DIFFERENT situation: A recurring report finishes in two minutes but its warehouse auto-suspends after an extremely short idle timeout between closely spaced queries. The correction required in this case is: Set workload budgets and monitor supported Cortex AI usage and cost meters alongside quality metrics.

Question 655

In a case affecting a telecommunications provider, this issue appears: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. What explains it?

  1. Application presentation does not eliminate Snowflake authorization boundaries.
  2. AI function usage can create distinct consumption costs that require their own monitoring.
  3. Model registry governance links artifact identity to deployment approvals and monitoring.
  4. Open table formats and catalog integrations have control boundaries distinct from ordinary managed tables.

Explanation

Correct Answer

B:

AI function usage can create distinct consumption costs that require their own monitoring. This explains the condition: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. The corrective response is: Set workload budgets and monitor supported Cortex AI usage and cost meters alongside quality metrics.

Incorrect Answers

A:

Application presentation does not eliminate Snowflake authorization boundaries. That mechanism explains a DIFFERENT Snowflake problem: A company develops an internal Streamlit data app but assumes every user should automatically see the creator's entire warehouse data. Here the relevant mechanism instead is: AI function usage can create distinct consumption costs that require their own monitoring.

C:

Model registry governance links artifact identity to deployment approvals and monitoring. That mechanism explains a DIFFERENT Snowflake problem: A team wants to trigger governance checks whenever a Snowflake model registry artifact changes but relies on manual emails. Here the relevant mechanism instead is: AI function usage can create distinct consumption costs that require their own monitoring.

D:

Open table formats and catalog integrations have control boundaries distinct from ordinary managed tables. That mechanism explains a DIFFERENT Snowflake problem: An application developer assumes an external Iceberg catalog table is administered identically to a native Snowflake-managed table. Here the relevant mechanism instead is: AI function usage can create distinct consumption costs that require their own monitoring.

Question 656

After remediating the Snowflake issue, the team reviews: An internal AI pilot is evaluated only on output quality while unbounded model calls inflate consumption charges. Which recurring control is most targeted?

  1. Pin availability checks to target regions in AI application deployment reviews.
  2. Audit registry versions and deployment history at every release.
  3. Review token usage, call frequency and cost alerts during model pilot checkpoints.
  4. Review clone cleanup and change-driven storage growth rather than assuming free perpetual copies.

Explanation

Correct Answer

C:

Review token usage, call frequency and cost alerts during model pilot checkpoints. This reduces recurrence of: AI function usage can create distinct consumption costs that require their own monitoring. The verification should demonstrate: The pilot stays inside an approved spend envelope while representative outputs remain useful.

Incorrect Answers

A:

Pin availability checks to target regions in AI application deployment reviews. That safeguard is aimed at ANOTHER risk: A team treats Snowflake's managed AI inference as having exactly the same regional availability for every model. It is less targeted than the control for: AI function usage can create distinct consumption costs that require their own monitoring.

B:

Audit registry versions and deployment history at every release. That safeguard is aimed at ANOTHER risk: A team wants to trigger governance checks whenever a Snowflake model registry artifact changes but relies on manual emails. It is less targeted than the control for: AI function usage can create distinct consumption costs that require their own monitoring.

D:

Review clone cleanup and change-driven storage growth rather than assuming free perpetual copies. That safeguard is aimed at ANOTHER risk: A developer clones a large table for integration testing and budgets for an immediate full physical data copy. It is less targeted than the control for: AI function usage can create distinct consumption costs that require their own monitoring.

Question 657

At a consumer marketplace, a Snowflake implementation review finds: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. Which action best addresses this requirement?

  1. Use distinct service identities with appropriately supported authentication and scoped roles for each integration.
  2. Review the intended role hierarchy and verify inheritance upward through granted roles.
  3. Delegate scoped CREATE TABLE in a controlled schema and required USAGE rather than broad database ownership.
  4. Assign controlled schema/object ownership and tag stewardship policies with accountable approvers.

Explanation

Correct Answer

A:

Use distinct service identities with appropriately supported authentication and scoped roles for each integration. This directly addresses the described Snowflake condition: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. The mechanism is: Shared credentials undermine per-application attribution and least-privilege offboarding. Verify success using: Query history attributes activity to the intended service identity and a revoked app credential stops only its app.

Incorrect Answers

B:

Review the intended role hierarchy and verify inheritance upward through granted roles. That is suitable for a DIFFERENT Snowflake situation: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. It does not directly resolve the current requirement: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data.

C:

Delegate scoped CREATE TABLE in a controlled schema and required USAGE rather than broad database ownership. That is suitable for a DIFFERENT Snowflake situation: An engineer gives an application OWNERSHIP on a production database merely to create one staging table. It does not directly resolve the current requirement: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data.

D:

Assign controlled schema/object ownership and tag stewardship policies with accountable approvers. That is suitable for a DIFFERENT Snowflake situation: An enterprise needs a reliable inventory of who owns sensitive schemas, but its governance tags are edited without review. It does not directly resolve the current requirement: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data.

Question 658

After the approved change, engineers revisit: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. Which result establishes the intended state?

  1. The parent role's effective rights include privileges inherited from authorized subordinate roles.
  2. Query history attributes activity to the intended service identity and a revoked app credential stops only its app.
  3. The consumer can read the created view without gaining access to base tables beyond design intent.
  4. A valid test token for the approved audience succeeds while a mismatched token fails.

Explanation

Correct Answer

B:

Query history attributes activity to the intended service identity and a revoked app credential stops only its app. This validates the relevant action: Use distinct service identities with appropriately supported authentication and scoped roles for each integration. The underlying Snowflake behavior is: Shared credentials undermine per-application attribution and least-privilege offboarding.

Incorrect Answers

A:

The parent role's effective rights include privileges inherited from authorized subordinate roles. This evidence tests a DIFFERENT situation: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. The correction required in this case is: Use distinct service identities with appropriately supported authentication and scoped roles for each integration.

C:

The consumer can read the created view without gaining access to base tables beyond design intent. This evidence tests a DIFFERENT situation: A role can create a view in a schema but analysts cannot SELECT from the newly created view. The correction required in this case is: Use distinct service identities with appropriately supported authentication and scoped roles for each integration.

D:

A valid test token for the approved audience succeeds while a mismatched token fails. This evidence tests a DIFFERENT situation: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. The correction required in this case is: Use distinct service identities with appropriately supported authentication and scoped roles for each integration.

Question 659

A root-cause investigation considers: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. What is the most applicable explanation?

  1. Compute usage is a separate privilege from database object DML privileges.
  2. Future grants automate access for future objects in a defined scope, subject to supported precedence.
  3. Shared credentials undermine per-application attribution and least-privilege offboarding.
  4. Data policies complement rather than replace the core authentication and object authorization model.

Explanation

Correct Answer

C:

Shared credentials undermine per-application attribution and least-privilege offboarding. This explains the condition: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. The corrective response is: Use distinct service identities with appropriately supported authentication and scoped roles for each integration.

Incorrect Answers

A:

Compute usage is a separate privilege from database object DML privileges. That mechanism explains a DIFFERENT Snowflake problem: An app deploys with a role that has INSERT but no warehouse usage, causing its insert-select query to fail. Here the relevant mechanism instead is: Shared credentials undermine per-application attribution and least-privilege offboarding.

B:

Future grants automate access for future objects in a defined scope, subject to supported precedence. That mechanism explains a DIFFERENT Snowflake problem: A project grants future objects manually each week and a newly created table is invisible to its application role. Here the relevant mechanism instead is: Shared credentials undermine per-application attribution and least-privilege offboarding.

D:

Data policies complement rather than replace the core authentication and object authorization model. That mechanism explains a DIFFERENT Snowflake problem: A security team thinks a masking policy can replace both network controls and database RBAC for a regulated dataset. Here the relevant mechanism instead is: Shared credentials undermine per-application attribution and least-privilege offboarding.

Question 660

During operational handoff for this problem: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. Which guardrail should be included?

  1. Audit highly privileged roles and replace convenience grants with scoped functional roles.
  2. Test effective permissions after role hierarchy changes rather than assuming role names set power.
  3. Schedule credential expiration and parallel-cutover tests for programmatic access.
  4. Inventory service-user ownership and rotate credentials with controlled revocation tests.

Explanation

Correct Answer

D:

Inventory service-user ownership and rotate credentials with controlled revocation tests. This reduces recurrence of: Shared credentials undermine per-application attribution and least-privilege offboarding. The verification should demonstrate: Query history attributes activity to the intended service identity and a revoked app credential stops only its app.

Incorrect Answers

A:

Audit highly privileged roles and replace convenience grants with scoped functional roles. That safeguard is aimed at ANOTHER risk: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. It is less targeted than the control for: Shared credentials undermine per-application attribution and least-privilege offboarding.

B:

Test effective permissions after role hierarchy changes rather than assuming role names set power. That safeguard is aimed at ANOTHER risk: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. It is less targeted than the control for: Shared credentials undermine per-application attribution and least-privilege offboarding.

C:

Schedule credential expiration and parallel-cutover tests for programmatic access. That safeguard is aimed at ANOTHER risk: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. It is less targeted than the control for: Shared credentials undermine per-application attribution and least-privilege offboarding.