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 3

Question 20

During operational handoff for this problem: A department wants sentiment analysis in SQL but proposes shipping every customer comment to an ungoverned third-party endpoint. Which guardrail should be included?

  1. Test generated SQL and model semantics against finance-approved calculations.
  2. Pin availability checks to target regions in AI application deployment reviews.
  3. Review min and max cluster settings against real hourly demand.
  4. Classify data and review function availability and charges before rollout.

Explanation

Correct Answer

D:

Classify data and review function availability and charges before rollout. This reduces recurrence of: Supported Cortex AI functions can provide managed model operations through Snowflake SQL interfaces. The verification should demonstrate: A small approved comment sample yields results while sensitive rows remain inside the approved processing boundary.

Incorrect Answers

A:

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: Supported Cortex AI functions can provide managed model operations through Snowflake SQL interfaces.

B:

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: Supported Cortex AI functions can provide managed model operations through Snowflake SQL interfaces.

C:

Review min and max cluster settings against real hourly demand. That safeguard is aimed at ANOTHER risk: A multi-cluster warehouse has a large fixed minimum cluster count during a quiet overnight period. It is less targeted than the control for: Supported Cortex AI functions can provide managed model operations through Snowflake SQL interfaces.

Question 21

A data-platform team must resolve: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. Which technical change most directly solves it?

  1. Grant the intended view SELECT plus necessary container privileges to the consuming role.
  2. Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.
  3. Separate user/role provisioning from data-object privileges and use scoped roles for table access.
  4. Evaluate approved cloud private connectivity such as PrivateLink or equivalent supported private endpoint integration.

Explanation

Correct Answer

B:

Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table. This directly addresses the described Snowflake condition: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. The mechanism is: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers. Verify success using: The role can query the intended fact table without adding unrestricted administrative grants.

Incorrect Answers

A:

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: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation.

C:

Separate user/role provisioning from data-object privileges and use scoped roles for table access. That is suitable for a DIFFERENT Snowflake situation: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. It does not directly resolve the current requirement: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation.

D:

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: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation.

Question 22

A Snowflake acceptance test follows this incident: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. What evidence most directly proves the correction?

  1. The app role can execute its expected insert-select without receiving control over unrelated warehouses.
  2. Query history attributes activity to the intended service identity and a revoked app credential stops only its app.
  3. The role can query the intended fact table without adding unrestricted administrative grants.
  4. The affected identity cannot read the restricted view through any remaining authorized role chain.

Explanation

Correct Answer

C:

The role can query the intended fact table without adding unrestricted administrative grants. This validates the relevant action: Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table. The underlying Snowflake behavior is: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

Incorrect Answers

A:

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: Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.

B:

Query history attributes activity to the intended service identity and a revoked app credential stops only its app. This evidence tests a DIFFERENT situation: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. The correction required in this case is: Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.

D:

The affected identity cannot read the restricted view through any remaining authorized role chain. This evidence tests a DIFFERENT situation: A data steward revokes a user's role but their previous worksheet continues to query an authorized view under a different active role. The correction required in this case is: Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.

Question 23

The data-platform team observes: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. Which architectural or processing fact matters most?

  1. Effective SQL authorization depends on the session's active role context and configured secondary roles.
  2. Account-wide administration is broader than the role privileges needed for read-only analysis.
  3. Usage, access history and cost metering contain different evidence about data access.
  4. Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

Explanation

Correct Answer

D:

Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers. This explains the condition: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. The corrective response is: Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.

Incorrect Answers

A:

Effective SQL authorization depends on the session's active role context and configured secondary roles. That mechanism explains a DIFFERENT Snowflake problem: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. Here the relevant mechanism instead is: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

B:

Account-wide administration is broader than the role privileges needed for read-only analysis. That mechanism explains a DIFFERENT Snowflake problem: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. Here the relevant mechanism instead is: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

C:

Usage, access history and cost metering contain different evidence about data access. That mechanism explains a DIFFERENT Snowflake problem: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. Here the relevant mechanism instead is: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

Question 24

