Snowflake SnowPro Core COF-C03 Practice Test 36 - Prepaway
Practice Exams:

Pass Snowflake SnowPro Core COF-C03 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$14.99
$74.99 $89.98

SnowPro Core COF-C03 Premium Bundle


  • Premium File 116 Questions & Answers. Last update: Nov 17, 2026
  • Study Guide 222 Pages

Snowflake SnowPro Core COF-C03 Practice Test 36

Question 350

A Snowflake analyst supporting student analytics and research-grant reporting at a public university intends: Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. The reported condition is: A large sort query takes longer as datasets grow and analysts blame partition pruning without checking memory pressure. Identify the most decisive diagnostic record.

  1. Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly.
  2. Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent.
  3. Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads.
  4. Query Profile shows a data scan and row access predicates, not a metadata-only computation.

Correct Answer: A

Explanation

A.

Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. The documented change is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. The acceptance check is whether a representative query reduces spill while preserving results and stays within cost limits.

B.

Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. This choice does not explain the observed failure mechanism. For student analytics and research-grant reporting at a public university, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The better-matched action is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.

C.

Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. This choice does not explain the observed failure mechanism. For student analytics and research-grant reporting at a public university, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The better-matched action is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.

D.

Query Profile shows a data scan and row access predicates, not a metadata-only computation. This choice does not explain the observed failure mechanism. For student analytics and research-grant reporting at a public university, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The better-matched action is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.

Question 351

For cargo scans and berth utilization reports at a container port operator, Snowflake administrators supporting cargo scans and berth utilization reports report: A role investigation finds a user can access a table even after the primary active role lost its SELECT privilege. Their diagnostic record states: Session diagnostics show an enabled secondary role still grants access to the table. Which corrective action is best supported by the evidence?

  1. Grant the database role to an appropriate account role and grant that account role to approved users.
  2. Grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants.
  3. Reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout.
  4. Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles.

Correct Answer: D

Explanation

A.

Grant the database role to an appropriate account role and grant that account role to approved users. Database roles scope database privileges and are activated through account-role inheritance. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. For this incident, review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles.

B.

Grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants. Snowflake role authorization must cover both referenced data and chosen execution warehouse. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. For this incident, review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles.

C.

Reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. Network policies add source-network restrictions independent of SQL role grants. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. For this incident, review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles.

D.

Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. Snowflake authorization can aggregate primary and enabled secondary role privileges. Verify that the user loses unauthorized read access in all permitted role combinations while approved data remains accessible.

Question 352

During a change review for asset maintenance logs and quality assurance reports at a water supplier, the team finds: An analyst downsizes warehouse compute hoping to reduce a growing table-storage bill caused by duplicate historical records. Investigation shows: Consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. What is the most appropriate next Snowflake action?

  1. Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test.
  2. Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries.
  3. Separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely.
  4. Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights.

Correct Answer: C

Explanation

A.

Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. Snowflake separates independently scalable query compute from persistent managed table storage. For asset maintenance logs and quality assurance reports at a water supplier, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. Instead, separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely.

B.

Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries. Independent virtual warehouses support workload isolation over shared centralized data. For asset maintenance logs and quality assurance reports at a water supplier, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. Instead, separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely.

C.

Separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely. For asset maintenance logs and quality assurance reports at a water supplier, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. Compute-credit consumption and managed storage usage are distinct cost drivers. A confirming result should show that retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes.

D.

Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. Interactive development tools still require supported execution compute and role context. For asset maintenance logs and quality assurance reports at a water supplier, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. Instead, separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely.

Question 353

An operations review of network event logs and account churn models at a telecommunications provider reports: An on-call engineer promises instant SQL access to data beyond Time Travel because permanent tables have Fail-safe. The differentiating observation is: UNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. Which proposed fix and test pair most directly addresses the failure?

  1. Review supported table type, edition, retention settings and backup strategy against the required recovery objective. — verification: An allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated.
  2. Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. — verification: A governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.
  3. Configure a supported secure data share with least privilege and document relevant region/account constraints. — verification: An authorized consumer queries the shared object while no unmanaged full dataset export is required.
  4. Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. — verification: The recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

Correct Answer: D

Explanation

A.

Review supported table type, edition, retention settings and backup strategy against the required recovery objective. Verify that an allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated. This action and its verification do not address the identified failure together. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The appropriate correction is to document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Confirm that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

B.

Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. Verify that a governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle. This action and its verification do not address the identified failure together. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The appropriate correction is to document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Confirm that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

C.

Configure a supported secure data share with least privilege and document relevant region/account constraints. Verify that an authorized consumer queries the shared object while no unmanaged full dataset export is required. This action and its verification do not address the identified failure together. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The appropriate correction is to document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Confirm that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

D.

Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Verify that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.

Question 354

