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 51

Question 500

During operational handoff for this problem: An account administrator plans to disable every login at a network boundary during an incident but forgets break-glass access. Which guardrail should be included?

  1. Test naming changes in IdP and Snowflake before federation migrations.
  2. Test privileged account enrollment and recovery before enforcement rollout.
  3. Test layered access with both allowed and denied user cases.
  4. Exercise break-glass access and log each use after authentication policy changes.

Explanation

Correct Answer

D:

Exercise break-glass access and log each use after authentication policy changes. This reduces recurrence of: Strong perimeter policies can lock out operators without properly governed emergency procedures. The verification should demonstrate: An incident drill confirms required emergency recovery without opening uncontrolled public login.

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: Strong perimeter policies can lock out operators without properly governed emergency procedures.

B:

Test privileged account enrollment and recovery before enforcement rollout. That safeguard is aimed at ANOTHER risk: Security requires stronger authentication for privileged human users but the account relies only on passwords. It is less targeted than the control for: Strong perimeter policies can lock out operators without properly governed emergency procedures.

C:

Test layered access with both allowed and denied user cases. That safeguard is aimed at ANOTHER risk: A security team thinks a masking policy can replace both network controls and database RBAC for a regulated dataset. It is less targeted than the control for: Strong perimeter policies can lock out operators without properly governed emergency procedures.

Question 501

A data-platform team must resolve: An analyst creates an external function that exports restricted data even though its normal table queries are masked. Which technical change most directly solves it?

  1. Attach a row access policy using approved role/entitlement logic to filter visible records.
  2. Review the external access and function privileges and apply appropriate data policies and outbound restrictions.
  3. Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.
  4. Grant the role necessary USAGE on the containing database and schema in addition to SELECT on the table.

Explanation

Correct Answer

B:

Review the external access and function privileges and apply appropriate data policies and outbound restrictions. This directly addresses the described Snowflake condition: An analyst creates an external function that exports restricted data even though its normal table queries are masked. The mechanism is: Data-governance policy must account for execution and external integration boundaries, not only UI views. Verify success using: Test queries enforce required column protections and disallow unapproved data export paths.

Incorrect Answers

A:

Attach a row access policy using approved role/entitlement logic to filter visible records. That is suitable for a DIFFERENT Snowflake situation: A regional sales analyst can read rows for every country despite having permission only for their own region. It does not directly resolve the current requirement: An analyst creates an external function that exports restricted data even though its normal table queries are masked.

C:

Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns. That is suitable for a DIFFERENT Snowflake situation: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. It does not directly resolve the current requirement: An analyst creates an external function that exports restricted data even though its normal table queries are masked.

D:

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: An analyst creates an external function that exports restricted data even though its normal table queries are masked.

Question 502

A Snowflake acceptance test follows this incident: An analyst creates an external function that exports restricted data even though its normal table queries are masked. What evidence most directly proves the correction?

  1. A payroll role sees approved values while the analyst sees the configured masked representation.
  2. Newly tagged sensitive test columns inherit the intended masking behavior where supported.
  3. Test queries enforce required column protections and disallow unapproved data export paths.
  4. The analyst can read approved reports without gaining account-wide administrative powers.

Explanation

Correct Answer

C:

Test queries enforce required column protections and disallow unapproved data export paths. This validates the relevant action: Review the external access and function privileges and apply appropriate data policies and outbound restrictions. The underlying Snowflake behavior is: Data-governance policy must account for execution and external integration boundaries, not only UI views.

Incorrect Answers

A:

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: Review the external access and function privileges and apply appropriate data policies and outbound restrictions.

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: Review the external access and function privileges and apply appropriate data policies and outbound restrictions.

D:

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 external access and function privileges and apply appropriate data policies and outbound restrictions.

Question 503

The data-platform team observes: An analyst creates an external function that exports restricted data even though its normal table queries are masked. Which architectural or processing fact matters most?

  1. Row access policies restrict result rows dynamically as SQL is executed.
  2. Metadata classification is only trustworthy when tag editing rights and ownership are governed.
  3. Independent programmatic credentials make service identities revocable without broad shared-secret outages.
  4. Data-governance policy must account for execution and external integration boundaries, not only UI views.

Explanation

Correct Answer

D:

Data-governance policy must account for execution and external integration boundaries, not only UI views. This explains the condition: An analyst creates an external function that exports restricted data even though its normal table queries are masked. The corrective response is: Review the external access and function privileges and apply appropriate data policies and outbound restrictions.

Incorrect Answers

A:

Row access policies restrict result rows dynamically as SQL is executed. That mechanism explains a DIFFERENT Snowflake problem: A regional sales analyst can read rows for every country despite having permission only for their own region. Here the relevant mechanism instead is: Data-governance policy must account for execution and external integration boundaries, not only UI views.

