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 28

Question 270

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

  1. The audit identifies query principals and accessed objects for representative governed tests.
  2. Newly tagged sensitive test columns inherit the intended masking behavior where supported.
  3. The affected identity cannot read the restricted view through any remaining authorized role chain.
  4. Authorized corporate connections succeed while an unapproved test source is rejected.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

Newly tagged sensitive test columns inherit the intended masking behavior where supported. This evidence tests a DIFFERENT situation: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. The correction required in this case is: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.

C:

The affected identity cannot read the restricted view through any remaining authorized role chain. This evidence tests a DIFFERENT situation: A data steward revokes a user's role but their previous worksheet continues to query an authorized view under a different active role. The correction required in this case is: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.

D:

Authorized corporate connections succeed while an unapproved test source is rejected. This evidence tests a DIFFERENT situation: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. The correction required in this case is: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.

Question 271

In a case affecting a telecommunications provider, this issue appears: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. What explains it?

  1. Masking policies evaluate authorized context at query time rather than copying a second redacted table.
  2. Usage, access history and cost metering contain different evidence about data access.
  3. An effective entitlement may arrive through multiple direct or inherited roles.
  4. Federated authentication requires a consistent identity mapping independently of database grants.

Explanation

Correct Answer

B:

Usage, access history and cost metering contain different evidence about data access. This explains the condition: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. The corrective response is: Use suitable ACCOUNT_USAGE or access-history sources with required privileges and known reporting lag.

Incorrect Answers

A:

Masking policies evaluate authorized context at query time rather than copying a second redacted table. That mechanism explains a DIFFERENT Snowflake problem: A human resources dataset contains salary amounts, and a general analyst role should see only masked values. Here the relevant mechanism instead is: Usage, access history and cost metering contain different evidence about data access.

C:

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: Usage, access history and cost metering contain different evidence about data access.

D:

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: Usage, access history and cost metering contain different evidence about data access.

Question 272

After remediating the Snowflake issue, the team reviews: A data owner requests a clean audit of who accessed a sensitive table, but the team looks only at warehouse spend charts. Which recurring control is most targeted?

  1. Test layered access with both allowed and denied user cases.
  2. Review automated classification changes and policy-tag associations regularly.
  3. Document audit view latency, retention and roles needed to query access history.
  4. Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless.

Explanation

Correct Answer

C:

Document audit view latency, retention and roles needed to query access history. This reduces recurrence of: Usage, access history and cost metering contain different evidence about data access. The verification should demonstrate: The audit identifies query principals and accessed objects for representative governed tests.

Incorrect Answers

A:

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: Usage, access history and cost metering contain different evidence about data access.

B:

Review automated classification changes and policy-tag associations regularly. That safeguard is aimed at ANOTHER risk: An enterprise classifies PII in columns but ignores data classification tags when assigning masking rules. It is less targeted than the control for: Usage, access history and cost metering contain different evidence about data access.

D:

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: Usage, access history and cost metering contain different evidence about data access.

Question 273

At a consumer marketplace, a Snowflake implementation review finds: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. Which action best addresses this requirement?

  1. Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately.
  2. Model compute, active/historical storage, and managed service meters independently before archiving the system.
  3. Inspect query profile and warehouse cache behavior before implementing aggressive resizes.
  4. Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.

Explanation

Correct Answer

A:

Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately. This directly addresses the described Snowflake condition: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. The mechanism is: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill. Verify success using: Representative project queries appear with traceable tags, allowing a reasoned chargeback allocation.

Incorrect Answers

B:

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 finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse.

C:

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 finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse.

D:

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: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse.

Question 274

After the approved change, engineers revisit: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. Which result establishes the intended state?

  1. The report shows an explicit freshness indicator and reconciles delayed cost rows later.
  2. Representative project queries appear with traceable tags, allowing a reasoned chargeback allocation.
  3. The monitor records the designated warehouse's consumption and triggers alerts or actions at test thresholds.
  4. Test queries enforce required column protections and disallow unapproved data export paths.

Explanation

Correct Answer

B:

Representative project queries appear with traceable tags, allowing a reasoned chargeback allocation. This validates the relevant action: Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately. The underlying Snowflake behavior is: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.

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: Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately.

C:

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: Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately.

D:

Test queries enforce required column protections and disallow unapproved data export paths. This evidence tests a DIFFERENT situation: An analyst creates an external function that exports restricted data even though its normal table queries are masked. The correction required in this case is: Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately.

Question 275

A root-cause investigation considers: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. What is the most applicable explanation?

  1. Warehouse suspension does not delete persisted data or eliminate unrelated storage charges.
  2. Serverless features can have separate meters outside traditional warehouse resource monitors.
  3. Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.
  4. IP allowlisting and private network attachment solve different transport security requirements.

Explanation

Correct Answer

C:

Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill. This explains the condition: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. The corrective response is: Create approved query tags and resource ownership conventions, then analyze query and metering telemetry appropriately.

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: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.

B:

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: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.

D:

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: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.

Question 276

During operational handoff for this problem: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. Which guardrail should be included?

  1. Maintain a cost-category inventory whenever pipelines migrate from warehouses to serverless.
  2. Label telemetry recency and use validated time windows in chargeback reports.
  3. Periodically verify new-object privilege behavior and future-grant overlap.
  4. Require consistent query tagging for important pipelines and dashboards.

Explanation

Correct Answer

D:

Require consistent query tagging for important pipelines and dashboards. This reduces recurrence of: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill. The verification should demonstrate: Representative project queries appear with traceable tags, allowing a reasoned chargeback allocation.

Incorrect Answers