For citizen service reporting and licensed contractor data at a municipal authority, Snowflake administrators supporting citizen service reporting and licensed contractor data report: A virtual warehouse consumes credits overnight despite no queries and the finance team assumes every query has become expensive. Their diagnostic record states: Metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. Which corrective action is best supported by the evidence?

  1. Enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.
  2. Assign supported resource monitor coverage and alert thresholds to the intended warehouse resources and owners.
  3. Combine relevant account usage and serverless cost views with warehouse metrics for a complete workload accounting.
  4. Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers.

Correct Answer: A

Explanation

A.

Enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs. For citizen service reporting and licensed contractor data at a municipal authority, metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. Warehouse credit costs can accrue during idle running time separately from actual query work. A suitable check should show that after an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully.

B.

Assign supported resource monitor coverage and alert thresholds to the intended warehouse resources and owners. Resource monitors act on associated virtual-warehouse credit usage rather than any unrelated account cost automatically. For citizen service reporting and licensed contractor data at a municipal authority, metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. The better-matched action is to enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.

C.

Combine relevant account usage and serverless cost views with warehouse metrics for a complete workload accounting. Snowflake total compute cost includes serverless services and is not always visible in warehouse metering. For citizen service reporting and licensed contractor data at a municipal authority, metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. The better-matched action is to enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.

D.

Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. Dynamic masking can enforce column-value protection according to access context. For citizen service reporting and licensed contractor data at a municipal authority, metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. The better-matched action is to enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.

Question 355

For instrument results and governed case metadata at a medical testing laboratory, an engineer diagnoses: A report team expects a repeated SELECT to use the persisted result cache but keeps modifying the SQL text and underlying data. The observation is: Query history shows new execution work and source-table modification timestamps between otherwise similar report runs. The response is: Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Which principle best explains the decision?

  1. Snowflake persisted query results are reused only when the required consistency and context conditions are met.
  2. Query result reuse depends on relevant session and security conditions as well as SQL text.
  3. Metadata-derived results cannot bypass filters needed for correct authorized query semantics.
  4. Query optimization governance needs observable workload attribution, not only raw credits.

Correct Answer: A

Explanation

A.

Snowflake persisted query results are reused only when the required consistency and context conditions are met. For instrument results and governed case metadata at a medical testing laboratory, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. To correct it, inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. A successful test shows an unchanged eligible repeated query demonstrates the expected cache behavior without stale results.

B.

Query result reuse depends on relevant session and security conditions as well as SQL text. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. The controlling principle is that Snowflake persisted query results are reused only when the required consistency and context conditions are met.

C.

Metadata-derived results cannot bypass filters needed for correct authorized query semantics. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. The controlling principle is that Snowflake persisted query results are reused only when the required consistency and context conditions are met.

D.

Query optimization governance needs observable workload attribution, not only raw credits. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. The controlling principle is that Snowflake persisted query results are reused only when the required consistency and context conditions are met.

Question 356

The assembly sensor events and warranty reports environment at an automotive parts manufacturer has an incident: Two analysts compare query cache savings using different roles and assume an exact result cache hit is universally shareable. The difference-making observation is: Query contexts differ in security and session conditions and tests do not control source change timing. Choose the most defensible corrective response.

  1. Benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.
  2. Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse.
  3. Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it.
  4. Deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.

Correct Answer: A

Explanation

A.

Benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results. For assembly sensor events and warranty reports at an automotive parts manufacturer, query contexts differ in security and session conditions and tests do not control source change timing. Query result reuse depends on relevant session and security conditions as well as SQL text. A confirming result should show that repeated qualified queries show understood result-cache behavior with authorization preserved.

B.

Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. This choice does not explain the observed failure mechanism. For assembly sensor events and warranty reports at an automotive parts manufacturer, query contexts differ in security and session conditions and tests do not control source change timing. Instead, benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.

C.

Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. This choice does not explain the observed failure mechanism. For assembly sensor events and warranty reports at an automotive parts manufacturer, query contexts differ in security and session conditions and tests do not control source change timing. Instead, benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.

D.

Deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE. This choice does not explain the observed failure mechanism. For assembly sensor events and warranty reports at an automotive parts manufacturer, query contexts differ in security and session conditions and tests do not control source change timing. Instead, benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.

Question 357

The Snowflake data engineering team at a wholesale retailer plans to: Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. The issue affecting sales aggregates and supplier order tracking is: A reporting team expects a fast metadata count on a filtered secured view but the query scans underlying protected rows. Which finding best distinguishes this cause from other Snowflake failures?

  1. Query Profile shows a data scan and row access predicates, not a metadata-only computation.
  2. Query history shows new execution work and source-table modification timestamps between otherwise similar report runs.
  3. The first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse.
  4. A sample event contains multiple nested elements and the output row count stays one per parent regardless of item count.

Correct Answer: A

Explanation

A.

Query Profile shows a data scan and row access predicates, not a metadata-only computation. Metadata-derived results cannot bypass filters needed for correct authorized query semantics. The corresponding fix is to use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. A successful test should show that the count respects row-level security and meets the approved performance target; the reported setting is: the snowflake data engineering team at a wholesale retailer plans to: use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies.

B.

