SnowPro Core COF-C03 Practice Test 26
Question 250
A Snowflake data team must make an implementation decision: A predictive service must decide whether generic standard compute or specialized inference capabilities are appropriate for model serving. Which choice addresses the requirement most directly?
- Package a supported Snowpark UDF with the correct runtime and package permissions.
- Use Snowflake Notebooks where available with governed compute and access.
- Use Streamlit in Snowflake for the approved internal application pattern.
- Benchmark Snowflake-supported ML inference and the available runtime against latency and security requirements.
Explanation
Correct Answer
D:Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries. The recommended choice specifically satisfies the required business outcome: A predictive service must decide whether generic standard compute or specialized inference capabilities are appropriate for model serving. Verify its use in the approved role and runtime context.
Incorrect Answers
A:Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions. That explains the role of “Package a supported Snowpark UDF with the correct runtime and package permissions”, but the present requirement calls for “Benchmark Snowflake-supported ML inference and the available runtime against latency and security requirements”: Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries.
B:Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports. That explains the role of “Use Snowflake Notebooks where available with governed compute and access”, but the present requirement calls for “Benchmark Snowflake-supported ML inference and the available runtime against latency and security requirements”: Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries.
C:Streamlit supports rapid Python application user interfaces with Snowflake-backed data and access controls. That explains the role of “Use Streamlit in Snowflake for the approved internal application pattern”, but the present requirement calls for “Benchmark Snowflake-supported ML inference and the available runtime against latency and security requirements”: Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries.
Question 251
An architecture reviewer proposes the following solution: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges. The business and technical requirement is: A Snowflake account should accept application connections only from approved office egress IP addresses. Which explanation most accurately justifies this choice?
- Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste.
- Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
- Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
- Network policies constrain permitted source addresses independently from SQL object grants.
Explanation
Correct Answer
D:Network policies constrain permitted source addresses independently from SQL object grants. This mechanism explains why the proposed action fits the scenario: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually. That explains the role of “Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste”, but the present requirement calls for “Network policies constrain permitted source addresses independently from SQL object grants”: This mechanism explains why the proposed action fits the scenario: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges.
B:This mechanism explains why the proposed action fits the scenario: Evaluate hourly credit usage across all warehouses and Snowflake-managed services. That explains the role of “Current warehouse size alone omits runtime, concurrency, and independent serverless consumption”, but the present requirement calls for “Network policies constrain permitted source addresses independently from SQL object grants”: This mechanism explains why the proposed action fits the scenario: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges.
C:This mechanism explains why the proposed action fits the scenario: Create and apply governed Snowflake object tags with approved allowed values where suitable. That explains the role of “Tags attach reusable metadata that downstream inventory and governance queries can evaluate”, but the present requirement calls for “Network policies constrain permitted source addresses independently from SQL object grants”: This mechanism explains why the proposed action fits the scenario: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges.
Question 252
An architecture reviewer proposes the following solution: Use LIST on the intended stage and file path with appropriate privileges. The business and technical requirement is: A team wants to see all staged files for a new source before executing the production load. Which explanation most accurately justifies this choice?
- Task DAGs express ordered execution and permit management of dependent pipeline steps.
- The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches.
- Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
- Listing stage contents validates location, pattern and access independently of a COPY operation.
Explanation
Correct Answer
D:Listing stage contents validates location, pattern and access independently of a COPY operation. This mechanism explains why the proposed action fits the scenario: Use LIST on the intended stage and file path with appropriate privileges. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Create a supported task graph with dependency links between tasks. That explains the role of “Task DAGs express ordered execution and permit management of dependent pipeline steps”, but the present requirement calls for “Listing stage contents validates location, pattern and access independently of a COPY operation”: This mechanism explains why the proposed action fits the scenario: Use LIST on the intended stage and file path with appropriate privileges.
B:This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration. That explains the role of “The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches”, but the present requirement calls for “Listing stage contents validates location, pattern and access independently of a COPY operation”: This mechanism explains why the proposed action fits the scenario: Use LIST on the intended stage and file path with appropriate privileges.
C:This mechanism explains why the proposed action fits the scenario: Define an auto-ingest Snowpipe with a stage and supported cloud event notifications. That explains the role of “Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification”, but the present requirement calls for “Listing stage contents validates location, pattern and access independently of a COPY operation”: This mechanism explains why the proposed action fits the scenario: Use LIST on the intended stage and file path with appropriate privileges.
Question 253
An architecture reviewer proposes the following solution: Inspect the Snowsight Query Profile and operator-level runtime statistics. The business and technical requirement is: An engineer wants to understand the most expensive stage of a Snowflake SQL plan rather than guess from final duration. Which explanation most accurately justifies this choice?
- STANDARD favors starting additional clusters to minimize query queuing as demand grows.
- Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans.
- Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
- Capacity should be evaluated against actual queue time, execution time and consumed credits.
Explanation
Correct Answer
B:Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans. This mechanism explains why the proposed action fits the scenario: Inspect the Snowsight Query Profile and operator-level runtime statistics. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing. That explains the role of “STANDARD favors starting additional clusters to minimize query queuing as demand grows”, but the present requirement calls for “Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans”: This mechanism explains why the proposed action fits the scenario: Inspect the Snowsight Query Profile and operator-level runtime statistics.
C:This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata. That explains the role of “Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually”, but the present requirement calls for “Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans”: This mechanism explains why the proposed action fits the scenario: Inspect the Snowsight Query Profile and operator-level runtime statistics.
D:This mechanism explains why the proposed action fits the scenario: Compare warehouse load, credits and query profile statistics before and after configuration changes. That explains the role of “Capacity should be evaluated against actual queue time, execution time and consumed credits”, but the present requirement calls for “Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans”: This mechanism explains why the proposed action fits the scenario: Inspect the Snowsight Query Profile and operator-level runtime statistics.
Question 254
An architecture reviewer proposes the following solution: Use supported UNDROP SCHEMA within the configured Time Travel window. The business and technical requirement is: A team wants to recover a mistakenly deleted schema and all its eligible objects without manually reconstructing DDL. Which explanation most accurately justifies this choice?
- Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model.
- Time Travel plus cloning can capture retained historical state for independent testing when object support permits.
- Provider-owned grants control consumer access independently of data persistence.
- Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
Explanation
Correct Answer
D:Time Travel object recovery can restore eligible dropped schema structures while retention is valid. This mechanism explains why the proposed action fits the scenario: Use supported UNDROP SCHEMA within the configured Time Travel window. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. That explains the role of “Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model”, but the present requirement calls for “Time Travel object recovery can restore eligible dropped schema structures while retention is valid”: This mechanism explains why the proposed action fits the scenario: Use supported UNDROP SCHEMA within the configured Time Travel window.
B:This mechanism explains why the proposed action fits the scenario: Create an eligible zero-copy clone at the supported Time Travel point and verify its schema. That explains the role of “Time Travel plus cloning can capture retained historical state for independent testing when object support permits”, but the present requirement calls for “Time Travel object recovery can restore eligible dropped schema structures while retention is valid”: This mechanism explains why the proposed action fits the scenario: Use supported UNDROP SCHEMA within the configured Time Travel window.
C:This mechanism explains why the proposed action fits the scenario: Remove that consumer from the authorized share or revoke the relevant shared object grants. That explains the role of “Provider-owned grants control consumer access independently of data persistence”, but the present requirement calls for “Time Travel object recovery can restore eligible dropped schema structures while retention is valid”: This mechanism explains why the proposed action fits the scenario: Use supported UNDROP SCHEMA within the configured Time Travel window.
Question 255
An architecture reviewer proposes the following solution: Organize distinct databases or accounts with documented roles and change promotion boundaries. The business and technical requirement is: A company needs separate development and production data environments while reusing standard governance patterns. Which explanation most accurately justifies this choice?
- Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
- Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings.
- Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
- ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication.
Explanation
Correct Answer
A:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. This mechanism explains why the proposed action fits the scenario: Organize distinct databases or accounts with documented roles and change promotion boundaries. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use a PERMANENT table with approved Time Travel retention. That explains the role of “Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings”, but the present requirement calls for “Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone”: This mechanism explains why the proposed action fits the scenario: Organize distinct databases or accounts with documented roles and change promotion boundaries.
C:This mechanism explains why the proposed action fits the scenario: Use a TEMPORARY table with an appropriately scoped session. That explains the role of “Temporary tables have session lifetime, unlike permanent tables that persist independently of a session”, but the present requirement calls for “Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone”: This mechanism explains why the proposed action fits the scenario: Organize distinct databases or accounts with documented roles and change promotion boundaries.
D:This mechanism explains why the proposed action fits the scenario: Configure an approved Snowflake ODBC driver and connection context. That explains the role of “ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication”, but the present requirement calls for “Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone”: This mechanism explains why the proposed action fits the scenario: Organize distinct databases or accounts with documented roles and change promotion boundaries.
Question 256
An architecture reviewer proposes the following solution: Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition. The business and technical requirement is: Sensitive regulatory data must use private connectivity rather than traversing a public internet endpoint for supported clients. Which explanation most accurately justifies this choice?
- Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing.
- Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds.
- A view does not automatically remove column-level policy obligations inherited from its sources.
- Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
Explanation
Correct Answer
A:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. This mechanism explains why the proposed action fits the scenario: Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Configure and monitor a resource monitor with appropriate credit triggers and warehouse association. That explains the role of “Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds”, but the present requirement calls for “Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing”: This mechanism explains why the proposed action fits the scenario: Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition.
C:This mechanism explains why the proposed action fits the scenario: Retain masking enforcement on underlying governed columns and test effective role conditions. That explains the role of “A view does not automatically remove column-level policy obligations inherited from its sources”, but the present requirement calls for “Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing”: This mechanism explains why the proposed action fits the scenario: Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition.
D:This mechanism explains why the proposed action fits the scenario: Evaluate hourly credit usage across all warehouses and Snowflake-managed services. That explains the role of “Current warehouse size alone omits runtime, concurrency, and independent serverless consumption”, but the present requirement calls for “Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing”: This mechanism explains why the proposed action fits the scenario: Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition.
Question 257
An architecture reviewer proposes the following solution: Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema. The business and technical requirement is: A file-loading task fails because the target column names differ in case from incoming Parquet fields. Which explanation most accurately justifies this choice?
- Private network access relies on cloud routing and DNS as well as Snowflake account policies.
- File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe.
- Name-based matching can align supported file columns without depending on file position alone.
- Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
Explanation
Correct Answer
C:Name-based matching can align supported file columns without depending on file position alone. This mechanism explains why the proposed action fits the scenario: Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint. That explains the role of “Private network access relies on cloud routing and DNS as well as Snowflake account policies”, but the present requirement calls for “Name-based matching can align supported file columns without depending on file position alone”: This mechanism explains why the proposed action fits the scenario: Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema.
B:This mechanism explains why the proposed action fits the scenario: Check pipe status, stage path and cloud notification integration for missed messages. That explains the role of “File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe”, but the present requirement calls for “Name-based matching can align supported file columns without depending on file position alone”: This mechanism explains why the proposed action fits the scenario: Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema.
D:This mechanism explains why the proposed action fits the scenario: Create a Snowflake task with an appropriate schedule and execution context. That explains the role of “Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary”, but the present requirement calls for “Name-based matching can align supported file columns without depending on file position alone”: This mechanism explains why the proposed action fits the scenario: Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema.
Question 258
An architecture reviewer proposes the following solution: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid. The business and technical requirement is: A table uses a transformation on the filter column and pruning disappears compared with a simple range predicate. Which explanation most accurately justifies this choice?
- MERGE combines conditional matched and unmatched DML paths in one operation.
- ECONOMY prioritizes fuller use of existing clusters before starting more compute.
- Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
- FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
Explanation
Correct Answer
C:Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter. This mechanism explains why the proposed action fits the scenario: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use MERGE with defined match keys and explicit update and insert branches. That explains the role of “MERGE combines conditional matched and unmatched DML paths in one operation”, but the present requirement calls for “Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter”: This mechanism explains why the proposed action fits the scenario: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid.
B:This mechanism explains why the proposed action fits the scenario: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits. That explains the role of “ECONOMY prioritizes fuller use of existing clusters before starting more compute”, but the present requirement calls for “Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter”: This mechanism explains why the proposed action fits the scenario: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid.
D:This mechanism explains why the proposed action fits the scenario: Use LATERAL FLATTEN against the relevant VARIANT path. That explains the role of “FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values”, but the present requirement calls for “Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter”: This mechanism explains why the proposed action fits the scenario: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid.
Question 259
An architecture reviewer proposes the following solution: Create a Secure Data Share with authorized objects and add the approved consumer account. The business and technical requirement is: A provider wants a partner already using Snowflake to read a governed dataset without copying files into the partner's cloud account. Which explanation most accurately justifies this choice?
- Replication propagates supported database state between accounts rather than rebuilding tables through files.
- Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially.
- Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
- Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
Explanation
Correct Answer
D:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. This mechanism explains why the proposed action fits the scenario: Create a Secure Data Share with authorized objects and add the approved consumer account. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Configure authorized database replication and monitor refresh status. That explains the role of “Replication propagates supported database state between accounts rather than rebuilding tables through files”, but the present requirement calls for “Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy”: This mechanism explains why the proposed action fits the scenario: Create a Secure Data Share with authorized objects and add the approved consumer account.
B:This mechanism explains why the proposed action fits the scenario: Write to the clone using its own object name and verify copy-on-write isolation. That explains the role of “Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially”, but the present requirement calls for “Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy”: This mechanism explains why the proposed action fits the scenario: Create a Secure Data Share with authorized objects and add the approved consumer account.
C:This mechanism explains why the proposed action fits the scenario: Explain that Fail-safe is Snowflake-assisted disaster recovery, not a user-queryable historical archive. That explains the role of “Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel”, but the present requirement calls for “Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy”: This mechanism explains why the proposed action fits the scenario: Create a Secure Data Share with authorized objects and add the approved consumer account.
Question 260
An architecture reviewer proposes the following solution: Execute supported Snowflake SQL transformations using an appropriate compute warehouse. The business and technical requirement is: A data analyst wants to test transformation results quickly without moving source data to a local laptop. Which explanation most accurately justifies this choice?
- Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
- Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds.
- Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently.
- Materialized views persist selected computed results but impose storage and maintenance costs.
Explanation
Correct Answer
A:Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls. This mechanism explains why the proposed action fits the scenario: Execute supported Snowflake SQL transformations using an appropriate compute warehouse. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously. That explains the role of “Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds”, but the present requirement calls for “Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls”: This mechanism explains why the proposed action fits the scenario: Execute supported Snowflake SQL transformations using an appropriate compute warehouse.
C:This mechanism explains why the proposed action fits the scenario: Use Snowflake's compute-storage separation as the architectural explanation. That explains the role of “Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently”, but the present requirement calls for “Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls”: This mechanism explains why the proposed action fits the scenario: Execute supported Snowflake SQL transformations using an appropriate compute warehouse.
D:This mechanism explains why the proposed action fits the scenario: Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost. That explains the role of “Materialized views persist selected computed results but impose storage and maintenance costs”, but the present requirement calls for “Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls”: This mechanism explains why the proposed action fits the scenario: Execute supported Snowflake SQL transformations using an appropriate compute warehouse.