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 4

Question 30

For a telecommunications provider, the original problem was: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. What observation confirms success?

  1. A payroll role sees approved values while the analyst sees the configured masked representation.
  2. The consumer role queries its approved interface but cannot read the raw customer table directly.
  3. A governance report identifies responsible owners and classified fields without unauthorized tag drift.
  4. Authorized corporate connections succeed while an unapproved test source is rejected.

Explanation

Correct Answer

A:

A payroll role sees approved values while the analyst sees the configured masked representation. This validates the relevant action: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression. The underlying Snowflake behavior is: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

Incorrect Answers

B:

The consumer role queries its approved interface but cannot read the raw customer table directly. This evidence tests a DIFFERENT situation: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. The correction required in this case is: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

C:

A governance report identifies responsible owners and classified fields without unauthorized tag drift. This evidence tests a DIFFERENT situation: An enterprise needs a reliable inventory of who owns sensitive schemas, but its governance tags are edited without review. The correction required in this case is: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

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: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

Question 31

In a case affecting a telecommunications provider, this issue appears: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. What explains it?

  1. Tags can carry governance metadata and support policy-based control design.
  2. Masking policies evaluate authorized context at query time rather than copying a second redacted table.
  3. Row access policies restrict result rows dynamically as SQL is executed.
  4. Strong perimeter policies can lock out operators without properly governed emergency procedures.

Explanation

Correct Answer

B:

Masking policies evaluate authorized context at query time rather than copying a second redacted table. This explains the condition: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. The corrective response is: Apply a dynamic data masking policy to the sensitive column using an appropriate role-aware expression.

Incorrect Answers

A:

Tags can carry governance metadata and support policy-based control design. That mechanism explains a DIFFERENT Snowflake problem: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. Here the relevant mechanism instead is: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

C:

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: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

D:

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: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

Question 32

After remediating the Snowflake issue, the team reviews: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. Which recurring control is most targeted?

  1. Reconcile raw-table grants when creating new governed reporting views.
  2. Audit tag changes and the identities allowed to mutate classification metadata.
  3. Test the policy with explicit role-switch fixtures and schema changes.
  4. Add new-view grants to deployment templates and access test fixtures.

Explanation

Correct Answer

C:

Test the policy with explicit role-switch fixtures and schema changes. This reduces recurrence of: Masking policies evaluate authorized context at query time rather than copying a second redacted table. The verification should demonstrate: A payroll role sees approved values while the analyst sees the configured masked representation.

Incorrect Answers

A:

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: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

B:

Audit tag changes and the identities allowed to mutate classification metadata. That safeguard is aimed at ANOTHER risk: An enterprise needs a reliable inventory of who owns sensitive schemas, but its governance tags are edited without review. It is less targeted than the control for: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

D:

Add new-view grants to deployment templates and access test fixtures. That safeguard is aimed at ANOTHER risk: A role can create a view in a schema but analysts cannot SELECT from the newly created view. It is less targeted than the control for: Masking policies evaluate authorized context at query time rather than copying a second redacted table.

Question 33

At a consumer marketplace, a Snowflake implementation review finds: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. Which action best addresses this requirement?

  1. Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses.
  2. Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately.
  3. Inspect storage usage including Time Travel and Fail-safe historical versions and adjust retention policy where justified.
  4. Delegate scoped CREATE TABLE in a controlled schema and required USAGE rather than broad database ownership.

Explanation

Correct Answer

A:

Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses. This directly addresses the described Snowflake condition: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. The mechanism is: Resource monitors track eligible warehouse credits, not every category of Snowflake charge. Verify success using: The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds.

Incorrect Answers

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: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap.

C:

Inspect storage usage including Time Travel and Fail-safe historical versions and adjust retention policy where justified. That is suitable for a DIFFERENT Snowflake situation: A department thinks all storage cost comes from active table bytes and ignores historical retained data from updates. It does not directly resolve the current requirement: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap.

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 analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap.

Question 34

After the approved change, engineers revisit: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. Which result establishes the intended state?

  1. A safe test monitor demonstrates the configured action at credit-limit breach.
  2. The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds.
  3. The cost report includes the task's serverless consumption even when the old warehouse is idle.
  4. The parent role's effective rights include privileges inherited from authorized subordinate roles.