Query history shows new execution work and source-table modification timestamps between otherwise similar report runs. Snowflake persisted query results are reused only when the required consistency and context conditions are met. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows a data scan and row access predicates, not a metadata-only computation. To address this, use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies.

C.

The first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. Virtual warehouse local data cache behavior differs from the persisted query result cache. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows a data scan and row access predicates, not a metadata-only computation. To address this, use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies.

D.

A sample event contains multiple nested elements and the output row count stays one per parent regardless of item count. Flattening nested semi-structured arrays changes row granularity and requires cardinality awareness. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows a data scan and row access predicates, not a metadata-only computation. To address this, use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies.

Question 358

For booking data marts and occupancy forecasts at a hospitality chain, an engineer diagnoses: An analyst enables search optimization on a huge table to speed a report that aggregates most records every night. The observation is: Query Profile shows broad scans with few selective equality or point lookup predicates. The response is: Choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking. Which principle best explains the decision?

  1. Search optimization is designed for selective access patterns, not all-table analytic scans.
  2. Clustering keys are workload-specific optimizations and are not universally beneficial.
  3. Extra query compute cannot correct incorrect SQL semantics.
  4. Pruning efficiency depends on how filter predicates interact with micro-partition metadata.

Correct Answer: A

Explanation

A.

Search optimization is designed for selective access patterns, not all-table analytic scans. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. The documented change is to choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking. A successful test shows the aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense.

B.

Clustering keys are workload-specific optimizations and are not universally beneficial. This choice does not explain the observed failure mechanism. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. The controlling principle is that search optimization is designed for selective access patterns, not all-table analytic scans.

C.

Extra query compute cannot correct incorrect SQL semantics. This choice does not explain the observed failure mechanism. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. The controlling principle is that search optimization is designed for selective access patterns, not all-table analytic scans.

D.

Pruning efficiency depends on how filter predicates interact with micro-partition metadata. This choice does not explain the observed failure mechanism. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. The controlling principle is that search optimization is designed for selective access patterns, not all-table analytic scans.

Question 359

A Snowflake analyst supporting factory telemetry and supplier quality dashboards at a manufacturing group intends: Choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation. The reported condition is: A team tries to replace a procedural multi-step orchestration with a scalar UDF even though it must run approved statements and coordinate task state. Identify the most decisive diagnostic record.

  1. The application session explicitly sets the same parameter and its effective value differs from the new account default.
  2. The proposed UDF contract expects state-changing workflow control rather than a per-row returned value.
  3. Privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation.
  4. Feature evaluation indicates the required control is not available at the current account edition and its trial behavior differs from production.

Correct Answer: B

Explanation

A.

The application session explicitly sets the same parameter and its effective value differs from the new account default. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, the proposed UDF contract expects state-changing workflow control rather than a per-row returned value. For this incident, choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation.

B.

The proposed UDF contract expects state-changing workflow control rather than a per-row returned value. Snowflake functions and procedures have different execution contracts and appropriate use cases. To correct it, choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation. Verification should establish that a test execution completes the controlled multi-step process with an auditable outcome and no unsupported UDF side effects.

C.

Privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, the proposed UDF contract expects state-changing workflow control rather than a per-row returned value. For this incident, choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation.

D.

Feature evaluation indicates the required control is not available at the current account edition and its trial behavior differs from production. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, the proposed UDF contract expects state-changing workflow control rather than a per-row returned value. For this incident, choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation.

Question 360

The Snowflake data engineering team at a hospital network plans to: Restore a selective supported date-range predicate and compare query profile pruning under reproducible data. The issue affecting care utilization metrics and de-identified clinical reporting is: A monthly report scans the full sales history after its date predicate was rewritten as a formatted string expression. Which finding best distinguishes this cause from other Snowflake failures?

  1. Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly.
  2. Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers.
  3. Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent.
  4. Query Profile shows a data scan and row access predicates, not a metadata-only computation.

Correct Answer: C

Explanation

A.

Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. For care utilization metrics and de-identified clinical reporting at a hospital network, query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. Instead, restore a selective supported date-range predicate and compare query profile pruning under reproducible data.

B.

Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Join cardinality affects both query cost and semantic result correctness. For care utilization metrics and de-identified clinical reporting at a hospital network, query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. Instead, restore a selective supported date-range predicate and compare query profile pruning under reproducible data.

C.

Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. Pruning efficiency depends on how filter predicates interact with micro-partition metadata. To address this, restore a selective supported date-range predicate and compare query profile pruning under reproducible data. Confirm that same expected rows return with fewer partitions scanned and lower measured query cost.

D.

Query Profile shows a data scan and row access predicates, not a metadata-only computation. Metadata-derived results cannot bypass filters needed for correct authorized query semantics. For care utilization metrics and de-identified clinical reporting at a hospital network, query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. Instead, restore a selective supported date-range predicate and compare query profile pruning under reproducible data.

SnowPro Core COF-C03 Practice Tests