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 20

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.

Question 191

In a case affecting an e-commerce operations team, this issue appears: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. What explains it?

  1. Least privilege is enforced at object and policy boundaries, not by naming tables as sensitive.
  2. Tags can carry governance metadata and support policy-based control design.
  3. Metadata classification is only trustworthy when tag editing rights and ownership are governed.
  4. Authentication factors protect account entry and are distinct from SQL roles after sign-in.

Explanation

Correct Answer

B:

Tags can carry governance metadata and support policy-based control design. This explains the condition: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. The corrective response is: Use governed classification tags and appropriate policy associations to apply consistent protection at scale.

Incorrect Answers

A:

Least privilege is enforced at object and policy boundaries, not by naming tables as sensitive. That mechanism explains a DIFFERENT Snowflake problem: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. Here the relevant mechanism instead is: Tags can carry governance metadata and support policy-based control design.

C:

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: Tags can carry governance metadata and support policy-based control design.

D:

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: Tags can carry governance metadata and support policy-based control design.

Question 192

After remediating the Snowflake issue, the team reviews: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. Which recurring control is most targeted?

  1. Reconcile raw-table grants when creating new governed reporting views.
  2. Audit complete grant hierarchies for sensitive object revocations.
  3. Review automated classification changes and policy-tag associations regularly.
  4. Evaluate the credit/performance trade-off when frequently resizing workloads.

Explanation

Correct Answer

C:

Review automated classification changes and policy-tag associations regularly. This reduces recurrence of: Tags can carry governance metadata and support policy-based control design. The verification should demonstrate: Newly tagged sensitive test columns inherit the intended masking behavior where supported.

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: Tags can carry governance metadata and support policy-based control design.

B:

Audit complete grant hierarchies for sensitive object revocations. That safeguard is aimed at ANOTHER risk: A data steward revokes a user's role but their previous worksheet continues to query an authorized view under a different active role. It is less targeted than the control for: Tags can carry governance metadata and support policy-based control design.

D:

Evaluate the credit/performance trade-off when frequently resizing workloads. That safeguard is aimed at ANOTHER risk: A daily report triggers many cache-missing queries after the warehouse is resized every few minutes. It is less targeted than the control for: Tags can carry governance metadata and support policy-based control design.

Question 193

At a retail analytics group, a Snowflake implementation review finds: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. Which action best addresses this requirement?

  1. Track the appropriate serverless task credit usage sources and apply supported budget or alerting mechanisms.
  2. Inspect query profile and warehouse cache behavior before implementing aggressive resizes.
  3. Configure a supported suspend action at the appropriate actual threshold rather than notification only.
  4. Grant the intended view SELECT plus necessary container privileges to the consuming role.

Explanation

Correct Answer

A:

Track the appropriate serverless task credit usage sources and apply supported budget or alerting mechanisms. This directly addresses the described Snowflake condition: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. The mechanism is: Serverless features can have separate meters outside traditional warehouse resource monitors. Verify success using: The cost report includes the task's serverless consumption even when the old warehouse is idle.

Incorrect Answers

B:

Inspect query profile and warehouse cache behavior before implementing aggressive resizes. That is suitable for a DIFFERENT Snowflake situation: A daily report triggers many cache-missing queries after the warehouse is resized every few minutes. It does not directly resolve the current requirement: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts.

C:

Configure a supported suspend action at the appropriate actual threshold rather than notification only. That is suitable for a DIFFERENT Snowflake situation: A resource monitor notifies at 90% but never interrupts spend after a team exceeds its hard monthly allowance. It does not directly resolve the current requirement: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts.

D:

Grant the intended view SELECT plus necessary container privileges to the consuming role. That is suitable for a DIFFERENT Snowflake situation: A role can create a view in a schema but analysts cannot SELECT from the newly created view. It does not directly resolve the current requirement: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts.

Question 194

After the approved change, engineers revisit: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. Which result establishes the intended state?

  1. The report shows an explicit freshness indicator and reconciles delayed cost rows later.
  2. The cost report includes the task's serverless consumption even when the old warehouse is idle.
  3. A controlled stable-size run has more predictable cache reuse without unexpected correctness differences.
  4. A privileged sign-in prompts for the required additional factor while noncompliant login fails.