For a university data platform, this issue must not recur: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. Which review control fits best?

  1. Check container and object grants together when diagnosing access failures.
  2. Inventory service-user ownership and rotate credentials with controlled revocation tests.
  3. Audit highly privileged roles and replace convenience grants with scoped functional roles.
  4. Review integration trust endpoints and claim mappings after IdP updates.

Explanation

Correct Answer

A:

Check container and object grants together when diagnosing access failures. This reduces recurrence of: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers. The verification should demonstrate: The role can query the intended fact table without adding unrestricted administrative grants.

Incorrect Answers

B:

Inventory service-user ownership and rotate credentials with controlled revocation tests. That safeguard is aimed at ANOTHER risk: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. It is less targeted than the control for: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

C:

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: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

D:

Review integration trust endpoints and claim mappings after IdP updates. That safeguard is aimed at ANOTHER risk: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. It is less targeted than the control for: Snowflake privilege checks include object access plus name-resolution privileges on database and schema containers.

Question 25

In a governed Snowflake environment, the reported condition is: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. What should be implemented first?

  1. Configure and enforce the supported authentication policy and MFA requirements for the relevant users.
  2. Design an approved emergency-access path with protected authentication and controlled network policy exceptions.
  3. Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.
  4. Inspect all effective role grants and session role context, then revoke the unintended privilege path.

Explanation

Correct Answer

C:

Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges. This directly addresses the described Snowflake condition: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. The mechanism is: Network policies constrain connection origins independently of data object privileges. Verify success using: Authorized corporate connections succeed while an unapproved test source is rejected.

Incorrect Answers

A:

Configure and enforce the supported authentication policy and MFA requirements for the relevant users. That is suitable for a DIFFERENT Snowflake situation: Security requires stronger authentication for privileged human users but the account relies only on passwords. It does not directly resolve the current requirement: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations.

B:

Design an approved emergency-access path with protected authentication and controlled network policy exceptions. That is suitable for a DIFFERENT Snowflake situation: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. It does not directly resolve the current requirement: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations.

D:

Inspect all effective role grants and session role context, then revoke the unintended privilege path. That is suitable for a DIFFERENT Snowflake situation: A data steward revokes a user's role but their previous worksheet continues to query an authorized view under a different active role. It does not directly resolve the current requirement: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations.

Question 26

A test plan evaluates: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. Which evidence should be required before release?

  1. A privileged sign-in prompts for the required additional factor while noncompliant login fails.
  2. An incident drill confirms required emergency recovery without opening uncontrolled public login.
  3. The role can query the intended fact table without adding unrestricted administrative grants.
  4. Authorized corporate connections succeed while an unapproved test source is rejected.

Explanation

Correct Answer

D:

Authorized corporate connections succeed while an unapproved test source is rejected. This validates the relevant action: Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges. The underlying Snowflake behavior is: Network policies constrain connection origins independently of data object privileges.

Incorrect Answers

A:

A privileged sign-in prompts for the required additional factor while noncompliant login fails. This evidence tests a DIFFERENT situation: Security requires stronger authentication for privileged human users but the account relies only on passwords. The correction required in this case is: Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.

B:

An incident drill confirms required emergency recovery without opening uncontrolled public login. This evidence tests a DIFFERENT situation: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. The correction required in this case is: Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.

C:

The role can query the intended fact table without adding unrestricted administrative grants. This evidence tests a DIFFERENT situation: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. The correction required in this case is: Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.

Question 27

A Snowflake incident report notes: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. What underlying mechanism explains the behavior?

  1. Network policies constrain connection origins independently of data object privileges.
  2. Federated authentication requires a consistent identity mapping independently of database grants.
  3. Strong perimeter policies can lock out operators without properly governed emergency procedures.
  4. Role grants create inherited privilege relationships that flow through the role hierarchy.

Explanation

Correct Answer

A:

Network policies constrain connection origins independently of data object privileges. This explains the condition: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. The corrective response is: Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.

Incorrect Answers

B:

Federated authentication requires a consistent identity mapping independently of database grants. That mechanism explains a DIFFERENT Snowflake problem: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. Here the relevant mechanism instead is: Network policies constrain connection origins independently of data object privileges.

C:

Strong perimeter policies can lock out operators without properly governed emergency procedures. That mechanism explains a DIFFERENT Snowflake problem: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. Here the relevant mechanism instead is: Network policies constrain connection origins independently of data object privileges.

D:

Role grants create inherited privilege relationships that flow through the role hierarchy. That mechanism explains a DIFFERENT Snowflake problem: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. Here the relevant mechanism instead is: Network policies constrain connection origins independently of data object privileges.

Question 28

A platform governance committee considers: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. What preventive check should be standardized?

  1. Test naming changes in IdP and Snowflake before federation migrations.
  2. Maintain approved egress IP ranges and test exceptions after network changes.
  3. Exercise break-glass access and log each use after authentication policy changes.
  4. Document audit view latency, retention and roles needed to query access history.

Explanation

Correct Answer

B:

Maintain approved egress IP ranges and test exceptions after network changes. This reduces recurrence of: Network policies constrain connection origins independently of data object privileges. The verification should demonstrate: Authorized corporate connections succeed while an unapproved test source is rejected.

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: Network policies constrain connection origins independently of data object privileges.

C:

Exercise break-glass access and log each use after authentication policy changes. That safeguard is aimed at ANOTHER risk: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. It is less targeted than the control for: Network policies constrain connection origins independently of data object privileges.

D:

Document audit view latency, retention and roles needed to query access history. That safeguard is aimed at ANOTHER risk: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. It is less targeted than the control for: Network policies constrain connection origins independently of data object privileges.

Question 29

An engineering team investigates the following Snowflake issue: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. Which configuration or processing decision is most appropriate?

  1. Use governed classification tags and appropriate policy associations to apply consistent protection at scale.
  2. Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.
  3. Review supported SSO federation settings and login-name/user mapping for the chosen identity provider.
  4. Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

Explanation

Correct Answer

D:

Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression. This directly addresses the described Snowflake condition: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. The mechanism is: Masking policies evaluate authorized context at query time rather than copying a second redacted table. Verify success using: A payroll role sees approved values while the analyst sees the configured masked representation.

Incorrect Answers

A:

Use governed classification tags and appropriate policy associations to apply consistent protection at scale. That is suitable for a DIFFERENT Snowflake situation: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. It does not directly resolve the current requirement: A human resources dataset contains salary amounts, and a general analyst role should see only masked values.

B:

Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns. That is suitable for a DIFFERENT Snowflake situation: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. It does not directly resolve the current requirement: A human resources dataset contains salary amounts, and a general analyst role should see only masked values.

C:

Review supported SSO federation settings and login-name/user mapping for the chosen identity provider. That is suitable for a DIFFERENT Snowflake situation: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. It does not directly resolve the current requirement: A human resources dataset contains salary amounts, and a general analyst role should see only masked values.

Question 30

For a telecommunications provider, the original problem was: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. What observation confirms success?

  1. A payroll role sees approved values while the analyst sees the configured masked representation.
  2. The consumer role queries its approved interface but cannot read the raw customer table directly.
  3. A governance report identifies responsible owners and classified fields without unauthorized tag drift.
  4. Authorized corporate connections succeed while an unapproved test source is rejected.

Explanation

Correct Answer

A:

A payroll role sees approved values while the analyst sees the configured masked representation. This validates the relevant action: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression. The underlying Snowflake behavior is: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

Incorrect Answers

B:

The consumer role queries its approved interface but cannot read the raw customer table directly. This evidence tests a DIFFERENT situation: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. The correction required in this case is: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

C:

A governance report identifies responsible owners and classified fields without unauthorized tag drift. This evidence tests a DIFFERENT situation: An enterprise needs a reliable inventory of who owns sensitive schemas, but its governance tags are edited without review. The correction required in this case is: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

D:

Authorized corporate connections succeed while an unapproved test source is rejected. This evidence tests a DIFFERENT situation: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. The correction required in this case is: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.