A:

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: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.

B:

Label telemetry recency and use validated time windows in chargeback reports. That safeguard is aimed at ANOTHER risk: A cost dashboard immediately queries ACCOUNT_USAGE views after a warehouse change and declares telemetry missing. It is less targeted than the control for: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.

C:

Periodically verify new-object privilege behavior and future-grant overlap. That safeguard is aimed at ANOTHER risk: A project grants future objects manually each week and a newly created table is invisible to its application role. It is less targeted than the control for: Query attribution metadata improves workload-level cost analysis but does not alter the underlying warehouse bill.

Question 277

A data-platform team must resolve: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows. Which technical change most directly solves it?

  1. Use a JSON file format and appropriate VARIANT target or extraction logic for the staged payload.
  2. Choose a supported ON_ERROR strategy consistent with data-quality and audit requirements.
  3. Reevaluate source file size and supported parallel loading strategy before increasing warehouse size.
  4. Evaluate a supported Kafka connector or Snowpipe Streaming ingestion path based on latency and throughput.

Explanation

Correct Answer

B:

Choose a supported ON_ERROR strategy consistent with data-quality and audit requirements. This directly addresses the described Snowflake condition: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows. The mechanism is: COPY error-handling options alter treatment of malformed file rows and must match governance requirements. Verify success using: A controlled bad-row fixture yields the approved failure or continue behavior and observable load results.

Incorrect Answers

A:

Use a JSON file format and appropriate VARIANT target or extraction logic for the staged payload. That is suitable for a DIFFERENT Snowflake situation: An engineer sets JSON FILE FORMAT to CSV and loads a nested event record into a one-column raw table. It does not directly resolve the current requirement: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows.

C:

Reevaluate source file size and supported parallel loading strategy before increasing warehouse size. That is suitable for a DIFFERENT Snowflake situation: An ingest job loads multi-gigabyte compressed files serially and expects maximum parallelism from the warehouse alone. It does not directly resolve the current requirement: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows.

D:

Evaluate a supported Kafka connector or Snowpipe Streaming ingestion path based on latency and throughput. That is suitable for a DIFFERENT Snowflake situation: A data app needs to ingest events from Kafka but engineers build one file per message and a new warehouse COPY for each row. It does not directly resolve the current requirement: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows.

Question 278

A Snowflake acceptance test follows this incident: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows. What evidence most directly proves the correction?

  1. A deliberately reordered input sample lands values in the correct target columns.
  2. The validation identifies a deliberately malformed fixture without modifying production data.
  3. A controlled bad-row fixture yields the approved failure or continue behavior and observable load results.
  4. The pipeline loads representative events with measured latency and manageable operational overhead.

Explanation

Correct Answer

C:

A controlled bad-row fixture yields the approved failure or continue behavior and observable load results. This validates the relevant action: Choose a supported ON_ERROR strategy consistent with data-quality and audit requirements. The underlying Snowflake behavior is: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.

Incorrect Answers

A:

A deliberately reordered input sample lands values in the correct target columns. This evidence tests a DIFFERENT situation: An operations analyst assumes COPY INTO will map reordered source columns correctly solely because target columns have matching names. The correction required in this case is: Choose a supported ON_ERROR strategy consistent with data-quality and audit requirements.

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: Choose a supported ON_ERROR strategy consistent with data-quality and audit requirements.

D:

The pipeline loads representative events with measured latency and manageable operational overhead. This evidence tests a DIFFERENT situation: A data app needs to ingest events from Kafka but engineers build one file per message and a new warehouse COPY for each row. The correction required in this case is: Choose a supported ON_ERROR strategy consistent with data-quality and audit requirements.

Question 279

The data-platform team observes: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows. Which architectural or processing fact matters most?

  1. Semi-structured JSON files require compatible parsing rather than CSV delimiter interpretation.
  2. Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files.
  3. Snowflake unloading uses COPY INTO location rather than PUT, which stages local source files.
  4. COPY error-handling options alter treatment of malformed file rows and must match governance requirements.

Explanation

Correct Answer

D:

COPY error-handling options alter treatment of malformed file rows and must match governance requirements. This explains the condition: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows. The corrective response is: Choose a supported ON_ERROR strategy consistent with data-quality and audit requirements.

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: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.

B:

Snowflake bulk COPY maintains file-load metadata to help avoid reloading already processed staged files. That mechanism explains a DIFFERENT Snowflake problem: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. Here the relevant mechanism instead is: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.

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 error-handling options alter treatment of malformed file rows and must match governance requirements.

Question 280

For a public-sector reporting unit, this issue must not recur: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows. Which review control fits best?

  1. Track rejected data and reconcile source counts after partial loads.
  2. Validate representative nested arrays, nulls and malformed JSON before production loads.
  3. Audit cloud trust relationships and allowed stage prefixes before onboarding new data.
  4. Keep environment-specific account identifiers out of source-code assumptions.

Explanation

Correct Answer

A:

Track rejected data and reconcile source counts after partial loads. This reduces recurrence of: COPY error-handling options alter treatment of malformed file rows and must match governance requirements. The verification should demonstrate: A controlled bad-row fixture yields the approved failure or continue behavior and observable load results.

Incorrect Answers

B:

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 error-handling options alter treatment of malformed file rows and must match governance requirements.

C:

Audit cloud trust relationships and allowed stage prefixes before onboarding new data. That safeguard is aimed at ANOTHER risk: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors. It is less targeted than the control for: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.

D:

Keep environment-specific account identifiers out of source-code assumptions. That safeguard is aimed at ANOTHER risk: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. It is less targeted than the control for: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.