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 50

Question 490

A test plan evaluates: A retailer builds an ML feature pipeline by copying full source datasets to laptops every day. Which evidence should be required before release?

  1. A pilot maps representative natural-language revenue questions to valid SQL based on approved definitions.
  2. A controlled nearest-neighbor example orders relevant embedding vectors by the intended similarity measure.
  3. A UDF call returns an expression value while the controlled procedure performs its intended procedural workflow.
  4. A representative feature calculation runs against permitted Snowflake data with fewer uncontrolled exports.

Explanation

Correct Answer

D:

A representative feature calculation runs against permitted Snowflake data with fewer uncontrolled exports. This validates the relevant action: Use supported Snowpark ML or in-account transformations appropriate for the workload and governance policy. The underlying Snowflake behavior is: Data-local processing reduces unnecessary movement of governed data and centralizes access control.

Incorrect Answers

A:

A pilot maps representative natural-language revenue questions to valid SQL based on approved definitions. This evidence tests a DIFFERENT situation: A business team asks an LLM to answer revenue questions but the model frequently invents column names and joins. The correction required in this case is: Use supported Snowpark ML or in-account transformations appropriate for the workload and governance policy.

B:

A controlled nearest-neighbor example orders relevant embedding vectors by the intended similarity measure. This evidence tests a DIFFERENT situation: An application stores vector embeddings but a developer expects standard string comparison to rank semantic similarity automatically. The correction required in this case is: Use supported Snowpark ML or in-account transformations appropriate for the workload and governance policy.

C:

A UDF call returns an expression value while the controlled procedure performs its intended procedural workflow. This evidence tests a DIFFERENT situation: A SQL reporting team mixes SQL UDFs and stored procedures as though both have identical invocation and side effects. The correction required in this case is: Use supported Snowpark ML or in-account transformations appropriate for the workload and governance policy.

Question 491

A Snowflake incident report notes: A retailer builds an ML feature pipeline by copying full source datasets to laptops every day. What underlying mechanism explains the behavior?

  1. Data-local processing reduces unnecessary movement of governed data and centralizes access control.
  2. AI application logic must respect Snowflake RBAC and data-governance rules on its source queries.
  3. AI function usage can create distinct consumption costs that require their own monitoring.
  4. Snowflake historical queries can use the current table or view schema even when querying earlier data.

Explanation

Correct Answer

A:

Data-local processing reduces unnecessary movement of governed data and centralizes access control. This explains the condition: A retailer builds an ML feature pipeline by copying full source datasets to laptops every day. The corrective response is: Use supported Snowpark ML or in-account transformations appropriate for the workload and governance policy.

Incorrect Answers

B:

AI application logic must respect Snowflake RBAC and data-governance rules on its source queries. That mechanism explains a DIFFERENT Snowflake problem: A developer combines customer and product records for an LLM app without considering masking policy and row restrictions. Here the relevant mechanism instead is: Data-local processing reduces unnecessary movement of governed data and centralizes access control.

C:

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: Data-local processing reduces unnecessary movement of governed data and centralizes access control.

D:

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: Data-local processing reduces unnecessary movement of governed data and centralizes access control.

Question 492

A platform governance committee considers: A retailer builds an ML feature pipeline by copying full source datasets to laptops every day. What preventive check should be standardized?

  1. Record vector dimensions, embedding model and evaluation methodology.
  2. Review feature reproducibility and data lineage across training runs.
  3. Test generated SQL and model semantics against finance-approved calculations.
  4. Review package/network permissions and cost before adopting new Snowpark processing.

Explanation

Correct Answer

B:

Review feature reproducibility and data lineage across training runs. This reduces recurrence of: Data-local processing reduces unnecessary movement of governed data and centralizes access control. The verification should demonstrate: A representative feature calculation runs against permitted Snowflake data with fewer uncontrolled exports.

Incorrect Answers

A:

Record vector dimensions, embedding model and evaluation methodology. That safeguard is aimed at ANOTHER risk: An application stores vector embeddings but a developer expects standard string comparison to rank semantic similarity automatically. It is less targeted than the control for: Data-local processing reduces unnecessary movement of governed data and centralizes access control.

C:

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: Data-local processing reduces unnecessary movement of governed data and centralizes access control.

D:

Review package/network permissions and cost before adopting new Snowpark processing. That safeguard is aimed at ANOTHER risk: A data science app requires Python transformations close to governed Snowflake tables but engineers plan repeated external exports. It is less targeted than the control for: Data-local processing reduces unnecessary movement of governed data and centralizes access control.

Question 493

An engineering team investigates the following Snowflake issue: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. Which configuration or processing decision is most appropriate?

  1. Delegate scoped CREATE TABLE in a controlled schema and required USAGE rather than broad database ownership.
  2. Create and assign a least-privilege reporting role with scoped container usage and table select rights.
  3. Assign controlled schema/object ownership and tag stewardship policies with accountable approvers.
  4. Set or activate the intended role for the connection and inspect session role context.