Explanation

Correct Answer

B:

The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds. This validates the relevant action: Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses. The underlying Snowflake behavior is: Resource monitors track eligible warehouse credits, not every category of Snowflake charge.

Incorrect Answers

A:

A safe test monitor demonstrates the configured action at credit-limit breach. This evidence tests a DIFFERENT situation: A resource monitor notifies at 90% but never interrupts spend after a team exceeds its hard monthly allowance. The correction required in this case is: Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses.

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: Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses.

D:

The parent role's effective rights include privileges inherited from authorized subordinate roles. This evidence tests a DIFFERENT situation: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. The correction required in this case is: Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses.

Question 35

A root-cause investigation considers: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. What is the most applicable explanation?

  1. Serverless features can have separate meters outside traditional warehouse resource monitors.
  2. Monitor notify-only actions do not impose the same workload restriction as suspend actions.
  3. Resource monitors track eligible warehouse credits, not every category of Snowflake charge.
  4. Object ownership enables more control than the creation privileges needed for a narrow workflow.

Explanation

Correct Answer

C:

Resource monitors track eligible warehouse credits, not every category of Snowflake charge. This explains the condition: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. The corrective response is: Configure an appropriate resource monitor with thresholds and email or suspend actions for eligible warehouses.

Incorrect Answers

A:

Serverless features can have separate meters outside traditional warehouse resource monitors. That mechanism explains a DIFFERENT Snowflake problem: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. Here the relevant mechanism instead is: Resource monitors track eligible warehouse credits, not every category of Snowflake charge.

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: Resource monitors track eligible warehouse credits, not every category of Snowflake charge.

D:

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: Resource monitors track eligible warehouse credits, not every category of Snowflake charge.

Question 36

During operational handoff for this problem: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. Which guardrail should be included?

  1. Review all monitor thresholds and action types during cost-control testing.
  2. Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless.
  3. Reconcile raw-table grants when creating new governed reporting views.
  4. Reconcile warehouse credits and serverless costs in parallel dashboards.

Explanation

Correct Answer

D:

Reconcile warehouse credits and serverless costs in parallel dashboards. This reduces recurrence of: Resource monitors track eligible warehouse credits, not every category of Snowflake charge. The verification should demonstrate: The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds.

Incorrect Answers

A:

Review all monitor thresholds and action types during cost-control testing. That safeguard is aimed at ANOTHER risk: A resource monitor notifies at 90% but never interrupts spend after a team exceeds its hard monthly allowance. It is less targeted than the control for: Resource monitors track eligible warehouse credits, not every category of Snowflake charge.

B:

Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless. That safeguard is aimed at ANOTHER risk: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. It is less targeted than the control for: Resource monitors track eligible warehouse credits, not every category of Snowflake charge.

C:

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: Resource monitors track eligible warehouse credits, not every category of Snowflake charge.

Question 37

A data-platform team must resolve: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. Which technical change most directly solves it?

  1. Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan.
  2. Stage the local file through a supported PUT-to-internal-stage or equivalent approved upload workflow first.
  3. Scope the stage path or filename pattern to the correct feed and verify expected input candidates.
  4. Use COPY INTO a designated stage or external location with the authorized file format and unload options.

Explanation

Correct Answer

B:

Stage the local file through a supported PUT-to-internal-stage or equivalent approved upload workflow first. This directly addresses the described Snowflake condition: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. The mechanism is: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files. Verify success using: The stage lists the expected file and COPY INTO can read it with the intended format.

Incorrect Answers

A:

Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan. That is suitable for a DIFFERENT Snowflake situation: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. It does not directly resolve the current requirement: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere.

C:

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: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere.

D:

Use COPY INTO a designated stage or external location with the authorized file format and unload options. That is suitable for a DIFFERENT Snowflake situation: An analyst must export approved query results to a partner's cloud stage but attempts PUT, which uploads workstation files. It does not directly resolve the current requirement: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere.

Question 38

