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 27

Question 260

During operational handoff for this problem: An application stores vector embeddings but a developer expects standard string comparison to rank semantic similarity automatically. Which guardrail should be included?

  1. Review feature reproducibility and data lineage across training runs.
  2. Pin availability checks to target regions in AI application deployment reviews.
  3. Review actual pruning evidence instead of imposing inherited file-partition assumptions.
  4. Record vector dimensions, embedding model and evaluation methodology.

Explanation

Correct Answer

D:

Record vector dimensions, embedding model and evaluation methodology. This reduces recurrence of: Vector similarity is numerical and model-dependent rather than lexicographic string comparison. The verification should demonstrate: A controlled nearest-neighbor example orders relevant embedding vectors by the intended similarity measure.

Incorrect Answers

A:

Review feature reproducibility and data lineage across training runs. That safeguard is aimed at ANOTHER risk: A retailer builds an ML feature pipeline by copying full source datasets to laptops every day. It is less targeted than the control for: Vector similarity is numerical and model-dependent rather than lexicographic string comparison.

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: Vector similarity is numerical and model-dependent rather than lexicographic string comparison.

C:

Review actual pruning evidence instead of imposing inherited file-partition assumptions. That safeguard is aimed at ANOTHER risk: A table is manually partitioned into separate daily physical files to achieve traditional partition maintenance in regular Snowflake tables. It is less targeted than the control for: Vector similarity is numerical and model-dependent rather than lexicographic string comparison.

Question 261

A data-platform team must resolve: A project grants future objects manually each week and a newly created table is invisible to its application role. Which technical change most directly solves it?

  1. Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.
  2. Define appropriate future grants in the intended database or schema and verify ownership/grant policies.
  3. Review the intended role hierarchy and verify inheritance upward through granted roles.
  4. Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses.

Explanation

Correct Answer

B:

Define appropriate future grants in the intended database or schema and verify ownership/grant policies. This directly addresses the described Snowflake condition: A project grants future objects manually each week and a newly created table is invisible to its application role. The mechanism is: Future grants automate access for future objects in a defined scope, subject to supported precedence. Verify success using: A newly created permitted table receives the expected privileges without per-table emergency grants.

Incorrect Answers

A:

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 project grants future objects manually each week and a newly created table is invisible to its application role.

C:

Review the intended role hierarchy and verify inheritance upward through granted roles. That is suitable for a DIFFERENT Snowflake situation: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. It does not directly resolve the current requirement: A project grants future objects manually each week and a newly created table is invisible to its application role.

D:

Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses. That is suitable for a DIFFERENT Snowflake situation: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. It does not directly resolve the current requirement: A project grants future objects manually each week and a newly created table is invisible to its application role.

Question 262

A Snowflake acceptance test follows this incident: A project grants future objects manually each week and a newly created table is invisible to its application role. 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 analyst can read approved reports without gaining account-wide administrative powers.
  3. A newly created permitted table receives the expected privileges without per-table emergency grants.
  4. The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds.

Explanation

Correct Answer

C:

A newly created permitted table receives the expected privileges without per-table emergency grants. This validates the relevant action: Define appropriate future grants in the intended database or schema and verify ownership/grant policies. The underlying Snowflake behavior is: Future grants automate access for future objects in a defined scope, subject to supported precedence.

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: Define appropriate future grants in the intended database or schema and verify ownership/grant policies.

B:

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: Define appropriate future grants in the intended database or schema and verify ownership/grant policies.

D:

The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds. This evidence tests a DIFFERENT situation: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. The correction required in this case is: Define appropriate future grants in the intended database or schema and verify ownership/grant policies.

Question 263

The data-platform team observes: A project grants future objects manually each week and a newly created table is invisible to its application role. Which architectural or processing fact matters most?

  1. Effective SQL authorization depends on the session's active role context and configured secondary roles.
  2. Shared credentials undermine per-application attribution and least-privilege offboarding.
  3. Independent programmatic credentials make service identities revocable without broad shared-secret outages.
  4. Future grants automate access for future objects in a defined scope, subject to supported precedence.

Explanation

Correct Answer

D:

Future grants automate access for future objects in a defined scope, subject to supported precedence. This explains the condition: A project grants future objects manually each week and a newly created table is invisible to its application role. The corrective response is: Define appropriate future grants in the intended database or schema and verify ownership/grant policies.

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: Future grants automate access for future objects in a defined scope, subject to supported precedence.

B:

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: Future grants automate access for future objects in a defined scope, subject to supported precedence.

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: Future grants automate access for future objects in a defined scope, subject to supported precedence.

Question 264

For a university data platform, this issue must not recur: A project grants future objects manually each week and a newly created table is invisible to its application role. Which review control fits best?

  1. Periodically verify new-object privilege behavior and future-grant overlap.
  2. Check container and object grants together when diagnosing access failures.
  3. Inventory service-user ownership and rotate credentials with controlled revocation tests.
  4. Schedule credential expiration and parallel-cutover tests for programmatic access.

Explanation

Correct Answer

A:

Periodically verify new-object privilege behavior and future-grant overlap. This reduces recurrence of: Future grants automate access for future objects in a defined scope, subject to supported precedence. The verification should demonstrate: A newly created permitted table receives the expected privileges without per-table emergency grants.

Incorrect Answers

B:

Check container and object grants together when diagnosing access failures. That safeguard is aimed at ANOTHER risk: A BI role has SELECT on a fact table but receives a schema authorization error during query compilation. It is less targeted than the control for: Future grants automate access for future objects in a defined scope, subject to supported precedence.

C:

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: Future grants automate access for future objects in a defined scope, subject to supported precedence.

D:

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: Future grants automate access for future objects in a defined scope, subject to supported precedence.

Question 265

In a governed Snowflake environment, the reported condition is: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. 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. Review supported SSO federation settings and login-name/user mapping for the chosen identity provider.
  4. Use distinct service identities with appropriately supported authentication and scoped roles for each integration.

Explanation

Correct Answer

C:

Review supported SSO federation settings and login-name/user mapping for the chosen identity provider. This directly addresses the described Snowflake condition: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. The mechanism is: Federated authentication requires a consistent identity mapping independently of database grants. Verify success using: A controlled SSO login resolves to the correct Snowflake user and role context.

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 user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user.

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 user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user.

D:

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 user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user.

Question 266

A test plan evaluates: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. Which evidence should be required before release?

  1. An incident drill confirms required emergency recovery without opening uncontrolled public login.
  2. One app credential can be rotated and verified while other distinct integrations continue running.
  3. The cost report includes the task's serverless consumption even when the old warehouse is idle.
  4. A controlled SSO login resolves to the correct Snowflake user and role context.

Explanation

Correct Answer

D:

A controlled SSO login resolves to the correct Snowflake user and role context. This validates the relevant action: Review supported SSO federation settings and login-name/user mapping for the chosen identity provider. The underlying Snowflake behavior is: Federated authentication requires a consistent identity mapping independently of database grants.

Incorrect Answers

A:

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: Review supported SSO federation settings and login-name/user mapping for the chosen identity provider.

B:

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: Review supported SSO federation settings and login-name/user mapping for the chosen identity provider.

C:

The cost report includes the task's serverless consumption even when the old warehouse is idle. This evidence tests a DIFFERENT situation: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. The correction required in this case is: Review supported SSO federation settings and login-name/user mapping for the chosen identity provider.

Question 267

A Snowflake incident report notes: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. What underlying mechanism explains the behavior?

  1. Federated authentication requires a consistent identity mapping independently of database grants.
  2. Authentication factors protect account entry and are distinct from SQL roles after sign-in.
  3. Independent programmatic credentials make service identities revocable without broad shared-secret outages.
  4. Warehouse suspension does not delete persisted data or eliminate unrelated storage charges.

Explanation

Correct Answer

A:

Federated authentication requires a consistent identity mapping independently of database grants. This explains the condition: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. The corrective response is: Review supported SSO federation settings and login-name/user mapping for the chosen identity provider.

Incorrect Answers

B:

Authentication factors protect account entry and are distinct from SQL roles after sign-in. That mechanism explains a DIFFERENT Snowflake problem: Security requires stronger authentication for privileged human users but the account relies only on passwords. Here the relevant mechanism instead is: Federated authentication requires a consistent identity mapping independently of database grants.

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: Federated authentication requires a consistent identity mapping independently of database grants.

D:

Warehouse suspension does not delete persisted data or eliminate unrelated storage charges. That mechanism explains a DIFFERENT Snowflake problem: A team thinks suspending a warehouse eliminates storage and file-stage charges for inactive datasets. Here the relevant mechanism instead is: Federated authentication requires a consistent identity mapping independently of database grants.

Question 268

A platform governance committee considers: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. What preventive check should be standardized?

  1. Schedule credential expiration and parallel-cutover tests for programmatic access.
  2. Test naming changes in IdP and Snowflake before federation migrations.
  3. Exercise break-glass access and log each use after authentication policy changes.
  4. Label telemetry recency and use validated time windows in chargeback reports.

Explanation

Correct Answer

B:

Test naming changes in IdP and Snowflake before federation migrations. This reduces recurrence of: Federated authentication requires a consistent identity mapping independently of database grants. The verification should demonstrate: A controlled SSO login resolves to the correct Snowflake user and role context.

Incorrect Answers

A:

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: Federated authentication requires a consistent identity mapping independently of database grants.

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: Federated authentication requires a consistent identity mapping independently of database grants.

D:

Label telemetry recency and use validated time windows in chargeback reports. That safeguard is aimed at ANOTHER risk: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. It is less targeted than the control for: Federated authentication requires a consistent identity mapping independently of database grants.

Question 269

An engineering team investigates the following Snowflake issue: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. Which configuration or processing decision is most appropriate?

  1. Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.
  2. Layer account authentication, scoped role privileges, row filtering and column masking according to threat model.
  3. Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.
  4. Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.

Explanation

Correct Answer

D:

Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag. This directly addresses the described Snowflake condition: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. The mechanism is: Usage, access history and cost metering contain different evidence about data access. Verify success using: The audit identifies query principals and accessed objects for representative governed tests.

Incorrect Answers

A:

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 data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts.

B:

Layer account authentication, scoped role privileges, row filtering and column masking according to threat model. That is suitable for a DIFFERENT Snowflake situation: A security team thinks a masking policy can replace both network controls and database RBAC for a regulated dataset. It does not directly resolve the current requirement: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts.

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 data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts.

Question 270

For a telecommunications provider, the original problem was: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. What observation confirms success?

  1. The audit identifies query principals and accessed objects for representative governed tests.
  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. Authorized corporate connections succeed while an unapproved test source is rejected.

Explanation

Correct Answer

A:

The audit identifies query principals and accessed objects for representative governed tests. This validates the relevant action: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag. The underlying Snowflake behavior is: Usage, access history and cost metering contain different evidence about data access.

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: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.

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: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.

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: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.