Explanation

Correct Answer

B:

The cost report includes the task's serverless consumption even when the old warehouse is idle. This validates the relevant action: Track the appropriate serverless task credit usage sources and apply supported budget or alerting mechanisms. The underlying Snowflake behavior is: Serverless features can have separate meters outside traditional warehouse resource monitors.

Incorrect Answers

A:

The report shows an explicit freshness indicator and reconciles delayed cost rows later. This evidence tests a DIFFERENT situation: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. The correction required in this case is: Track the appropriate serverless task credit usage sources and apply supported budget or alerting mechanisms.

C:

A controlled stable-size run has more predictable cache reuse without unexpected correctness differences. This evidence tests a DIFFERENT situation: A daily report triggers many cache-missing queries after the warehouse is resized every few minutes. The correction required in this case is: Track the appropriate serverless task credit usage sources and apply supported budget or alerting mechanisms.

D:

A privileged sign-in prompts for the required additional factor while noncompliant login fails. This evidence tests a DIFFERENT situation: Security requires stronger authentication for privileged human users but the account relies only on passwords. The correction required in this case is: Track the appropriate serverless task credit usage sources and apply supported budget or alerting mechanisms.

Question 195

A root-cause investigation considers: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. What is the most applicable explanation?

  1. Warehouse suspension does not delete persisted data or eliminate unrelated storage charges.
  2. Repeated updates can create retained micro-partition versions billed during recovery windows.
  3. Serverless features can have separate meters outside traditional warehouse resource monitors.
  4. An effective entitlement may arrive through multiple direct or inherited roles.

Explanation

Correct Answer

C:

Serverless features can have separate meters outside traditional warehouse resource monitors. This explains the condition: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. The corrective response is: Track the appropriate serverless task credit usage sources and apply supported budget or alerting mechanisms.

Incorrect Answers

A:

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: Serverless features can have separate meters outside traditional warehouse resource monitors.

B:

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: Serverless features can have separate meters outside traditional warehouse resource monitors.

D:

An effective entitlement may arrive through multiple direct or inherited roles. That mechanism explains a DIFFERENT Snowflake problem: A data steward revokes a user's role but their previous worksheet continues to query an authorized view under a different active role. Here the relevant mechanism instead is: Serverless features can have separate meters outside traditional warehouse resource monitors.

Question 196

During operational handoff for this problem: A serverless task consumes large credits, but a resource monitor attached to its old warehouse shows no alerts. Which guardrail should be included?

  1. Reconcile warehouse credits and serverless costs in parallel dashboards.
  2. Require consistent query tagging for important pipelines and dashboards.
  3. Test the policy with explicit role-switch fixtures and schema changes.
  4. Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless.

Explanation

Correct Answer

D:

Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless. This reduces recurrence of: Serverless features can have separate meters outside traditional warehouse resource monitors. The verification should demonstrate: The cost report includes the task's serverless consumption even when the old warehouse is idle.

Incorrect Answers

A:

Reconcile warehouse credits and serverless costs in parallel dashboards. That safeguard is aimed at ANOTHER risk: An analyst runs many costly ad hoc queries, but no team is notified when warehouse credits exceed a monthly cap. It is less targeted than the control for: Serverless features can have separate meters outside traditional warehouse resource monitors.

B:

Require consistent query tagging for important pipelines and dashboards. That safeguard is aimed at ANOTHER risk: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. It is less targeted than the control for: Serverless features can have separate meters outside traditional warehouse resource monitors.

C:

Test the policy with explicit role-switch fixtures and schema changes. That safeguard is aimed at ANOTHER risk: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. It is less targeted than the control for: Serverless features can have separate meters outside traditional warehouse resource monitors.

Question 197

A data-platform team must resolve: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. Which technical change most directly solves it?

  1. Configure an appropriate supported column-name matching or explicit transformation mapping.
  2. Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan.
  3. Define and test the correct CSV FILE FORMAT delimiter, quote and header handling for the staged data.
  4. Configure a supported Snowpipe pipe with notification-based auto-ingest for the external stage.

