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 19

Question 180

During operational handoff for this problem: A business team asks an LLM to answer revenue questions but the model frequently invents column names and joins. 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. Test input parsing and malformed payload handling in ingestion contracts.
  4. Test generated SQL and model semantics against finance-approved calculations.

Explanation

Correct Answer

D:

Test generated SQL and model semantics against finance-approved calculations. This reduces recurrence of: Text-to-SQL accuracy depends on controlled semantic definitions and database permissions. The verification should demonstrate: A pilot maps representative natural-language revenue questions to valid SQL based on approved definitions.

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: Text-to-SQL accuracy depends on controlled semantic definitions and database permissions.

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: Text-to-SQL accuracy depends on controlled semantic definitions and database permissions.

C:

Test input parsing and malformed payload handling in ingestion contracts. That safeguard is aimed at ANOTHER risk: A migration tool defines a table column as VARCHAR then assumes all JSON path operators will work on it without conversion. It is less targeted than the control for: Text-to-SQL accuracy depends on controlled semantic definitions and database permissions.

Question 181

A data-platform team must resolve: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. Which technical change most directly solves it?

  1. Define appropriate future grants in the intended database or schema and verify ownership/grant policies.
  2. Review the intended role hierarchy and verify inheritance upward through granted roles.
  3. Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.
  4. Choose supported secure view semantics where definition exposure and optimization trade-offs are material.

Explanation

Correct Answer

B:

Review the intended role hierarchy and verify inheritance upward through granted roles. This directly addresses the described Snowflake condition: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. The mechanism is: Role grants create inherited privilege relationships that flow through the role hierarchy. Verify success using: The parent role's effective rights include privileges inherited from authorized subordinate roles.

Incorrect Answers

A:

Define appropriate future grants in the intended database or schema and verify ownership/grant policies. That is suitable for a DIFFERENT Snowflake situation: A project grants future objects manually each week and a newly created table is invisible to its application role. It does not directly resolve the current requirement: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission.

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 manager grants SELECT to a child role and expects a parent role to automatically lose that permission.

D:

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 manager grants SELECT to a child role and expects a parent role to automatically lose that permission.

Question 182

A Snowflake acceptance test follows this incident: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. What evidence most directly proves the correction?

  1. Query history attributes activity to the intended service identity and a revoked app credential stops only its app.
  2. The analyst can read approved reports without gaining account-wide administrative powers.
  3. The parent role's effective rights include privileges inherited from authorized subordinate roles.
  4. A network trace uses the intended private endpoint while public access remains subject to documented policy.

Explanation

Correct Answer

C:

The parent role's effective rights include privileges inherited from authorized subordinate roles. This validates the relevant action: Review the intended role hierarchy and verify inheritance upward through granted roles. The underlying Snowflake behavior is: Role grants create inherited privilege relationships that flow through the role hierarchy.

Incorrect Answers

A:

Query history attributes activity to the intended service identity and a revoked app credential stops only its app. This evidence tests a DIFFERENT situation: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. The correction required in this case is: Review the intended role hierarchy and verify inheritance upward through granted roles.

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: Review the intended role hierarchy and verify inheritance upward through granted roles.

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: Review the intended role hierarchy and verify inheritance upward through granted roles.

Question 183

The data-platform team observes: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. Which architectural or processing fact matters most?

  1. Object ownership enables more control than the creation privileges needed for a narrow workflow.
  2. Account-wide administration is broader than the role privileges needed for read-only analysis.
  3. Federated authentication requires a consistent identity mapping independently of database grants.
  4. Role grants create inherited privilege relationships that flow through the role hierarchy.

Explanation

Correct Answer

D:

Role grants create inherited privilege relationships that flow through the role hierarchy. This explains the condition: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. The corrective response is: Review the intended role hierarchy and verify inheritance upward through granted roles.

Incorrect Answers

A:

Object ownership enables more control than the creation privileges needed for a narrow workflow. That mechanism explains a DIFFERENT Snowflake problem: An engineer gives an application OWNERSHIP on a production database merely to create one staging table. Here the relevant mechanism instead is: Role grants create inherited privilege relationships that flow through the role hierarchy.

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: Role grants create inherited privilege relationships that flow through the role hierarchy.

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: Role grants create inherited privilege relationships that flow through the role hierarchy.

Question 184

For a public-sector reporting unit, this issue must not recur: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. Which review control fits best?

  1. Test effective permissions after role hierarchy changes rather than assuming role names set power.
  2. Inventory service-user ownership and rotate credentials with controlled revocation tests.
  3. Review service roles for accidental object ownership escalation.
  4. Exercise break-glass access and log each use after authentication policy changes.

Explanation

Correct Answer

A:

Test effective permissions after role hierarchy changes rather than assuming role names set power. This reduces recurrence of: Role grants create inherited privilege relationships that flow through the role hierarchy. The verification should demonstrate: The parent role's effective rights include privileges inherited from authorized subordinate roles.

Incorrect Answers

B:

Inventory service-user ownership and rotate credentials with controlled revocation tests. That safeguard is aimed at ANOTHER risk: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. It is less targeted than the control for: Role grants create inherited privilege relationships that flow through the role hierarchy.

C:

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: Role grants create inherited privilege relationships that flow through the role hierarchy.

D:

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: Role grants create inherited privilege relationships that flow through the role hierarchy.

Question 185

In a governed Snowflake environment, the reported condition is: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. What should be implemented first?

  1. Configure and enforce the supported authentication policy and MFA requirements for the relevant users.
  2. Evaluate approved cloud private connectivity such as PrivateLink or equivalent supported private endpoint integration.
  3. Move toward supported key-pair or programmatic token authentication with per-application rotation control.
  4. Delegate scoped CREATE TABLE in a controlled schema and required USAGE rather than broad database ownership.

Explanation

Correct Answer

C:

Move toward supported key-pair or programmatic token authentication with per-application rotation control. This directly addresses the described Snowflake condition: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. The mechanism is: Independent programmatic credentials make service identities revocable without broad shared-secret outages. Verify success using: One app credential can be rotated and verified while other distinct integrations continue running.

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: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs.

B:

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 integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs.

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: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs.

Question 186

A test plan evaluates: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. Which evidence should be required before release?

  1. A network trace uses the intended private endpoint while public access remains subject to documented policy.
  2. A controlled SSO login resolves to the correct Snowflake user and role context.
  3. Query history attributes activity to the intended service identity and a revoked app credential stops only its app.
  4. One app credential can be rotated and verified while other distinct integrations continue running.

Explanation

Correct Answer

D:

One app credential can be rotated and verified while other distinct integrations continue running. This validates the relevant action: Move toward supported key-pair or programmatic token authentication with per-application rotation control. The underlying Snowflake behavior is: Independent programmatic credentials make service identities revocable without broad shared-secret outages.

Incorrect Answers

A:

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: Move toward supported key-pair or programmatic token authentication with per-application rotation control.

B:

A controlled SSO login resolves to the correct Snowflake user and role context. This evidence tests a DIFFERENT situation: A user from a federated identity provider can authenticate, but Snowflake cannot map the sign-in to the intended account user. The correction required in this case is: Move toward supported key-pair or programmatic token authentication with per-application rotation control.

C:

Query history attributes activity to the intended service identity and a revoked app credential stops only its app. This evidence tests a DIFFERENT situation: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. The correction required in this case is: Move toward supported key-pair or programmatic token authentication with per-application rotation control.

Question 187

A Snowflake incident report notes: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. What underlying mechanism explains the behavior?

  1. Independent programmatic credentials make service identities revocable without broad shared-secret outages.
  2. IP allowlisting and private network attachment solve different transport security requirements.
  3. Strong perimeter policies can lock out operators without properly governed emergency procedures.
  4. Shared credentials undermine per-application attribution and least-privilege offboarding.

Explanation

Correct Answer

A:

Independent programmatic credentials make service identities revocable without broad shared-secret outages. This explains the condition: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. The corrective response is: Move toward supported key-pair or programmatic token authentication with per-application rotation control.

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: Independent programmatic credentials make service identities revocable without broad shared-secret outages.

C:

Strong perimeter policies can lock out operators without properly governed emergency procedures. That mechanism explains a DIFFERENT Snowflake problem: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. Here the relevant mechanism instead is: Independent programmatic credentials make service identities revocable without broad shared-secret outages.

D:

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: Independent programmatic credentials make service identities revocable without broad shared-secret outages.

Question 188

A platform governance committee considers: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. What preventive check should be standardized?

  1. Test naming changes in IdP and Snowflake before federation migrations.
  2. Schedule credential expiration and parallel-cutover tests for programmatic access.
  3. Maintain approved egress IP ranges and test exceptions after network changes.
  4. Revalidate entitlement mapping after organizational restructures.

Explanation

Correct Answer

B:

Schedule credential expiration and parallel-cutover tests for programmatic access. This reduces recurrence of: Independent programmatic credentials make service identities revocable without broad shared-secret outages. The verification should demonstrate: One app credential can be rotated and verified while other distinct integrations continue running.

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: Independent programmatic credentials make service identities revocable without broad shared-secret outages.

C:

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: Independent programmatic credentials make service identities revocable without broad shared-secret outages.

D:

Revalidate entitlement mapping after organizational restructures. That safeguard is aimed at ANOTHER risk: A regional sales analyst can read rows for every country despite having permission only for their own region. It is less targeted than the control for: Independent programmatic credentials make service identities revocable without broad shared-secret outages.

Question 189

An engineering team investigates the following Snowflake issue: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. Which configuration or processing decision is most appropriate?

  1. Choose supported secure view semantics where definition exposure and optimization trade-offs are material.
  2. Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.
  3. Review the intended role hierarchy and verify inheritance upward through granted roles.
  4. Use governed classification tags and appropriate policy associations to apply consistent protection at scale.

Explanation

Correct Answer

D:

Use governed classification tags and appropriate policy associations to apply consistent protection at scale. This directly addresses the described Snowflake condition: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. The mechanism is: Tags can carry governance metadata and support policy-based control design. Verify success using: Newly tagged sensitive test columns inherit the intended masking behavior where supported.

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: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules.

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: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules.

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: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules.

Question 190

For an e-commerce operations team, the original problem was: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. What observation confirms success?

  1. Newly tagged sensitive test columns inherit the intended masking behavior where supported.
  2. The consumer can query approved rows while the secure view definition is not exposed like an ordinary view.
  3. A payroll role sees approved values while the analyst sees the configured masked representation.
  4. The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds.

Explanation

Correct Answer

A:

Newly tagged sensitive test columns inherit the intended masking behavior where supported. This validates the relevant action: Use governed classification tags and appropriate policy associations to apply consistent protection at scale. The underlying Snowflake behavior is: Tags can carry governance metadata and support policy-based control design.

Incorrect Answers

B:

The consumer can query approved rows while the secure view definition is not exposed like an ordinary view. This evidence tests a DIFFERENT situation: A contractor is granted a secure view but its definition reveals an underlying protected calculation when copied into an ordinary view. The correction required in this case is: Use governed classification tags and appropriate policy associations to apply consistent protection at scale.

C:

A payroll role sees approved values while the analyst sees the configured masked representation. This evidence tests a DIFFERENT situation: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. The correction required in this case is: Use governed classification tags and appropriate policy associations to apply consistent protection at scale.

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: Use governed classification tags and appropriate policy associations to apply consistent protection at scale.