Explanation

Correct Answer

D:

Set or activate the intended role for the connection and inspect session role context. This directly addresses the described Snowflake condition: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. The mechanism is: Effective SQL authorization depends on the session's active role context and configured secondary roles. Verify success using: Session inspection shows the correct active primary role and authorized query behavior.

Incorrect Answers

A:

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 user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session.

B:

Create and assign a least-privilege reporting role with scoped container usage and table select rights. That is suitable for a DIFFERENT Snowflake situation: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. It does not directly resolve the current requirement: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session.

C:

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 user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session.

Question 494

For a global logistics company, the original problem was: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. What observation confirms success?

  1. Session inspection shows the correct active primary role and authorized query behavior.
  2. The application creates its approved staging object while database ownership remains with governance.
  3. The app role can execute its expected insert-select without receiving control over unrelated warehouses.
  4. A valid test token for the approved audience succeeds while a mismatched token fails.

Explanation

Correct Answer

A:

Session inspection shows the correct active primary role and authorized query behavior. This validates the relevant action: Set or activate the intended role for the connection and inspect session role context. The underlying Snowflake behavior is: Effective SQL authorization depends on the session's active role context and configured secondary roles.

Incorrect Answers

B:

The application creates its approved staging object while database ownership remains with governance. This evidence tests a DIFFERENT situation: An engineer gives an application OWNERSHIP on a production database merely to create one staging table. The correction required in this case is: Set or activate the intended role for the connection and inspect session role context.

C:

The app role can execute its expected insert-select without receiving control over unrelated warehouses. This evidence tests a DIFFERENT situation: An app deploys with a role that has INSERT but no warehouse usage, causing its insert-select query to fail. The correction required in this case is: Set or activate the intended role for the connection and inspect session role context.

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: Set or activate the intended role for the connection and inspect session role context.

Question 495

In a case affecting a global logistics company, this issue appears: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. What explains it?

  1. Shared credentials undermine per-application attribution and least-privilege offboarding.
  2. Effective SQL authorization depends on the session's active role context and configured secondary roles.
  3. Snowflake system administration responsibilities and data access are distinct privilege domains.
  4. Secure views reduce certain metadata exposure paths; they are not a substitute for all row and column controls.

Explanation

Correct Answer

B:

Effective SQL authorization depends on the session's active role context and configured secondary roles. This explains the condition: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. The corrective response is: Set or activate the intended role for the connection and inspect session role context.

Incorrect Answers

A:

Shared credentials undermine per-application attribution and least-privilege offboarding. That mechanism explains a DIFFERENT Snowflake problem: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. Here the relevant mechanism instead is: Effective SQL authorization depends on the session's active role context and configured secondary roles.

C:

Snowflake system administration responsibilities and data access are distinct privilege domains. That mechanism explains a DIFFERENT Snowflake problem: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. Here the relevant mechanism instead is: Effective SQL authorization depends on the session's active role context and configured secondary roles.

D:

Secure views reduce certain metadata exposure paths; they are not a substitute for all row and column controls. That mechanism explains a DIFFERENT Snowflake problem: A contractor is granted a secure view but its definition reveals an underlying protected calculation when copied into an ordinary view. Here the relevant mechanism instead is: Effective SQL authorization depends on the session's active role context and configured secondary roles.

Question 496

After remediating the Snowflake issue, the team reviews: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. Which recurring control is most targeted?

  1. Check container and object grants together when diagnosing access failures.
  2. Audit highly privileged roles and replace convenience grants with scoped functional roles.
  3. Test service integrations with real connection parameters, not only interactive worksheets.
  4. Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless.

Explanation

Correct Answer

C:

Test service integrations with real connection parameters, not only interactive worksheets. This reduces recurrence of: Effective SQL authorization depends on the session's active role context and configured secondary roles. The verification should demonstrate: Session inspection shows the correct active primary role and authorized query behavior.

Incorrect Answers

A:

Check container and object grants together when diagnosing access failures. That safeguard is aimed at ANOTHER risk: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. It is less targeted than the control for: Effective SQL authorization depends on the session's active role context and configured secondary roles.

B:

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: Effective SQL authorization depends on the session's active role context and configured secondary roles.

D:

Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless. That safeguard is aimed at ANOTHER risk: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. It is less targeted than the control for: Effective SQL authorization depends on the session's active role context and configured secondary roles.

Question 497

At a subscription SaaS business, a Snowflake implementation review finds: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. Which action best addresses this requirement?

  1. Design an approved emergency-access path with protected authentication and controlled network policy exceptions.
  2. Evaluate approved cloud private connectivity such as PrivateLink or equivalent supported private endpoint integration.
  3. Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.
  4. Grant the intended view SELECT plus necessary container privileges to the consuming role.

Explanation

Correct Answer

A:

Design an approved emergency-access path with protected authentication and controlled network policy exceptions. This directly addresses the described Snowflake condition: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. The mechanism is: Strong perimeter policies can lock out operators without properly governed emergency procedures. Verify success using: An incident drill confirms required emergency recovery without opening uncontrolled public login.

Incorrect Answers

B:

Evaluate approved cloud private connectivity such as PrivateLink or equivalent supported private endpoint integration. That is suitable for a DIFFERENT Snowflake situation: A company wants external clients to reach Snowflake without traversing public Internet but plans only a network allowlist. It does not directly resolve the current requirement: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access.

C:

Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges. That is suitable for a DIFFERENT Snowflake situation: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. It does not directly resolve the current requirement: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access.

D:

Grant the intended view SELECT plus necessary container privileges to the consuming role. That is suitable for a DIFFERENT Snowflake situation: A role can create a view in a schema but analysts cannot SELECT from the newly created view. It does not directly resolve the current requirement: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access.

Question 498

After the approved change, engineers revisit: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. Which result establishes the intended state?

  1. A valid test token for the approved audience succeeds while a mismatched token fails.
  2. An incident drill confirms required emergency recovery without opening uncontrolled public login.
  3. One app credential can be rotated and verified while other distinct integrations continue running.
  4. The warehouse stops consuming idle compute credits but retained tables still contribute to storage.

Explanation

Correct Answer

B:

An incident drill confirms required emergency recovery without opening uncontrolled public login. This validates the relevant action: Design an approved emergency-access path with protected authentication and controlled network policy exceptions. The underlying Snowflake behavior is: Strong perimeter policies can lock out operators without properly governed emergency procedures.

Incorrect Answers

A:

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: Design an approved emergency-access path with protected authentication and controlled network policy exceptions.

C:

One app credential can be rotated and verified while other distinct integrations continue running. This evidence tests a DIFFERENT situation: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. The correction required in this case is: Design an approved emergency-access path with protected authentication and controlled network policy exceptions.

D:

The warehouse stops consuming idle compute credits but retained tables still contribute to storage. This evidence tests a DIFFERENT situation: A team thinks suspending a warehouse eliminates storage and file-stage charges for inactive datasets. The correction required in this case is: Design an approved emergency-access path with protected authentication and controlled network policy exceptions.

Question 499

A root-cause investigation considers: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. What is the most applicable explanation?

  1. IP allowlisting and private network attachment solve different transport security requirements.
  2. Authentication factors protect account entry and are distinct from SQL roles after sign-in.
  3. Strong perimeter policies can lock out operators without properly governed emergency procedures.
  4. Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

Explanation

Correct Answer

C:

Strong perimeter policies can lock out operators without properly governed emergency procedures. This explains the condition: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. The corrective response is: Design an approved emergency-access path with protected authentication and controlled network policy exceptions.

Incorrect Answers

A:

IP allowlisting and private network attachment solve different transport security requirements. That mechanism explains a DIFFERENT Snowflake problem: A company wants external clients to reach Snowflake without traversing public Internet but plans only a network allowlist. Here the relevant mechanism instead is: Strong perimeter policies can lock out operators without properly governed emergency procedures.

B:

Authentication factors protect account entry and are distinct from SQL roles after sign-in. That mechanism explains a DIFFERENT Snowflake problem: Security requires stronger authentication for privileged human users but the account relies only on passwords. Here the relevant mechanism instead is: Strong perimeter policies can lock out operators without properly governed emergency procedures.

D:

Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers. That mechanism explains a DIFFERENT Snowflake problem: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. Here the relevant mechanism instead is: Strong perimeter policies can lock out operators without properly governed emergency procedures.

Question 500

During operational handoff for this problem: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. Which guardrail should be included?

  1. Test naming changes in IdP and Snowflake before federation migrations.
  2. Test privileged account enrollment and recovery before enforcement rollout.
  3. Test layered access with both allowed and denied user cases.
  4. Exercise break-glass access and log each use after authentication policy changes.

Explanation

Correct Answer

D:

Exercise break-glass access and log each use after authentication policy changes. This reduces recurrence of: Strong perimeter policies can lock out operators without properly governed emergency procedures. The verification should demonstrate: An incident drill confirms required emergency recovery without opening uncontrolled public login.

Incorrect Answers

A:

Test naming changes in IdP and Snowflake before federation migrations. That safeguard is aimed at ANOTHER risk: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. It is less targeted than the control for: Strong perimeter policies can lock out operators without properly governed emergency procedures.

B:

Test privileged account enrollment and recovery before enforcement rollout. That safeguard is aimed at ANOTHER risk: Security requires stronger authentication for privileged human users but the account relies only on passwords. It is less targeted than the control for: Strong perimeter policies can lock out operators without properly governed emergency procedures.

C:

Test layered access with both allowed and denied user cases. That safeguard is aimed at ANOTHER risk: A security team thinks a masking policy can replace both network controls and database RBAC for a regulated dataset. It is less targeted than the control for: Strong perimeter policies can lock out operators without properly governed emergency procedures.