Explanation

Correct Answer

B:

Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan. This directly addresses the described Snowflake condition: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. The mechanism is: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files. Verify success using: Running the same unchanged file twice through the normal procedure does not create duplicate target rows.

Incorrect Answers

A:

Configure an appropriate supported column-name matching or explicit transformation mapping. That is suitable for a DIFFERENT Snowflake situation: An operations analyst assumes COPY INTO will map reordered source columns correctly solely because target columns have matching names. It does not directly resolve the current requirement: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run.

C:

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 monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run.

D:

Configure a supported Snowpipe pipe with notification-based auto-ingest for the external stage. That is suitable for a DIFFERENT Snowflake situation: A team runs hourly COPY scripts on files arriving every minute but needs near-continuous loading without scheduling a warehouse. It does not directly resolve the current requirement: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run.

Question 198

A Snowflake acceptance test follows this incident: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. What evidence most directly proves the correction?

  1. The stage lists the expected file and COPY INTO can read it with the intended format.
  2. A representative record maps its fields and header correctly without column shifts.
  3. Running the same unchanged file twice through the normal procedure does not create duplicate target rows.
  4. Session metadata shows the intended target account and query history records the application job.

Explanation

Correct Answer

C:

Running the same unchanged file twice through the normal procedure does not create duplicate target rows. This validates the relevant action: Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan. The underlying Snowflake behavior is: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.

Incorrect Answers

A:

The stage lists the expected file and COPY INTO can read it with the intended format. This evidence tests a DIFFERENT situation: An ingestion job expects a CSV file on a laptop to be accessible by COPY INTO immediately, without uploading it anywhere. The correction required in this case is: Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan.

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: Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan.

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: Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan.

Question 199

The data-platform team observes: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. Which architectural or processing fact matters most?

  1. Semi-structured JSON files require compatible parsing rather than CSV delimiter interpretation.
  2. Stage paths and COPY PATTERN can restrict which objects participate in a load.
  3. Snowpipe serverless ingestion uses pipe definitions and event notifications rather than a permanently running query warehouse.
  4. Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.

Explanation

Correct Answer

D:

Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files. This explains the condition: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. The corrective response is: Remove unnecessary forced reloading and use intended load-history behavior or an explicit deduplication plan.

Incorrect Answers

A:

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: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.

B:

Stage paths and COPY PATTERN can restrict which objects participate in a load. That mechanism explains a DIFFERENT Snowflake problem: A staged directory contains many unrelated feeds and COPY loads data intended for another department. Here the relevant mechanism instead is: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.

C:

Snowpipe serverless ingestion uses pipe definitions and event notifications rather than a permanently running query warehouse. That mechanism explains a DIFFERENT Snowflake problem: A team runs hourly COPY scripts on files arriving every minute but needs near-continuous loading without scheduling a warehouse. Here the relevant mechanism instead is: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.

Question 200

For a regulated healthcare organization, this issue must not recur: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. Which review control fits best?

  1. Review FORCE and PURGE options during production code changes.
  2. Test schema drift and reordered source files before each upstream release.
  3. Record recommended file sizing and compression for each data producer.
  4. Freeze export contracts with round-trip parser tests.

Explanation

Correct Answer

A:

Review FORCE and PURGE options during production code changes. This reduces recurrence of: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files. The verification should demonstrate: Running the same unchanged file twice through the normal procedure does not create duplicate target rows.

Incorrect Answers

B:

Test schema drift and reordered source files before each upstream release. That safeguard is aimed at ANOTHER risk: An operations analyst assumes COPY INTO will map reordered source columns correctly solely because target columns have matching names. It is less targeted than the control for: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.

C:

Record recommended file sizing and compression for each data producer. That safeguard is aimed at ANOTHER risk: An ingest job loads multi-gigabyte compressed files serially and expects maximum parallelism from the warehouse alone. It is less targeted than the control for: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.

D:

Freeze export contracts with round-trip parser tests. That safeguard is aimed at ANOTHER risk: A CSV unload intended for downstream SQL ingestion contains headers in some files and not others. It is less targeted than the control for: Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.