A Snowflake acceptance test follows this incident: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. What evidence most directly proves the correction?

  1. A least-privilege role can read the approved object prefix without SQL containing long-lived cloud secrets.
  2. The validation identifies a deliberately malformed fixture without modifying production data.
  3. The stage lists the expected file and COPY INTO can read it with the intended format.
  4. Session metadata shows the intended target account and query history records the application job.

Explanation

Correct Answer

C:

The stage lists the expected file and COPY INTO can read it with the intended format. This validates the relevant action: Stage the local file through a supported PUT-to-internal-stage or equivalent approved upload workflow first. The underlying Snowflake behavior is: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

Incorrect Answers

A:

A least-privilege role can read the approved object prefix without SQL containing long-lived cloud secrets. This evidence tests a DIFFERENT situation: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors. The correction required in this case is: Stage the local file through a supported PUT-to-internal-stage or equivalent approved upload workflow first.

B:

The validation identifies a deliberately malformed fixture without modifying production data. This evidence tests a DIFFERENT situation: A data engineer needs to inspect malformed rows before committing a bulk load into the finance table. The correction required in this case is: Stage the local file through a supported PUT-to-internal-stage or equivalent approved upload workflow first.

D:

Session metadata shows the intended target account and query history records the application job. This evidence tests a DIFFERENT situation: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. The correction required in this case is: Stage the local file through a supported PUT-to-internal-stage or equivalent approved upload workflow first.

Question 39

The data-platform team observes: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. Which architectural or processing fact matters most?

  1. CSV parsing depends on the declared file format, not just a .csv extension.
  2. Semi-structured JSON files require compatible parsing rather than CSV delimiter interpretation.
  3. Snowflake unloading uses COPY INTO location rather than PUT, which stages local source files.
  4. COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

Explanation

Correct Answer

D:

COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files. This explains the condition: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. The corrective response is: Stage the local file through a supported PUT-to-internal-stage or equivalent approved upload workflow first.

Incorrect Answers

A:

CSV parsing depends on the declared file format, not just a .csv extension. That mechanism explains a DIFFERENT Snowflake problem: A bulk load of customer CSV records splits addresses into wrong columns because the delimiter differs from the source contract. Here the relevant mechanism instead is: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

B:

Semi-structured JSON files require compatible parsing rather than CSV delimiter interpretation. That mechanism explains a DIFFERENT Snowflake problem: An engineer sets JSON FILE FORMAT to CSV and loads a nested event record into a one-column raw table. Here the relevant mechanism instead is: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

C:

Snowflake unloading uses COPY INTO location rather than PUT, which stages local source files. That mechanism explains a DIFFERENT Snowflake problem: An analyst must export approved query results to a partner's cloud stage but attempts PUT, which uploads workstation files. Here the relevant mechanism instead is: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

Question 40

For a public-sector reporting unit, this issue must not recur: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. Which review control fits best?

  1. Validate stage upload and permissions separately from table loading.
  2. Add negative file fixtures to every new file-format rollout.
  3. Validate representative nested arrays, nulls and malformed JSON before production loads.
  4. Version output schemas and run consumer compatibility tests after format changes.

Explanation

Correct Answer

A:

Validate stage upload and permissions separately from table loading. This reduces recurrence of: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files. The verification should demonstrate: The stage lists the expected file and COPY INTO can read it with the intended format.

Incorrect Answers

B:

Add negative file fixtures to every new file-format rollout. That safeguard is aimed at ANOTHER risk: A data engineer needs to inspect malformed rows before committing a bulk load into the finance table. It is less targeted than the control for: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

C:

Validate representative nested arrays, nulls and malformed JSON before production loads. That safeguard is aimed at ANOTHER risk: An engineer sets JSON FILE FORMAT to CSV and loads a nested event record into a one-column raw table. It is less targeted than the control for: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.

D:

Version output schemas and run consumer compatibility tests after format changes. That safeguard is aimed at ANOTHER risk: A business partner receives unloaded numeric fields as unexpected strings because the agreed file encoding differs from the Snowflake unload format. It is less targeted than the control for: COPY INTO reads staged data, not arbitrary local workstation paths as if they were Snowflake server files.