Pass Snowflake SnowPro Core Exam in First Attempt Easily
Real Snowflake SnowPro Core Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts
3 products

You save $69.98

SnowPro Core Premium Bundle

  • Premium File 703 Questions & Answers
  • Last Update: Nov 22, 2026
  • Training Course 92 Lectures
  • Study Guide 413 Pages
$79.99 $149.97

Purchase Individually

  • Premium File

    703 Questions & Answers
    Last Update: Nov 22, 2026

    $76.99
    $69.99
  • Training Course

    92 Lectures

    $43.99
    $39.99
  • Study Guide

    413 Pages

    $43.99
    $39.99

SnowPro Core Practice Test 22

Question 210

The Snowflake implementation fails its pilot test. A web analytics service needs scoped delegated access without handling employees' primary passwords. Which evidence should be inspected first to isolate the likely cause?

  1. Inspect SHOW DATABASE ROLES, database grants and role inheritance results.
  2. Inspect the role hierarchy, granted roles and an impersonated access test.
  3. Inspect security integration, token scopes, current role and failed unauthorized requests.
  4. Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds.

Explanation

Correct Answer

C:

Inspect security integration, token scopes, current role and failed unauthorized requests. These checks diagnose OAuth delegated application tokens. Correct response: Configure supported OAuth security integration and application role mapping with carefully scoped tokens. Expected observation: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.

Incorrect Answers

A:

Inspect SHOW DATABASE ROLES, database grants and role inheritance results. Those checks would investigate Database role boundaries, not the current OAuth delegated application tokens failure. The targeted diagnostic here is: Inspect security integration, token scopes, current role and failed unauthorized requests.

B:

Inspect the role hierarchy, granted roles and an impersonated access test. Those checks would investigate Role hierarchy inheritance, not the current OAuth delegated application tokens failure. The targeted diagnostic here is: Inspect security integration, token scopes, current role and failed unauthorized requests.

D:

Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current OAuth delegated application tokens failure. The targeted diagnostic here is: Inspect security integration, token scopes, current role and failed unauthorized requests.

Question 211

A Snowflake implementation team encounters this specific requirement: Support engineers can troubleshoot transactions but should see redacted account numbers unless specifically approved. Which action best addresses it?

  1. Attach a correctly configured resource monitor and threshold actions to supported warehouse resources.
  2. Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority.
  3. Evaluate Snowflake Trust Center capabilities and investigate actionable findings with their relevant owners.
  4. Attach a context-aware masking policy to the sensitive column using supported role conditions.

Explanation

Correct Answer

D:

Attach a context-aware masking policy to the sensitive column using supported role conditions. This resolves Dynamic column masking. Underlying reason: Masking policies transform or restrict column values at query time according to policy context. Verify with: An ordinary role sees masked values and an approved role sees permitted clear data. Boundary: Masking policy selection and governance privileges are separate from the table's reader grants.

Incorrect Answers

A:

Attach a correctly configured resource monitor and threshold actions to supported warehouse resources. That is suitable for a different requirement, Resource monitor credit threshold, with this separate condition: An ad hoc warehouse consumes far more credits than allocated and the team wants an automated spending guardrail.

B:

Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority. That is suitable for a different requirement, Managed access schema grants, with this separate condition: Object creators in a finance schema grant confidential views to other teams without central review.

C:

Evaluate Snowflake Trust Center capabilities and investigate actionable findings with their relevant owners. That is suitable for a different requirement, Trust Center security posture findings, with this separate condition: A security review needs continuous account posture checks rather than a one-time spreadsheet of recommended settings.

Question 212

After implementing a Snowflake control, the reviewer must prove the business requirement was met. Support engineers can troubleshoot transactions but should see redacted account numbers unless specifically approved. Which result is the most direct acceptance evidence?

  1. A test user signs in through the approved IdP and receives the intended Snowflake identity.
  2. A newly created eligible table becomes readable under the approved role without manual repeat grants.
  3. An ordinary role sees masked values and an approved role sees permitted clear data.
  4. The incident timeline separately identifies authentication and subsequent object-access events.

Explanation

Correct Answer

C:

An ordinary role sees masked values and an approved role sees permitted clear data. This directly demonstrates success for Dynamic column masking. Implementation: Attach a context-aware masking policy to the sensitive column using supported role conditions. Mechanism: Masking policies transform or restrict column values at query time according to policy context.

Incorrect Answers

A:

A test user signs in through the approved IdP and receives the intended Snowflake identity. This outcome is evidence for the separate Federated SSO with corporate identity case, not the described Dynamic column masking requirement. For the current context, verify: An ordinary role sees masked values and an approved role sees permitted clear data.

B:

A newly created eligible table becomes readable under the approved role without manual repeat grants. This outcome is evidence for the separate Future grants for new tables case, not the described Dynamic column masking requirement. For the current context, verify: An ordinary role sees masked values and an approved role sees permitted clear data.

D:

The incident timeline separately identifies authentication and subsequent object-access events. This outcome is evidence for the separate Login history versus access history case, not the described Dynamic column masking requirement. For the current context, verify: An ordinary role sees masked values and an approved role sees permitted clear data.

Question 213

A Snowflake specialist explains why a proposed design works. Support engineers can troubleshoot transactions but should see redacted account numbers unless specifically approved. Which technical principle is most relevant?

  1. Query tags attach contextual metadata to statements without automatically changing execution behavior.
  2. Masking policies transform or restrict column values at query time according to policy context.
  3. Roles may inherit privileges of roles granted to them, providing reusable RBAC composition.
  4. A managed security posture capability can identify configuration concerns beyond individual queries.

Explanation

Correct Answer

B:

Masking policies transform or restrict column values at query time according to policy context. This explains Dynamic column masking. Correct implementation: Attach a context-aware masking policy to the sensitive column using supported role conditions. Acceptance evidence: An ordinary role sees masked values and an approved role sees permitted clear data.

Incorrect Answers

A:

Query tags attach contextual metadata to statements without automatically changing execution behavior. This mechanism concerns Query tagging for audit trail. The mechanism specific to Dynamic column masking is: Masking policies transform or restrict column values at query time according to policy context.

C:

Roles may inherit privileges of roles granted to them, providing reusable RBAC composition. This mechanism concerns Role hierarchy inheritance. The mechanism specific to Dynamic column masking is: Masking policies transform or restrict column values at query time according to policy context.

D:

A managed security posture capability can identify configuration concerns beyond individual queries. This mechanism concerns Trust Center security posture findings. The mechanism specific to Dynamic column masking is: Masking policies transform or restrict column values at query time according to policy context.

Question 214

The project leaves the described Snowflake requirement unresolved. Support engineers can troubleshoot transactions but should see redacted account numbers unless specifically approved. Which consequence is most directly related?

  1. A successful login record alone does not prove a sensitive table was queried.
  2. Granting table SELECT without column protection can disclose sensitive financial identifiers.
  3. Unmanaged object grants can circumvent governance expectations even with correct tables.
  4. Duplicating grants on every team role produces entitlement drift and difficult revocation.

Explanation

Correct Answer

B:

Granting table SELECT without column protection can disclose sensitive financial identifiers. This is the direct exposure if Dynamic column masking is not handled. Recommended protection: Attach a context-aware masking policy to the sensitive column using supported role conditions. Validate by: An ordinary role sees masked values and an approved role sees permitted clear data.

Incorrect Answers

A:

A successful login record alone does not prove a sensitive table was queried. This is an exposure in a separate Login history versus access history scenario. The direct failure for Dynamic column masking is: Granting table SELECT without column protection can disclose sensitive financial identifiers.

C:

Unmanaged object grants can circumvent governance expectations even with correct tables. This is an exposure in a separate Managed access schema grants scenario. The direct failure for Dynamic column masking is: Granting table SELECT without column protection can disclose sensitive financial identifiers.

D:

Duplicating grants on every team role produces entitlement drift and difficult revocation. This is an exposure in a separate Role hierarchy inheritance scenario. The direct failure for Dynamic column masking is: Granting table SELECT without column protection can disclose sensitive financial identifiers.

Question 215

The Snowflake implementation fails its pilot test. Support engineers can troubleshoot transactions but should see redacted account numbers unless specifically approved. Which evidence should be inspected first to isolate the likely cause?

  1. Inspect masking policy definition, column bindings, role evaluation and test queries.
  2. Inspect the role hierarchy, granted roles and an impersonated access test.
  3. Inspect policy attachment, allowed and blocked rules, login history and effective client IP.
  4. Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds.

Explanation

Correct Answer

A:

Inspect masking policy definition, column bindings, role evaluation and test queries. These checks diagnose Dynamic column masking. Correct response: Attach a context-aware masking policy to the sensitive column using supported role conditions. Expected observation: An ordinary role sees masked values and an approved role sees permitted clear data.

Incorrect Answers

B:

Inspect the role hierarchy, granted roles and an impersonated access test. Those checks would investigate Role hierarchy inheritance, not the current Dynamic column masking failure. The targeted diagnostic here is: Inspect masking policy definition, column bindings, role evaluation and test queries.

C:

Inspect policy attachment, allowed and blocked rules, login history and effective client IP. Those checks would investigate Network policy for trusted admin paths, not the current Dynamic column masking failure. The targeted diagnostic here is: Inspect masking policy definition, column bindings, role evaluation and test queries.

D:

Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current Dynamic column masking failure. The targeted diagnostic here is: Inspect masking policy definition, column bindings, role evaluation and test queries.

Question 216

A Snowflake implementation team encounters this specific requirement: Managers in EMEA must see only EMEA customer records from a shared sales table even though all use the same dashboard. Which action best addresses it?

  1. Attach a correctly configured resource monitor and threshold actions to supported warehouse resources.
  2. Grant the reader role to the reporting role following the approved account role hierarchy.
  3. Transfer OWNERSHIP through the supported grant process with a deliberate plan for dependent privileges.
  4. Attach an authorized row access policy using region and role-to-region mapping.

Explanation

Correct Answer

D:

Attach an authorized row access policy using region and role-to-region mapping. This resolves Row-level regional access. Underlying reason: Row access policies filter visible rows based on policy logic and evaluation context. Verify with: EMEA and Americas test roles receive only their intended regions from the same SELECT. Boundary: Row access policies control query visibility rather than blocking every possible INSERT.

Incorrect Answers

A:

Attach a correctly configured resource monitor and threshold actions to supported warehouse resources. That is suitable for a different requirement, Resource monitor credit threshold, with this separate condition: An ad hoc warehouse consumes far more credits than allocated and the team wants an automated spending guardrail.

B:

Grant the reader role to the reporting role following the approved account role hierarchy. That is suitable for a different requirement, Role hierarchy inheritance, with this separate condition: A reporting role should inherit a narrow reader role but currently needs every SELECT privilege granted repeatedly.

C:

Transfer OWNERSHIP through the supported grant process with a deliberate plan for dependent privileges. That is suitable for a different requirement, Object ownership transfer, with this separate condition: A departed engineer's role owns production tables and a new maintenance role cannot perform approved ALTER operations.

Question 217

After implementing a Snowflake control, the reviewer must prove the business requirement was met. Managers in EMEA must see only EMEA customer records from a shared sales table even though all use the same dashboard. Which result is the most direct acceptance evidence?

  1. A test user signs in through the approved IdP and receives the intended Snowflake identity.
  2. The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.
  3. EMEA and Americas test roles receive only their intended regions from the same SELECT.
  4. Individual object creators cannot independently regrant protected objects in that managed schema.

Explanation

Correct Answer

C:

EMEA and Americas test roles receive only their intended regions from the same SELECT. This directly demonstrates success for Row-level regional access. Implementation: Attach an authorized row access policy using region and role-to-region mapping. Mechanism: Row access policies filter visible rows based on policy logic and evaluation context.

Incorrect Answers

A:

A test user signs in through the approved IdP and receives the intended Snowflake identity. This outcome is evidence for the separate Federated SSO with corporate identity case, not the described Row-level regional access requirement. For the current context, verify: EMEA and Americas test roles receive only their intended regions from the same SELECT.

B:

The app receives access for authorized scopes and unauthorized Snowflake objects remain protected. This outcome is evidence for the separate OAuth delegated application tokens case, not the described Row-level regional access requirement. For the current context, verify: EMEA and Americas test roles receive only their intended regions from the same SELECT.

D:

Individual object creators cannot independently regrant protected objects in that managed schema. This outcome is evidence for the separate Managed access schema grants case, not the described Row-level regional access requirement. For the current context, verify: EMEA and Americas test roles receive only their intended regions from the same SELECT.

Question 218

A Snowflake specialist explains why a proposed design works. Managers in EMEA must see only EMEA customer records from a shared sales table even though all use the same dashboard. Which technical principle is most relevant?

  1. Snowflake access checks applicable privileges on the object and its containing namespaces.
  2. Managed access schemas centralize privilege-grant authority separately from object ownership.
  3. Row access policies filter visible rows based on policy logic and evaluation context.
  4. OWNERSHIP governs object control independently of ordinary SELECT or INSERT privileges.

Explanation

Correct Answer

C:

Row access policies filter visible rows based on policy logic and evaluation context. This explains Row-level regional access. Correct implementation: Attach an authorized row access policy using region and role-to-region mapping. Acceptance evidence: EMEA and Americas test roles receive only their intended regions from the same SELECT.

Incorrect Answers

A:

Snowflake access checks applicable privileges on the object and its containing namespaces. This mechanism concerns Least privilege with role grants. The mechanism specific to Row-level regional access is: Row access policies filter visible rows based on policy logic and evaluation context.

B:

Managed access schemas centralize privilege-grant authority separately from object ownership. This mechanism concerns Managed access schema grants. The mechanism specific to Row-level regional access is: Row access policies filter visible rows based on policy logic and evaluation context.

D:

OWNERSHIP governs object control independently of ordinary SELECT or INSERT privileges. This mechanism concerns Object ownership transfer. The mechanism specific to Row-level regional access is: Row access policies filter visible rows based on policy logic and evaluation context.

Question 219

The project leaves the described Snowflake requirement unresolved. Managers in EMEA must see only EMEA customer records from a shared sales table even though all use the same dashboard. Which consequence is most directly related?

  1. Separate dashboards alone do not prevent ad hoc SQL from reading other regions.
  2. A successful login record alone does not prove a sensitive table was queried.
  3. Assigning ACCOUNTADMIN to bypass a missing USAGE grant unnecessarily broadens control.
  4. Unmanaged object grants can circumvent governance expectations even with correct tables.

Explanation

Correct Answer

A:

Separate dashboards alone do not prevent ad hoc SQL from reading other regions. This is the direct exposure if Row-level regional access is not handled. Recommended protection: Attach an authorized row access policy using region and role-to-region mapping. Validate by: EMEA and Americas test roles receive only their intended regions from the same SELECT.

Incorrect Answers

B:

A successful login record alone does not prove a sensitive table was queried. This is an exposure in a separate Login history versus access history scenario. The direct failure for Row-level regional access is: Separate dashboards alone do not prevent ad hoc SQL from reading other regions.

C:

Assigning ACCOUNTADMIN to bypass a missing USAGE grant unnecessarily broadens control. This is an exposure in a separate Least privilege with role grants scenario. The direct failure for Row-level regional access is: Separate dashboards alone do not prevent ad hoc SQL from reading other regions.

D:

Unmanaged object grants can circumvent governance expectations even with correct tables. This is an exposure in a separate Managed access schema grants scenario. The direct failure for Row-level regional access is: Separate dashboards alone do not prevent ad hoc SQL from reading other regions.

Question 220

The Snowflake implementation fails its pilot test. Managers in EMEA must see only EMEA customer records from a shared sales table even though all use the same dashboard. Which evidence should be inspected first to isolate the likely cause?

  1. Inspect policy signature, mapping table, CURRENT_ROLE logic and test role results.
  2. Inspect SHOW DATABASE ROLES, database grants and role inheritance results.
  3. Inspect security integration, token scopes, current role and failed unauthorized requests.
  4. Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds.

Explanation

Correct Answer

A:

Inspect policy signature, mapping table, CURRENT_ROLE logic and test role results. These checks diagnose Row-level regional access. Correct response: Attach an authorized row access policy using region and role-to-region mapping. Expected observation: EMEA and Americas test roles receive only their intended regions from the same SELECT.

Incorrect Answers

B:

Inspect SHOW DATABASE ROLES, database grants and role inheritance results. Those checks would investigate Database role boundaries, not the current Row-level regional access failure. The targeted diagnostic here is: Inspect policy signature, mapping table, CURRENT_ROLE logic and test role results.

C:

Inspect security integration, token scopes, current role and failed unauthorized requests. Those checks would investigate OAuth delegated application tokens, not the current Row-level regional access failure. The targeted diagnostic here is: Inspect policy signature, mapping table, CURRENT_ROLE logic and test role results.

D:

Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current Row-level regional access failure. The targeted diagnostic here is: Inspect policy signature, mapping table, CURRENT_ROLE logic and test role results.

SnowPro Core Practice Tests

Purchase Individually

  • Premium File

    703 Questions & Answers
    Last Update: Nov 22, 2026

    $76.99
    $69.99
  • Training Course

    92 Lectures

    $43.99
    $39.99
  • Study Guide

    413 Pages

    $43.99
    $39.99

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports