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 35

Question 340

During operational handoff for this problem: A company develops an internal Streamlit data app but assumes every user should automatically see the creator's entire warehouse data. Which guardrail should be included?

  1. Classify data and review function availability and charges before rollout.
  2. Evaluate retrieval accuracy and authorization on representative document sets.
  3. Review clone cleanup and change-driven storage growth rather than assuming free perpetual copies.
  4. Test Streamlit app roles and underlying queries before promoting it.

Explanation

Correct Answer

D:

Test Streamlit app roles and underlying queries before promoting it. This reduces recurrence of: Application presentation does not eliminate Snowflake authorization boundaries. The verification should demonstrate: A restricted test user sees the app's permitted data and cannot access unapproved sensitive tables.

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: Application presentation does not eliminate Snowflake authorization boundaries.

B:

Evaluate retrieval accuracy and authorization on representative document sets. That safeguard is aimed at ANOTHER risk: An AI team expects an enterprise search feature to be built by sorting all documents by their file names. It is less targeted than the control for: Application presentation does not eliminate Snowflake authorization boundaries.

C:

Review clone cleanup and change-driven storage growth rather than assuming free perpetual copies. That safeguard is aimed at ANOTHER risk: A developer clones a large table for integration testing and budgets for an immediate full physical data copy. It is less targeted than the control for: Application presentation does not eliminate Snowflake authorization boundaries.

Question 341

A data-platform team must resolve: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. Which technical change most directly solves it?

  1. Grant appropriate USAGE on the designated execution warehouse as well as the required source and destination rights.
  2. Separate user/role provisioning from data-object privileges and use scoped roles for table access.
  3. Create and assign a least-privilege reporting role with scoped container usage and table select rights.
  4. Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.

Explanation

Correct Answer

B:

Separate user/role provisioning from data-object privileges and use scoped roles for table access. This directly addresses the described Snowflake condition: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. The mechanism is: Snowflake system administration responsibilities and data access are distinct privilege domains. Verify success using: A test administrator can manage authorized identities but cannot read restricted data without separate grants.

Incorrect Answers

A:

Grant appropriate USAGE on the designated execution warehouse as well as the required source and destination rights. That is suitable for a DIFFERENT Snowflake situation: An app deploys with a role that has INSERT but no warehouse usage, causing its insert-select query to fail. It does not directly resolve the current requirement: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts.

C:

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 pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts.

D:

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 pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts.

Question 342

A Snowflake acceptance test follows this incident: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. What evidence most directly proves the correction?

  1. The analyst can read approved reports without gaining account-wide administrative powers.
  2. The consumer can read the created view without gaining access to base tables beyond design intent.
  3. A test administrator can manage authorized identities but cannot read restricted data without separate grants.
  4. A network trace uses the intended private endpoint while public access remains subject to documented policy.

Explanation

Correct Answer

C:

A test administrator can manage authorized identities but cannot read restricted data without separate grants. This validates the relevant action: Separate user/role provisioning from data-object privileges and use scoped roles for table access. The underlying Snowflake behavior is: Snowflake system administration responsibilities and data access are distinct privilege domains.

Incorrect Answers

A:

The analyst can read approved reports without gaining account-wide administrative powers. This evidence tests a DIFFERENT situation: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. The correction required in this case is: Separate user/role provisioning from data-object privileges and use scoped roles for table access.

B:

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: Separate user/role provisioning from data-object privileges and use scoped roles for table access.

D:

A network trace uses the intended private endpoint while public access remains subject to documented policy. This evidence tests a DIFFERENT situation: A company wants external clients to reach Snowflake without traversing public Internet but plans only a network allowlist. The correction required in this case is: Separate user/role provisioning from data-object privileges and use scoped roles for table access.

Question 343

The data-platform team observes: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. Which architectural or processing fact matters most?

  1. Shared credentials undermine per-application attribution and least-privilege offboarding.
  2. Account-wide administration is broader than the role privileges needed for read-only analysis.
  3. Repeated updates can create retained micro-partition versions billed during recovery windows.
  4. Snowflake system administration responsibilities and data access are distinct privilege domains.

Explanation

Correct Answer

D:

Snowflake system administration responsibilities and data access are distinct privilege domains. This explains the condition: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. The corrective response is: Separate user/role provisioning from data-object privileges and use scoped roles for table access.

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: Snowflake system administration responsibilities and data access are distinct privilege domains.

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 system administration responsibilities and data access are distinct privilege domains.

C:

Repeated updates can create retained micro-partition versions billed during recovery windows. That mechanism explains a DIFFERENT Snowflake problem: A department thinks all storage cost comes from active table bytes and ignores historical retained data from updates. Here the relevant mechanism instead is: Snowflake system administration responsibilities and data access are distinct privilege domains.

Question 344

For a regulated healthcare organization, this issue must not recur: A pipeline owner assigns the USERADMIN system role broad table privileges because it manages user accounts. Which review control fits best?

  1. Review system roles' responsibilities before using them as generic data superusers.
  2. Review service roles for accidental object ownership escalation.
  3. Test service integrations with real connection parameters, not only interactive worksheets.
  4. Document audit view latency, retention and roles needed to query access history.

Explanation

Correct Answer

A:

Review system roles' responsibilities before using them as generic data superusers. This reduces recurrence of: Snowflake system administration responsibilities and data access are distinct privilege domains. The verification should demonstrate: A test administrator can manage authorized identities but cannot read restricted data without separate grants.

Incorrect Answers

B:

Review service roles for accidental object ownership escalation. That safeguard is aimed at ANOTHER risk: An engineer gives an application OWNERSHIP on a production database merely to create one staging table. It is less targeted than the control for: Snowflake system administration responsibilities and data access are distinct privilege domains.

C:

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: Snowflake system administration responsibilities and data access are distinct privilege domains.

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: Snowflake system administration responsibilities and data access are distinct privilege domains.

Question 345

In a governed Snowflake environment, the reported condition is: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. What should be implemented first?

  1. Evaluate approved cloud private connectivity such as PrivateLink or equivalent supported private endpoint integration.
  2. Configure and enforce the supported authentication policy and MFA requirements for the relevant users.
  3. Configure the supported security integration with correct issuer, audience and role-scope mapping.
  4. Review the external access and function privileges and apply appropriate data policies and outbound restrictions.

Explanation

Correct Answer

C:

Configure the supported security integration with correct issuer, audience and role-scope mapping. This directly addresses the described Snowflake condition: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. The mechanism is: OAuth trust requires verifying token issuer, audience and supported authorization scope. Verify success using: A valid test token for the approved audience succeeds while a mismatched token fails.

Incorrect Answers

A:

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 enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations.

B:

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: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations.

D:

Review the external access and function privileges and apply appropriate data policies and outbound restrictions. That is suitable for a DIFFERENT Snowflake situation: An analyst creates an external function that exports restricted data even though its normal table queries are masked. It does not directly resolve the current requirement: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations.

Question 346

A test plan evaluates: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. 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. Session inspection shows the correct active primary role and authorized query behavior.
  4. A valid test token for the approved audience succeeds while a mismatched token fails.

Explanation

Correct Answer

D:

A valid test token for the approved audience succeeds while a mismatched token fails. This validates the relevant action: Configure the supported security integration with correct issuer, audience and role-scope mapping. The underlying Snowflake behavior is: OAuth trust requires verifying token issuer, audience and supported authorization scope.

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 the supported security integration with correct issuer, audience and role-scope mapping.

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 the supported security integration with correct issuer, audience and role-scope mapping.

C:

Session inspection shows the correct active primary role and authorized query behavior. This evidence tests a DIFFERENT situation: A user receives a new secondary role but an integration still acts under the wrong primary role in a JDBC session. The correction required in this case is: Configure the supported security integration with correct issuer, audience and role-scope mapping.

Question 347

A Snowflake incident report notes: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. What underlying mechanism explains the behavior?

  1. OAuth trust requires verifying token issuer, audience and supported authorization scope.
  2. IP allowlisting and private network attachment solve different transport security requirements.
  3. Federated authentication requires a consistent identity mapping independently of database grants.
  4. Data-governance policy must account for execution and external integration boundaries, not only UI views.

Explanation

Correct Answer

A:

OAuth trust requires verifying token issuer, audience and supported authorization scope. This explains the condition: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. The corrective response is: Configure the supported security integration with correct issuer, audience and role-scope mapping.

Incorrect Answers

B:

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: OAuth trust requires verifying token issuer, audience and supported authorization scope.

C:

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: OAuth trust requires verifying token issuer, audience and supported authorization scope.

D:

Data-governance policy must account for execution and external integration boundaries, not only UI views. That mechanism explains a DIFFERENT Snowflake problem: An analyst creates an external function that exports restricted data even though its normal table queries are masked. Here the relevant mechanism instead is: OAuth trust requires verifying token issuer, audience and supported authorization scope.

Question 348

A platform governance committee considers: An account enables external OAuth for an app but accepts tokens with the wrong audience and scope expectations. What preventive check should be standardized?

  1. Maintain approved egress IP ranges and test exceptions after network changes.
  2. Review integration trust endpoints and claim mappings after IdP updates.
  3. Validate private DNS and endpoint routing across failover conditions.
  4. Review view security properties before sharing sensitive transformation logic.

Explanation

Correct Answer

B:

Review integration trust endpoints and claim mappings after IdP updates. This reduces recurrence of: OAuth trust requires verifying token issuer, audience and supported authorization scope. The verification should demonstrate: A valid test token for the approved audience succeeds while a mismatched token fails.

Incorrect Answers

A:

Maintain approved egress IP ranges and test exceptions after network changes. That safeguard is aimed at ANOTHER risk: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. It is less targeted than the control for: OAuth trust requires verifying token issuer, audience and supported authorization scope.

C:

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: OAuth trust requires verifying token issuer, audience and supported authorization scope.

D:

Review view security properties before sharing sensitive transformation logic. That safeguard is aimed at ANOTHER risk: A contractor is granted a secure view but its definition reveals an underlying protected calculation when copied into an ordinary view. It is less targeted than the control for: OAuth trust requires verifying token issuer, audience and supported authorization scope.

Question 349

An engineering team investigates the following Snowflake issue: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. Which configuration or processing decision is most appropriate?

  1. Choose supported secure view semantics where definition exposure and optimization trade-offs are material.
  2. Review the external access and function privileges and apply appropriate data policies and outbound restrictions.
  3. Separate user/role provisioning from data-object privileges and use scoped roles for table access.
  4. Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.

Explanation

Correct Answer

D:

Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns. This directly addresses the described Snowflake condition: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. The mechanism is: Least privilege is enforced at object and policy boundaries, not by naming tables as sensitive. Verify success using: The consumer role queries its approved interface but cannot read the raw customer table directly.

Incorrect Answers

A:

Choose supported secure view semantics where definition exposure and optimization trade-offs are material. That is suitable for a DIFFERENT Snowflake situation: A contractor is granted a secure view but its definition reveals an underlying protected calculation when copied into an ordinary view. It does not directly resolve the current requirement: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view.

B:

Review the external access and function privileges and apply appropriate data policies and outbound restrictions. That is suitable for a DIFFERENT Snowflake situation: An analyst creates an external function that exports restricted data even though its normal table queries are masked. It does not directly resolve the current requirement: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view.

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 security review finds a shared role with direct access to raw customer names even though applications need only a masked view.

Question 350

For a global logistics company, the original problem was: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. What observation confirms success?

  1. The consumer role queries its approved interface but cannot read the raw customer table directly.
  2. The affected identity cannot read the restricted view through any remaining authorized role chain.
  3. Two test roles see only their permitted country rows while a governed admin test gets its required scope.
  4. Authorized corporate connections succeed while an unapproved test source is rejected.

Explanation

Correct Answer

A:

The consumer role queries its approved interface but cannot read the raw customer table directly. This validates the relevant action: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns. The underlying Snowflake behavior is: Least privilege is enforced at object and policy boundaries, not by naming tables as sensitive.

Incorrect Answers

B:

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: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.

C:

Two test roles see only their permitted country rows while a governed admin test gets its required scope. This evidence tests a DIFFERENT situation: A regional sales analyst can read rows for every country despite having permission only for their own region. The correction required in this case is: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.

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: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.