B:

Metadata classification is only trustworthy when tag editing rights and ownership are governed. That mechanism explains a DIFFERENT Snowflake problem: An enterprise needs a reliable inventory of who owns sensitive schemas, but its governance tags are edited without review. Here the relevant mechanism instead is: Data-governance policy must account for execution and external integration boundaries, not only UI views.

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: Data-governance policy must account for execution and external integration boundaries, not only UI views.

Question 504

For a university data platform, this issue must not recur: An analyst creates an external function that exports restricted data even though its normal table queries are masked. Which review control fits best?

  1. Include external functions and outbound integrations in data exfiltration reviews.
  2. Document audit view latency, retention and roles needed to query access history.
  3. Review view security properties before sharing sensitive transformation logic.
  4. Test naming changes in IdP and Snowflake before federation migrations.

Explanation

Correct Answer

A:

Include external functions and outbound integrations in data exfiltration reviews. This reduces recurrence of: Data-governance policy must account for execution and external integration boundaries, not only UI views. The verification should demonstrate: Test queries enforce required column protections and disallow unapproved data export paths.

Incorrect Answers

B:

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: Data-governance policy must account for execution and external integration boundaries, not only UI views.

C:

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: Data-governance policy must account for execution and external integration boundaries, not only UI views.

D:

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: Data-governance policy must account for execution and external integration boundaries, not only UI views.

Question 505

In a governed Snowflake environment, the reported condition is: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. What should be implemented first?

  1. Model compute, active/historical storage, and managed service meters independently before archiving the system.
  2. Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately.
  3. Account for documented data latency and use near-real-time sources where supported for urgent validation.
  4. Apply a supported network policy at the appropriate account or user scope with approved allowed IP ranges.

Explanation

Correct Answer

C:

Account for documented data latency and use near-real-time sources where supported for urgent validation. This directly addresses the described Snowflake condition: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. The mechanism is: Account-level usage views can have latency rather than providing immediate transactional updates. Verify success using: The report shows an explicit freshness indicator and reconciles delayed cost rows later.

Incorrect Answers

A:

Model compute, active/historical storage, and managed service meters independently before archiving the system. That is suitable for a DIFFERENT Snowflake situation: A team thinks suspending a warehouse eliminates storage and file-stage charges for inactive datasets. It does not directly resolve the current requirement: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing.

B:

Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately. That is suitable for a DIFFERENT Snowflake situation: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. It does not directly resolve the current requirement: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing.

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 cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing.

Question 506

A test plan evaluates: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. Which evidence should be required before release?

  1. Representative project queries appear with traceable tags, allowing a reasoned chargeback allocation.
  2. The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds.
  3. The analyst can read approved reports without gaining account-wide administrative powers.
  4. The report shows an explicit freshness indicator and reconciles delayed cost rows later.

Explanation

Correct Answer

D:

The report shows an explicit freshness indicator and reconciles delayed cost rows later. This validates the relevant action: Account for documented data latency and use near-real-time sources where supported for urgent validation. The underlying Snowflake behavior is: Account-level usage views can have latency rather than providing immediate transactional updates.

Incorrect Answers

A:

Representative project queries appear with traceable tags, allowing a reasoned chargeback allocation. This evidence tests a DIFFERENT situation: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. The correction required in this case is: Account for documented data latency and use near-real-time sources where supported for urgent validation.

B:

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: Account for documented data latency and use near-real-time sources where supported for urgent validation.

C:

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: Account for documented data latency and use near-real-time sources where supported for urgent validation.

Question 507

A Snowflake incident report notes: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. What underlying mechanism explains the behavior?

  1. Account-level usage views can have latency rather than providing immediate transactional updates.
  2. Monitor notify-only actions do not impose the same workload restriction as suspend actions.
  3. Repeated updates can create retained micro-partition versions billed during recovery windows.
  4. Secure views reduce certain metadata exposure paths; they are not a substitute for all row and column controls.

Explanation

Correct Answer

A:

Account-level usage views can have latency rather than providing immediate transactional updates. This explains the condition: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. The corrective response is: Account for documented data latency and use near-real-time sources where supported for urgent validation.

Incorrect Answers

B:

Monitor notify-only actions do not impose the same workload restriction as suspend actions. That mechanism explains a DIFFERENT Snowflake problem: A resource monitor notifies at 90% but never interrupts spend after a team exceeds its hard monthly allowance. Here the relevant mechanism instead is: Account-level usage views can have latency rather than providing immediate transactional updates.

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: Account-level usage views can have latency rather than providing immediate transactional updates.

D:

Secure views reduce certain metadata exposure paths; they are not a substitute for all row and column controls. That mechanism explains a DIFFERENT Snowflake problem: A contractor is granted a secure view but its definition reveals an underlying protected calculation when copied into an ordinary view. Here the relevant mechanism instead is: Account-level usage views can have latency rather than providing immediate transactional updates.

Question 508

A platform governance committee considers: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. What preventive check should be standardized?

  1. Track data churn, retention and recoverability before tuning storage costs.
  2. Label telemetry recency and use validated time windows in chargeback reports.
  3. Review all billing components before claiming a workload is cost-free.
  4. Reconcile raw-table grants when creating new governed reporting views.

Explanation

Correct Answer

B:

Label telemetry recency and use validated time windows in chargeback reports. This reduces recurrence of: Account-level usage views can have latency rather than providing immediate transactional updates. The verification should demonstrate: The report shows an explicit freshness indicator and reconciles delayed cost rows later.

Incorrect Answers

A:

Track data churn, retention and recoverability before tuning storage costs. That safeguard is aimed at ANOTHER risk: A department thinks all storage cost comes from active table bytes and ignores historical retained data from updates. It is less targeted than the control for: Account-level usage views can have latency rather than providing immediate transactional updates.

C:

Review all billing components before claiming a workload is cost-free. That safeguard is aimed at ANOTHER risk: A team thinks suspending a warehouse eliminates storage and file-stage charges for inactive datasets. It is less targeted than the control for: Account-level usage views can have latency rather than providing immediate transactional updates.

D:

Reconcile raw-table grants when creating new governed reporting views. That safeguard is aimed at ANOTHER risk: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. It is less targeted than the control for: Account-level usage views can have latency rather than providing immediate transactional updates.

Question 509

An engineering team investigates the following Snowflake issue: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors. Which configuration or processing decision is most appropriate?

  1. Define and test the correct CSV FILE FORMAT delimiter, quote and header handling for the staged data.
  2. Scope the stage path or filename pattern to the correct feed and verify expected input candidates.
  3. Reduce allowed cloud storage locations and integration permissions to the approved prefixes.
  4. Use a supported external stage and storage integration with properly scoped cloud permissions.

Explanation

Correct Answer

D:

Use a supported external stage and storage integration with properly scoped cloud permissions. This directly addresses the described Snowflake condition: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors. The mechanism is: Storage integrations provide controlled cloud access delegation for external stages. Verify success using: A least-privilege role can read the approved object prefix without SQL containing long-lived cloud secrets.

Incorrect Answers

A:

Define and test the correct CSV FILE FORMAT delimiter, quote and header handling for the staged data. That is suitable for a DIFFERENT Snowflake situation: A bulk load of customer CSV records splits addresses into wrong columns because the delimiter differs from the source contract. It does not directly resolve the current requirement: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors.

B:

Scope the stage path or filename pattern to the correct feed and verify expected input candidates. That is suitable for a DIFFERENT Snowflake situation: A staged directory contains many unrelated feeds and COPY loads data intended for another department. It does not directly resolve the current requirement: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors.

C:

Reduce allowed cloud storage locations and integration permissions to the approved prefixes. That is suitable for a DIFFERENT Snowflake situation: A service account imports data via a storage integration but its cloud IAM policy allows access to an entire organization bucket. It does not directly resolve the current requirement: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors.

Question 510

For a telecommunications provider, the original problem was: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors. What observation confirms success?

  1. A least-privilege role can read the approved object prefix without SQL containing long-lived cloud secrets.
  2. A representative record maps its fields and header correctly without column shifts.
  3. A dry-run or test load includes only source files for the approved business feed.
  4. The updated client establishes an authorized session and runs the same controlled query.

Explanation

Correct Answer

A:

A least-privilege role can read the approved object prefix without SQL containing long-lived cloud secrets. This validates the relevant action: Use a supported external stage and storage integration with properly scoped cloud permissions. The underlying Snowflake behavior is: Storage integrations provide controlled cloud access delegation for external stages.

Incorrect Answers

B:

A representative record maps its fields and header correctly without column shifts. This evidence tests a DIFFERENT situation: A bulk load of customer CSV records splits addresses into wrong columns because the delimiter differs from the source contract. The correction required in this case is: Use a supported external stage and storage integration with properly scoped cloud permissions.

C:

A dry-run or test load includes only source files for the approved business feed. This evidence tests a DIFFERENT situation: A staged directory contains many unrelated feeds and COPY loads data intended for another department. The correction required in this case is: Use a supported external stage and storage integration with properly scoped cloud permissions.

D:

The updated client establishes an authorized session and runs the same controlled query. This evidence tests a DIFFERENT situation: A BI tool connects using an outdated driver and sees unsupported authentication failures after a platform security update. The correction required in this case is: Use a supported external stage and storage integration with properly scoped cloud permissions.