Snowflake SnowPro Core COF-C03 Practice Test 46
Question 450
[Query performance review] The team proposes: Create a scoped SQL user-defined function and grant the appropriate usage privileges to consuming roles. Its actual requirement is: A performance engineer is benchmarking representative queries before accepting changes. Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely.
- SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
- A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
- TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
Explanation
Correct Answer
B:A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row. This is an outcome test of the specified sql udf reusable expression action under the query performance review conditions.
Incorrect Answers
A:In this query performance review context, The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely. This is an outcome for a different requirement: An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. It cannot by itself validate the proposed sql udf reusable expression action; the appropriate test is: SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
C:A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows. This is an outcome for a different requirement: One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. It cannot by itself validate the proposed sql udf reusable expression action; the appropriate test is: SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
D:In this query performance review context, TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule. This is an outcome for a different requirement: A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. It cannot by itself validate the proposed sql udf reusable expression action; the appropriate test is: SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
Question 451
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. A support application must retrieve relevant passages from a collection of policy documents to ground an answer. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
- Assume deploying the app bypasses database grants and makes every protected table readable to all anonymous visitors.
- Ask Cortex Analyst to index and retrieve all document paragraphs without configuring a document search service.
- Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
Explanation
Correct Answer
C:The supportable direction is: Build a supported Cortex Search service over appropriately prepared text and filterable metadata. Ask Cortex Analyst to index and retrieve all document paragraphs without configuring a document search service.
Incorrect Answers
A:That is a mistake for a different search optimization selective lookup task, where An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. Under architecture planning workshop conditions, Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
B:That is a mistake for a different streamlit app inside snowflake task, where An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. It does not directly defeat the present cortex search document retrieval requirement, whose proper treatment is: Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
D:That is a mistake for a different cortex generative text operation task, where A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. Under architecture planning workshop conditions, Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
Question 452
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Use FORCE=TRUE on every retry without any deduplication plan and assume no extra records can appear.
- Export the entire database to CSV and reload it as the only supported cloning approach.
- Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
- Use ON_ERROR=CONTINUE and call the loaded row count complete without logging the rejected records.
Explanation
Correct Answer
D:The discriminating technical reason is: COPY error behavior determines whether load execution aborts or continues past bad rows; strict policy fits completeness-sensitive feeds. The supportable direction is: Select a strict COPY INTO error policy such as ABORT_STATEMENT and reconcile source counts before releasing downstream results.
Incorrect Answers
A:Under production cutover rehearsal conditions, Use FORCE=TRUE on every retry without any deduplication plan and assume no extra records can appear.
B:That is a mistake for a different zero-copy clone for sandbox task, where A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. Under production cutover rehearsal conditions, Export the entire database to CSV and reload it as the only supported cloning approach.
C:That is a mistake for a different zero-copy clone lifecycle in collaboration task, where A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. Under production cutover rehearsal conditions, Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
Question 453
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
- Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
- Change the result cache setting and assume it will switch the current schema for both sessions.
Explanation
Correct Answer
A:The supportable direction is: Keep data in managed database storage and resume compute only when processing is needed. This directly undermines durable database storage separation in the specified context.
Incorrect Answers
B:That is a mistake for a different external table over data lake task, where A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. Under architecture planning workshop conditions, Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
C:That is a mistake for a different warehouse local data cache task, where A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. Under architecture planning workshop conditions, Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
D:That is a mistake for a different session database and role context task, where Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. It does not directly defeat the present durable database storage separation requirement, whose proper treatment is: Keep data in managed database storage and resume compute only when processing is needed.
Question 454
[Peak traffic performance incident] A reviewer recommends: Use LATERAL FLATTEN on the array path and project element fields together with the parent row key. The requirement remains: A BI engineer is investigating the exact bottleneck observed under production-like load. An event JSON record contains a purchases array and analysts need one relational row per purchase item while retaining the parent event identifier. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records.
- FLATTEN expands nested arrays or objects into tabular rows; ordinary JSON string extraction does not iterate every item.
- Partition metadata lets Snowflake skip micro-partitions whose ranges cannot satisfy the filter, but scattered values limit effective pruning.
- Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows.
Explanation
Correct Answer
B:In this peak traffic performance incident context, FLATTEN expands nested arrays or objects into tabular rows; ordinary JSON string extraction does not iterate every item. The recommendation is linked to observable evidence for this exact case: A record with three purchase objects yields three item rows with the same parent identifier and expected element values. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records.
C:That option concerns selective filter micro-partition pruning, not the requirement in this case. That explanation applies to a different selective filter micro-partition pruning problem: A daily operational report filters on a narrow event-time range yet scans nearly the entire multi-terabyte event table.
D:For the peak traffic performance incident conditions, Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows. That explanation applies to a different row access policy filtering problem: Regional managers share a table but must see only the geographic rows permitted by their assigned region.
Question 455
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which specific design mistake would most directly defeat the intended result?
- Assume a dynamic table is updated instantly on every source write regardless of its refresh behavior and target lag.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
- Choose a conventional analytical external table and expect the same transactional constraints and row update behavior.
- Replace the protected production table with transient storage merely to avoid Fail-safe storage expense.
Explanation
Correct Answer
C:The supportable direction is: Evaluate hybrid tables for the transactional access pattern and verify feature and account availability. This directly undermines hybrid table transactional access in the specified context.
Incorrect Answers
A:That is a mistake for a different dynamic table declarative refresh task, where A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. It does not directly defeat the present hybrid table transactional access requirement, whose proper treatment is: Evaluate hybrid tables for the transactional access pattern and verify feature and account availability.
B:That is a mistake for a different external table over data lake task, where A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It does not directly defeat the present hybrid table transactional access requirement, whose proper treatment is: Evaluate hybrid tables for the transactional access pattern and verify feature and account availability.
D:That is a mistake for a different permanent table recovery choice task, where An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It does not directly defeat the present hybrid table transactional access requirement, whose proper treatment is: Evaluate hybrid tables for the transactional access pattern and verify feature and account availability.
Question 456
[Production cutover rehearsal] The team proposes: Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication. Its actual requirement is: A data integration group runs a controlled replay with representative files or events. A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials.
- A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible.
- A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
- Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Explanation
Correct Answer
D:Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart. This is an outcome test of the specified kafka connector topic ingestion action under the production cutover rehearsal conditions. The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
Incorrect Answers
A:In this production cutover rehearsal context, A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials. This is an outcome for a different requirement: A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. It cannot by itself validate the proposed kafka connector topic ingestion action; the appropriate test is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
B:In this production cutover rehearsal context, A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible. This is an outcome for a different requirement: A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. It cannot by itself validate the proposed kafka connector topic ingestion action; the appropriate test is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
C:In this production cutover rehearsal context, A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions. This is an outcome for a different requirement: A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. It cannot by itself validate the proposed kafka connector topic ingestion action; the appropriate test is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Question 457
[Production migration readiness] The team proposes: Configure a suitable AUTO_SUSPEND interval and AUTO_RESUME for the development warehouse after assessing startup cadence. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
- Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions.
- Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
Explanation
Correct Answer
A:Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data. This is an outcome test of the specified warehouse auto-suspend economics action under the production migration readiness conditions. Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
Incorrect Answers
B:In this production migration readiness context, Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions. This is an outcome for a different requirement: A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It cannot by itself validate the proposed warehouse auto-suspend economics action; the appropriate test is: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
C:It cannot by itself validate the proposed warehouse auto-suspend economics action; the appropriate test is: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
D:In this production migration readiness context, Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size. This is an outcome for a different requirement: A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It cannot by itself validate the proposed warehouse auto-suspend economics action; the appropriate test is: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
Question 458
[Production cutover rehearsal] A reviewer recommends: Use the compatible Snowflake Spark connector with the correct authentication, pushdown, and connector settings. The requirement remains: A data integration group runs a controlled replay with representative files or events. A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files.
- The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown.
- Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
- Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
Explanation
Correct Answer
B:In this production cutover rehearsal context, The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown. The recommendation is linked to observable evidence for this exact case: A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns copy into location for unload, not the requirement in this case. It does not justify the specific spark connector distributed read action or its validation path: A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials.
C:It does not justify the specific spark connector distributed read action or its validation path: A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials.
D:That option concerns least-privilege read role, not the requirement in this case. It does not justify the specific spark connector distributed read action or its validation path: A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials.
Question 459
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which specific design mistake would most directly defeat the intended result?
- Assume a standard tiny warehouse can execute an arbitrary in-memory dataframe operation regardless of memory demand.
- Change the result cache setting and assume it will switch the current schema for both sessions.
- Download the entire confidential source table to a local pandas session before applying a simple supported projection.
- Assume deploying the app bypasses database grants and makes every protected table readable to all anonymous visitors.
Explanation
Correct Answer
C:The supportable direction is: Use Snowpark for Python with an appropriately provisioned execution context and pushdown-compatible dataframe operations. This directly undermines snowpark python pushdown in the specified context.
Incorrect Answers
A:That is a mistake for a different snowpark optimized workload isolation task, where A Python Snowpark pipeline uses large in-memory intermediate processing and repeatedly runs out of memory on a standard virtual warehouse. It does not directly defeat the present snowpark python pushdown requirement, whose proper treatment is: Use Snowpark for Python with an appropriately provisioned execution context and pushdown-compatible dataframe operations.
B:That is a mistake for a different session database and role context task, where Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. Under production migration readiness conditions, Change the result cache setting and assume it will switch the current schema for both sessions.
D:That is a mistake for a different streamlit app inside snowflake task, where An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. Under production migration readiness conditions, Assume deploying the app bypasses database grants and makes every protected table readable to all anonymous visitors.
Question 460
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload.
- Inspect pruning and the overlap of the filter column's values, then tune a supported clustering strategy if warranted.
- Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
- Evaluate Search Optimization Service for the supported predicate pattern and account edition after reviewing query profile.
Explanation
Correct Answer
D:Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency. In this peak traffic performance incident setting, the intended validation is: The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
Incorrect Answers
A:That action is relevant when Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency.
B:That action is relevant when A daily operational report filters on a narrow event-time range yet scans nearly the entire multi-terabyte event table. Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency.
C:That action is relevant when A support application must retrieve relevant passages from a collection of policy documents to ground an answer. It is not the primary action for the stated search optimization selective lookup need.