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 11

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.

Question 101

A data-platform team must resolve: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. Which technical change most directly solves it?

  1. Use distinct service identities with appropriately supported authentication and scoped roles for each integration.
  2. Create and assign a least-privilege reporting role with scoped container usage and table select rights.
  3. Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.
  4. Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

Explanation

Correct Answer

B:

Create and assign a least-privilege reporting role with scoped container usage and table select rights. This directly addresses the described Snowflake condition: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. The mechanism is: Account-wide administration is broader than the role privileges needed for read-only analysis. Verify success using: The analyst can read approved reports without gaining account-wide administrative powers.

Incorrect Answers

A:

Use distinct service identities with appropriately supported authentication and scoped roles for each integration. That is suitable for a DIFFERENT Snowflake situation: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. It does not directly resolve the current requirement: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table.

C:

Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table. That is suitable for a DIFFERENT Snowflake situation: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. It does not directly resolve the current requirement: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table.

D:

Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression. That is suitable for a DIFFERENT Snowflake situation: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. It does not directly resolve the current requirement: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table.

Question 102

A Snowflake acceptance test follows this incident: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. What evidence most directly proves the correction?

  1. The consumer can read the created view without gaining access to base tables beyond design intent.
  2. The application creates its approved staging object while database ownership remains with governance.
  3. The analyst can read approved reports without gaining account-wide administrative powers.
  4. Authorized corporate connections succeed while an unapproved test source is rejected.

Explanation

Correct Answer

C:

The analyst can read approved reports without gaining account-wide administrative powers. This validates the relevant action: Create and assign a least-privilege reporting role with scoped container usage and table select rights. The underlying Snowflake behavior is: Account-wide administration is broader than the role privileges needed for read-only analysis.

Incorrect Answers

A:

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: Create and assign a least-privilege reporting role with scoped container usage and table select rights.

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: Create and assign a least-privilege reporting role with scoped container usage and table select rights.

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: Create and assign a least-privilege reporting role with scoped container usage and table select rights.

Question 103

The data-platform team observes: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. Which architectural or processing fact matters most?

  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. Least privilege is enforced at object and policy boundaries, not by naming tables as sensitive.
  4. Account-wide administration is broader than the role privileges needed for read-only analysis.

Explanation

Correct Answer

D:

Account-wide administration is broader than the role privileges needed for read-only analysis. This explains the condition: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. The corrective response is: Create and assign a least-privilege reporting role with scoped container usage and table select rights.

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: Account-wide administration is broader than the role privileges needed for read-only analysis.

B:

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: Account-wide administration is broader than the role privileges needed for read-only analysis.

C:

Least privilege is enforced at object and policy boundaries, not by naming tables as sensitive. That mechanism explains a DIFFERENT Snowflake problem: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. Here the relevant mechanism instead is: Account-wide administration is broader than the role privileges needed for read-only analysis.

Question 104

For a regulated healthcare organization, this issue must not recur: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. Which review control fits best?

  1. Audit highly privileged roles and replace convenience grants with scoped functional roles.
  2. Test service integrations with real connection parameters, not only interactive worksheets.
  3. Add new-view grants to deployment templates and access test fixtures.
  4. Validate private DNS and endpoint routing across failover conditions.

Explanation

Correct Answer

A:

Audit highly privileged roles and replace convenience grants with scoped functional roles. This reduces recurrence of: Account-wide administration is broader than the role privileges needed for read-only analysis. The verification should demonstrate: The analyst can read approved reports without gaining account-wide administrative powers.

Incorrect Answers

B:

Test service integrations with real connection parameters, not only interactive worksheets. That safeguard is aimed at ANOTHER risk: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. It is less targeted than the control for: Account-wide administration is broader than the role privileges needed for read-only analysis.

C:

Add new-view grants to deployment templates and access test fixtures. That safeguard is aimed at ANOTHER risk: A role can create a view in a schema but analysts cannot SELECT from the newly created view. It is less targeted than the control for: Account-wide administration is broader than the role privileges needed for read-only analysis.

D:

Validate private DNS and endpoint routing across failover conditions. That safeguard is aimed at ANOTHER risk: A company wants external clients to reach Snowflake without traversing public Internet but plans only a network allowlist. It is less targeted than the control for: Account-wide administration is broader than the role privileges needed for read-only analysis.

Question 105

In a governed Snowflake environment, the reported condition is: Security requires stronger authentication for privileged human users but the account relies only on passwords. What should be implemented first?

  1. Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.
  2. Configure the supported security integration with correct issuer, audience and role-scope mapping.
  3. Configure and enforce the supported authentication policy and MFA requirements for the relevant users.
  4. Delegate scoped CREATE TABLE in a controlled schema and required USAGE rather than broad database ownership.

Explanation

Correct Answer

C:

Configure and enforce the supported authentication policy and MFA requirements for the relevant users. This directly addresses the described Snowflake condition: Security requires stronger authentication for privileged human users but the account relies only on passwords. The mechanism is: Authentication factors protect account entry and are distinct from SQL roles after sign-in. Verify success using: A privileged sign-in prompts for the required additional factor while noncompliant login fails.

Incorrect Answers

A:

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: Security requires stronger authentication for privileged human users but the account relies only on passwords.

B:

Configure the supported security integration with correct issuer, audience and role-scope mapping. That is suitable for a DIFFERENT Snowflake situation: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. It does not directly resolve the current requirement: Security requires stronger authentication for privileged human users but the account relies only on passwords.

D:

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: Security requires stronger authentication for privileged human users but the account relies only on passwords.

Question 106

A test plan evaluates: Security requires stronger authentication for privileged human users but the account relies only on passwords. Which evidence should be required before release?

  1. One app credential can be rotated and verified while other distinct integrations continue running.
  2. Authorized corporate connections succeed while an unapproved test source is rejected.
  3. The application creates its approved staging object while database ownership remains with governance.
  4. A privileged sign-in prompts for the required additional factor while noncompliant login fails.

Explanation

Correct Answer

D:

A privileged sign-in prompts for the required additional factor while noncompliant login fails. This validates the relevant action: Configure and enforce the supported authentication policy and MFA requirements for the relevant users. The underlying Snowflake behavior is: Authentication factors protect account entry and are distinct from SQL roles after sign-in.

Incorrect Answers

A:

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: Configure and enforce the supported authentication policy and MFA requirements for the relevant users.

B:

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: Configure and enforce the supported authentication policy and MFA requirements for the relevant users.

C:

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: Configure and enforce the supported authentication policy and MFA requirements for the relevant users.

Question 107

A Snowflake incident report notes: Security requires stronger authentication for privileged human users but the account relies only on passwords. What underlying mechanism explains the behavior?

  1. Authentication factors protect account entry and are distinct from SQL roles after sign-in.
  2. Strong perimeter policies can lock out operators without properly governed emergency procedures.
  3. Independent programmatic credentials make service identities revocable without broad shared-secret outages.
  4. Secure views reduce certain metadata exposure paths; they are not a substitute for all row and column controls.

Explanation

Correct Answer

A:

Authentication factors protect account entry and are distinct from SQL roles after sign-in. This explains the condition: Security requires stronger authentication for privileged human users but the account relies only on passwords. The corrective response is: Configure and enforce the supported authentication policy and MFA requirements for the relevant users.

Incorrect Answers

B:

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: Authentication factors protect account entry and are distinct from SQL roles after sign-in.

C:

Independent programmatic credentials make service identities revocable without broad shared-secret outages. That mechanism explains a DIFFERENT Snowflake problem: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. Here the relevant mechanism instead is: Authentication factors protect account entry and are distinct from SQL roles after sign-in.

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: Authentication factors protect account entry and are distinct from SQL roles after sign-in.

Question 108

A platform governance committee considers: Security requires stronger authentication for privileged human users but the account relies only on passwords. What preventive check should be standardized?

  1. Test naming changes in IdP and Snowflake before federation migrations.
  2. Test privileged account enrollment and recovery before enforcement rollout.
  3. Schedule credential expiration and parallel-cutover tests for programmatic access.
  4. Audit highly privileged roles and replace convenience grants with scoped functional roles.

Explanation

Correct Answer

B:

Test privileged account enrollment and recovery before enforcement rollout. This reduces recurrence of: Authentication factors protect account entry and are distinct from SQL roles after sign-in. The verification should demonstrate: A privileged sign-in prompts for the required additional factor while noncompliant login fails.

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: Authentication factors protect account entry and are distinct from SQL roles after sign-in.

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: Authentication factors protect account entry and are distinct from SQL roles after sign-in.

D:

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: Authentication factors protect account entry and are distinct from SQL roles after sign-in.

Question 109

An engineering team investigates the following Snowflake issue: A regional sales analyst can read rows for every country despite having permission only for their own region. Which configuration or processing decision is most appropriate?

  1. Use governed classification tags and appropriate policy associations to apply consistent protection at scale.
  2. Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.
  3. Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.
  4. Attach a row access policy using approved role/entitlement logic to filter visible records.

Explanation

Correct Answer

D:

Attach a row access policy using approved role/entitlement logic to filter visible records. This directly addresses the described Snowflake condition: A regional sales analyst can read rows for every country despite having permission only for their own region. The mechanism is: Row access policies restrict result rows dynamically as SQL is executed. Verify success using: Two test roles see only their permitted country rows while a governed admin test gets its required scope.

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 regional sales analyst can read rows for every country despite having permission only for their own region.

B:

Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression. That is suitable for a DIFFERENT Snowflake situation: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. It does not directly resolve the current requirement: A regional sales analyst can read rows for every country despite having permission only for their own region.

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: A regional sales analyst can read rows for every country despite having permission only for their own region.

Question 110

For a global logistics company, the original problem was: A regional sales analyst can read rows for every country despite having permission only for their own region. What observation confirms success?

  1. Two test roles see only their permitted country rows while a governed admin test gets its required scope.
  2. Newly tagged sensitive test columns inherit the intended masking behavior where supported.
  3. The affected identity cannot read the restricted view through any remaining authorized role chain.
  4. The report shows an explicit freshness indicator and reconciles delayed cost rows later.

Explanation

Correct Answer

A:

Two test roles see only their permitted country rows while a governed admin test gets its required scope. This validates the relevant action: Attach a row access policy using approved role/entitlement logic to filter visible records. The underlying Snowflake behavior is: Row access policies restrict result rows dynamically as SQL is executed.

Incorrect Answers

B:

Newly tagged sensitive test columns inherit the intended masking behavior where supported. This evidence tests a DIFFERENT situation: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. The correction required in this case is: Attach a row access policy using approved role/entitlement logic to filter visible records.

C:

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: Attach a row access policy using approved role/entitlement logic to filter visible records.

D:

The report shows an explicit freshness indicator and reconciles delayed cost rows later. This evidence tests a DIFFERENT situation: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. The correction required in this case is: Attach a row access policy using approved role/entitlement logic to filter visible records.