SnowPro Core COF-C03 Practice Test 27
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.
Question 261
An architecture reviewer proposes the following solution: Use a supported overlapping key or token rotation procedure with staged validation. The business and technical requirement is: An operator needs to rotate credentials for a service identity without breaking every production connector at once. Which explanation most accurately justifies this choice?
- Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
- Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
- Query metadata supports operational reporting of status, user, role and execution context.
- Planned rotation allows new credentials to be tested before revoking the old authentication method.
Explanation
Correct Answer
D:Planned rotation allows new credentials to be tested before revoking the old authentication method. This mechanism explains why the proposed action fits the scenario: Use a supported overlapping key or token rotation procedure with staged validation. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Inspect warehouse load history and query history for queue time distribution. That explains the role of “Queueing indicates concurrency pressure, which should be distinguished from slow execution operators”, but the present requirement calls for “Planned rotation allows new credentials to be tested before revoking the old authentication method”: This mechanism explains why the proposed action fits the scenario: Use a supported overlapping key or token rotation procedure with staged validation.
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 “Planned rotation allows new credentials to be tested before revoking the old authentication method”: This mechanism explains why the proposed action fits the scenario: Use a supported overlapping key or token rotation procedure with staged validation.
C:This mechanism explains why the proposed action fits the scenario: Use authorized QUERY_HISTORY and related account monitoring views. That explains the role of “Query metadata supports operational reporting of status, user, role and execution context”, but the present requirement calls for “Planned rotation allows new credentials to be tested before revoking the old authentication method”: This mechanism explains why the proposed action fits the scenario: Use a supported overlapping key or token rotation procedure with staged validation.
Question 262
An architecture reviewer proposes the following solution: Use a controlled post-load removal policy or supported COPY purge behavior where appropriate. The business and technical requirement is: An ETL group wants to remove staged temporary files only after successful ingestion and retention approval. Which explanation most accurately justifies this choice?
- Stage file deletion and data loading are separate governance decisions that require verification.
- DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
- The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches.
- Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
Explanation
Correct Answer
A:Stage file deletion and data loading are separate governance decisions that require verification. This mechanism explains why the proposed action fits the scenario: Use a controlled post-load removal policy or supported COPY purge behavior where appropriate. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table. That explains the role of “DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer”, but the present requirement calls for “Stage file deletion and data loading are separate governance decisions that require verification”: This mechanism explains why the proposed action fits the scenario: Use a controlled post-load removal policy or supported COPY purge behavior where appropriate.
C: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 “Stage file deletion and data loading are separate governance decisions that require verification”: This mechanism explains why the proposed action fits the scenario: Use a controlled post-load removal policy or supported COPY purge behavior where appropriate.
D:This mechanism explains why the proposed action fits the scenario: Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing. That explains the role of “Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending”, but the present requirement calls for “Stage file deletion and data loading are separate governance decisions that require verification”: This mechanism explains why the proposed action fits the scenario: Use a controlled post-load removal policy or supported COPY purge behavior where appropriate.
Question 263
An architecture reviewer proposes the following solution: Evaluate supported search optimization for qualified semi-structured path predicates. The business and technical requirement is: A team wants to improve selectivity for nested VARIANT key searches rather than clustering every whole document. Which explanation most accurately justifies this choice?
- LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset.
- CTEs structure intermediate logic for readability while still permitting optimizer planning.
- Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
- Capacity should be evaluated against actual queue time, execution time and consumed credits.
Explanation
Correct Answer
C:Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape. This mechanism explains why the proposed action fits the scenario: Evaluate supported search optimization for qualified semi-structured path predicates. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use LAG in a partitioned, ordered window expression. That explains the role of “LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset”, but the present requirement calls for “Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape”: This mechanism explains why the proposed action fits the scenario: Evaluate supported search optimization for qualified semi-structured path predicates.
B:This mechanism explains why the proposed action fits the scenario: Use common table expressions with the WITH clause to organize query stages. That explains the role of “CTEs structure intermediate logic for readability while still permitting optimizer planning”, but the present requirement calls for “Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape”: This mechanism explains why the proposed action fits the scenario: Evaluate supported search optimization for qualified semi-structured path predicates.
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 “Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape”: This mechanism explains why the proposed action fits the scenario: Evaluate supported search optimization for qualified semi-structured path predicates.
Question 264
An architecture reviewer proposes the following solution: Expose a governed secure view through a direct share rather than granting raw base-table access. The business and technical requirement is: A data provider must make a subset of rows available to a partner while retaining sensitive attributes in the underlying table. Which explanation most accurately justifies this choice?
- Time Travel supports restoration of recently dropped eligible objects while their retention remains valid.
- Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features.
- Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially.
- Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
Explanation
Correct Answer
D:Secure views can project approved data to recipients while protecting provider-owned source logic and columns. This mechanism explains why the proposed action fits the scenario: Expose a governed secure view through a direct share rather than granting raw base-table access. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window. That explains the role of “Time Travel supports restoration of recently dropped eligible objects while their retention remains valid”, but the present requirement calls for “Secure views can project approved data to recipients while protecting provider-owned source logic and columns”: This mechanism explains why the proposed action fits the scenario: Expose a governed secure view through a direct share rather than granting raw base-table access.
B:This mechanism explains why the proposed action fits the scenario: Evaluate supported database replication and failover configuration for the required regions and account editions. That explains the role of “Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features”, but the present requirement calls for “Secure views can project approved data to recipients while protecting provider-owned source logic and columns”: This mechanism explains why the proposed action fits the scenario: Expose a governed secure view through a direct share rather than granting raw base-table access.
C: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 “Secure views can project approved data to recipients while protecting provider-owned source logic and columns”: This mechanism explains why the proposed action fits the scenario: Expose a governed secure view through a direct share rather than granting raw base-table access.
Question 265
An architecture reviewer proposes the following solution: Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage. The business and technical requirement is: A large organization wants to distinguish Snowflake operational charges caused by compute from charges caused by stored data. Which explanation most accurately justifies this choice?
- Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index.
- Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
- Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
- Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms.
Explanation
Correct Answer
D:Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms. This mechanism explains why the proposed action fits the scenario: Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate clustering only against table size and selective range-filter access patterns. That explains the role of “Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index”, but the present requirement calls for “Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms”: This mechanism explains why the proposed action fits the scenario: Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage.
B:This mechanism explains why the proposed action fits the scenario: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity. That explains the role of “Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement”, but the present requirement calls for “Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms”: This mechanism explains why the proposed action fits the scenario: Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage.
C:This mechanism explains why the proposed action fits the scenario: Evaluate scaling the warehouse up after confirming memory spill in Query Profile. That explains the role of “Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query”, but the present requirement calls for “Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms”: This mechanism explains why the proposed action fits the scenario: Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage.
Question 266
An architecture reviewer proposes the following solution: Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate. The business and technical requirement is: An organization asks which default system role should own routine data objects rather than using ACCOUNTADMIN for all development. Which explanation most accurately justifies this choice?
- Routine creation should use governed roles rather than expanding use of top-level account administration.
- Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames.
- Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
- Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
Explanation
Correct Answer
A:Routine creation should use governed roles rather than expanding use of top-level account administration. This mechanism explains why the proposed action fits the scenario: Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use object tagging and catalog metadata to track data classification and responsible owners. That explains the role of “Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames”, but the present requirement calls for “Routine creation should use governed roles rather than expanding use of top-level account administration”: This mechanism explains why the proposed action fits the scenario: Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
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 “Routine creation should use governed roles rather than expanding use of top-level account administration”: This mechanism explains why the proposed action fits the scenario: Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
D:This mechanism explains why the proposed action fits the scenario: Delegate policy management to a controlled governance role and review ownership and grants. That explains the role of “Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers”, but the present requirement calls for “Routine creation should use governed roles rather than expanding use of top-level account administration”: This mechanism explains why the proposed action fits the scenario: Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
Question 267
An architecture reviewer proposes the following solution: Tune staged file sizing and compression based on Snowflake loading best practices. The business and technical requirement is: A large CSV file takes unusually long to parse and the team is considering splitting the source into parallelizable chunks. Which explanation most accurately justifies this choice?
- File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
- Change-based processing limits recomputation when the SQL pattern and source changes support incremental work.
- Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
- The supported connector provides SQL execution over an authenticated client session.
Explanation
Correct Answer
A:File granularity and format affect parallelism and parsing overhead for warehouse-based loads. This mechanism explains why the proposed action fits the scenario: Tune staged file sizing and compression based on Snowflake loading best practices. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation. That explains the role of “Change-based processing limits recomputation when the SQL pattern and source changes support incremental work”, but the present requirement calls for “File granularity and format affect parallelism and parsing overhead for warehouse-based loads”: This mechanism explains why the proposed action fits the scenario: Tune staged file sizing and compression based on Snowflake loading best practices.
C:This mechanism explains why the proposed action fits the scenario: Evaluate the supported Snowflake Connector for Kafka and its delivery mode. That explains the role of “Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling”, but the present requirement calls for “File granularity and format affect parallelism and parsing overhead for warehouse-based loads”: This mechanism explains why the proposed action fits the scenario: Tune staged file sizing and compression based on Snowflake loading best practices.
D:This mechanism explains why the proposed action fits the scenario: Use the official Snowflake Python Connector with the intended secure session settings. That explains the role of “The supported connector provides SQL execution over an authenticated client session”, but the present requirement calls for “File granularity and format affect parallelism and parsing overhead for warehouse-based loads”: This mechanism explains why the proposed action fits the scenario: Tune staged file sizing and compression based on Snowflake loading best practices.
Question 268
An architecture reviewer proposes the following solution: Prioritize clustering only where measured pruning gains justify reclustering costs. The business and technical requirement is: A DBA activates clustering on every table without checking table size or query access patterns. Which explanation most accurately justifies this choice?
- A maximum permits capacity growth but does not force permanent use of all configured clusters.
- Reclustering creates maintenance compute and storage overhead and does not improve every query.
- Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
- Parsing JSON converts text into structured semi-structured values suitable for path operations.
Explanation
Correct Answer
B:Reclustering creates maintenance compute and storage overhead and does not improve every query. This mechanism explains why the proposed action fits the scenario: Prioritize clustering only where measured pruning gains justify reclustering costs. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Verify multi-cluster auto-scale rules and minimum versus maximum cluster settings. That explains the role of “A maximum permits capacity growth but does not force permanent use of all configured clusters”, but the present requirement calls for “Reclustering creates maintenance compute and storage overhead and does not improve every query”: This mechanism explains why the proposed action fits the scenario: Prioritize clustering only where measured pruning gains justify reclustering costs.
C:This mechanism explains why the proposed action fits the scenario: Use Snowpark DataFrames with transformations executed by Snowflake compute. That explains the role of “Snowpark expresses transformations using supported languages and executes data operations close to governed tables”, but the present requirement calls for “Reclustering creates maintenance compute and storage overhead and does not improve every query”: This mechanism explains why the proposed action fits the scenario: Prioritize clustering only where measured pruning gains justify reclustering costs.
D:This mechanism explains why the proposed action fits the scenario: Apply a supported PARSE_JSON conversion and store or query VARIANT values. That explains the role of “Parsing JSON converts text into structured semi-structured values suitable for path operations”, but the present requirement calls for “Reclustering creates maintenance compute and storage overhead and does not improve every query”: This mechanism explains why the proposed action fits the scenario: Prioritize clustering only where measured pruning gains justify reclustering costs.
Question 269
An architecture reviewer proposes the following solution: Use an approved Snowflake Reader Account managed through the provider's sharing workflow. The business and technical requirement is: A non-Snowflake customer needs governed access to a provider dataset and does not want to operate its own existing Snowflake account. Which explanation most accurately justifies this choice?
- Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements.
- 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.
- Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
Explanation
Correct Answer
A:Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements. This mechanism explains why the proposed action fits the scenario: Use an approved Snowflake Reader Account managed through the provider's sharing workflow. Confirm the design against supported platform behavior.
Incorrect Answers
B: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 “Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements”: This mechanism explains why the proposed action fits the scenario: Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
C: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 “Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements”: This mechanism explains why the proposed action fits the scenario: Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
D:This mechanism explains why the proposed action fits the scenario: Use supported UNDROP SCHEMA within the configured Time Travel window. That explains the role of “Time Travel object recovery can restore eligible dropped schema structures while retention is valid”, but the present requirement calls for “Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements”: This mechanism explains why the proposed action fits the scenario: Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
Question 270
An architecture reviewer proposes the following solution: Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization. The business and technical requirement is: A team argues that cloud services is the layer that scans all data blocks when a reporting SQL statement executes. Which explanation most accurately justifies this choice?
- Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
- ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication.
- Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
- Search provides semantic retrieval over textual content for a retrieval-augmented question-answering pattern.
Explanation
Correct Answer
A:Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution. This mechanism explains why the proposed action fits the scenario: Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization. Confirm the design against supported platform behavior.
Incorrect Answers
B: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 “Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution”: This mechanism explains why the proposed action fits the scenario: Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization.
C:This mechanism explains why the proposed action fits the scenario: Use a dynamic table with an explicit target lag and warehouse for eligible transformations. That explains the role of “Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules”, but the present requirement calls for “Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution”: This mechanism explains why the proposed action fits the scenario: Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization.
D:This mechanism explains why the proposed action fits the scenario: Use Cortex Search with an approved indexed unstructured text corpus. That explains the role of “Search provides semantic retrieval over textual content for a retrieval-augmented question-answering pattern”, but the present requirement calls for “Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution”: This mechanism explains why the proposed action fits the scenario: Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization.