SnowPro Core COF-C03 Practice Test 28
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.
Question 271
An architecture reviewer proposes the following solution: Inspect Snowflake access and query history using properly privileged monitoring views. The business and technical requirement is: A security engineer must find who ran a sensitive SQL query and whether the operation succeeded. Which explanation most accurately justifies this choice?
- Account activity history connects query operations to principals and execution context for investigation.
- Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
- Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure.
- Clear compute ownership and query identification improve chargeback compared with account totals alone.
Explanation
Correct Answer
A:Account activity history connects query operations to principals and execution context for investigation. This mechanism explains why the proposed action fits the scenario: Inspect Snowflake access and query history using properly privileged monitoring views. Confirm the design against supported platform behavior.
Incorrect Answers
B: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 “Account activity history connects query operations to principals and execution context for investigation”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake access and query history using properly privileged monitoring views.
C:This mechanism explains why the proposed action fits the scenario: Analyze Snowflake cost and account usage records by metering category. That explains the role of “Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure”, but the present requirement calls for “Account activity history connects query operations to principals and execution context for investigation”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake access and query history using properly privileged monitoring views.
D:This mechanism explains why the proposed action fits the scenario: Use independent warehouses or supported attribution metadata and query tags for the workloads. That explains the role of “Clear compute ownership and query identification improve chargeback compared with account totals alone”, but the present requirement calls for “Account activity history connects query operations to principals and execution context for investigation”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake access and query history using properly privileged monitoring views.
Question 272
An architecture reviewer proposes the following solution: Set the correct CSV header-handling option in the file format. The business and technical requirement is: A staged data file contains a header row and the table receives that header as ordinary data. Which explanation most accurately justifies this choice?
- Change-based processing limits recomputation when the SQL pattern and source changes support incremental work.
- The loader needs explicit format rules to distinguish metadata rows from data records.
- Task DAGs express ordered execution and permit management of dependent pipeline steps.
- DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
Explanation
Correct Answer
B:The loader needs explicit format rules to distinguish metadata rows from data records. This mechanism explains why the proposed action fits the scenario: Set the correct CSV header-handling option in the file format. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “The loader needs explicit format rules to distinguish metadata rows from data records”: This mechanism explains why the proposed action fits the scenario: Set the correct CSV header-handling option in the file format.
C: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 “The loader needs explicit format rules to distinguish metadata rows from data records”: This mechanism explains why the proposed action fits the scenario: Set the correct CSV header-handling option in the file format.
D: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 “The loader needs explicit format rules to distinguish metadata rows from data records”: This mechanism explains why the proposed action fits the scenario: Set the correct CSV header-handling option in the file format.
Question 273
An architecture reviewer proposes the following solution: Inspect join cardinality, join keys and query plan before simply adding compute. The business and technical requirement is: A developer assumes raising warehouse size fixes an accidentally explosive many-to-many join. Which explanation most accurately justifies this choice?
- Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size.
- CASE supplies conditional SQL expressions suited to bounded mappings, including defaults.
- Array access supports positional extraction from nested semi-structured values.
- Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
Explanation
Correct Answer
A:Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size. This mechanism explains why the proposed action fits the scenario: Inspect join cardinality, join keys and query plan before simply adding compute. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use CASE expressions with explicit ELSE handling for unknown values. That explains the role of “CASE supplies conditional SQL expressions suited to bounded mappings, including defaults”, but the present requirement calls for “Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size”: This mechanism explains why the proposed action fits the scenario: Inspect join cardinality, join keys and query plan before simply adding compute.
C:This mechanism explains why the proposed action fits the scenario: Use Snowflake VARIANT array indexing with appropriate type casting. That explains the role of “Array access supports positional extraction from nested semi-structured values”, but the present requirement calls for “Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size”: This mechanism explains why the proposed action fits the scenario: Inspect join cardinality, join keys and query plan before simply adding compute.
D: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 “Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size”: This mechanism explains why the proposed action fits the scenario: Inspect join cardinality, join keys and query plan before simply adding compute.
Question 274
An architecture reviewer proposes the following solution: Create an approved Snowflake Marketplace listing for the supported data product. The business and technical requirement is: A data vendor wants a published dataset discoverable through the Snowflake Marketplace with documented terms. Which explanation most accurately justifies this choice?
- Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share.
- Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
- Time Travel supports restoration of recently dropped eligible objects while their retention remains valid.
- A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
Explanation
Correct Answer
A:Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share. This mechanism explains why the proposed action fits the scenario: Create an approved Snowflake Marketplace listing for the supported data product. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Configure eligible extended Time Travel retention up to the edition's supported maximum. That explains the role of “Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs”, but the present requirement calls for “Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share”: This mechanism explains why the proposed action fits the scenario: Create an approved Snowflake Marketplace listing for the supported data product.
C: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 “Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share”: This mechanism explains why the proposed action fits the scenario: Create an approved Snowflake Marketplace listing for the supported data product.
D:This mechanism explains why the proposed action fits the scenario: Use CREATE DATABASE CLONE with supported Time Travel options where applicable. That explains the role of “A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks”, but the present requirement calls for “Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share”: This mechanism explains why the proposed action fits the scenario: Create an approved Snowflake Marketplace listing for the supported data product.
Question 275
An architecture reviewer proposes the following solution: Identify managed database storage as the persistence layer for compressed columnar table data. The business and technical requirement is: An auditor asks which Snowflake layer holds compressed columnar micro-partitions after a table is loaded. Which explanation most accurately justifies this choice?
- An explicit session command changes the active namespace used for later unqualified SQL references.
- Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
- Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute.
- Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage.
Explanation
Correct Answer
C:Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute. This mechanism explains why the proposed action fits the scenario: Identify managed database storage as the persistence layer for compressed columnar table data. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Check effective session context and precedence of explicit USE statements over connection defaults. That explains the role of “An explicit session command changes the active namespace used for later unqualified SQL references”, but the present requirement calls for “Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute”: This mechanism explains why the proposed action fits the scenario: Identify managed database storage as the persistence layer for compressed columnar table data.
B:This mechanism explains why the proposed action fits the scenario: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior. That explains the role of “Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries”, but the present requirement calls for “Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute”: This mechanism explains why the proposed action fits the scenario: Identify managed database storage as the persistence layer for compressed columnar table data.
D:This mechanism explains why the proposed action fits the scenario: Attribute workloads using dedicated warehouses and query or credit usage reporting. That explains the role of “Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage”, but the present requirement calls for “Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute”: This mechanism explains why the proposed action fits the scenario: Identify managed database storage as the persistence layer for compressed columnar table data.
Question 276
An architecture reviewer proposes the following solution: Use user-management privileges or the appropriate system administration role without broad data grants. The business and technical requirement is: A junior administrator should create user accounts but must not assume unrestricted business data ownership. Which explanation most accurately justifies this choice?
- Query metadata supports operational reporting of status, user, role and execution context.
- Managing identities and accessing all customer tables are distinct authorization duties.
- Consistent tag semantics support reliable downstream policy and reporting behavior.
- Table privileges alone may permit data use that governance and purpose restrictions prohibit.
Explanation
Correct Answer
B:Managing identities and accessing all customer tables are distinct authorization duties. This mechanism explains why the proposed action fits the scenario: Use user-management privileges or the appropriate system administration role without broad data grants. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Managing identities and accessing all customer tables are distinct authorization duties”: This mechanism explains why the proposed action fits the scenario: Use user-management privileges or the appropriate system administration role without broad data grants.
C:This mechanism explains why the proposed action fits the scenario: Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks. That explains the role of “Consistent tag semantics support reliable downstream policy and reporting behavior”, but the present requirement calls for “Managing identities and accessing all customer tables are distinct authorization duties”: This mechanism explains why the proposed action fits the scenario: Use user-management privileges or the appropriate system administration role without broad data grants.
D:This mechanism explains why the proposed action fits the scenario: Enforce policy-based governance and classification alongside least-privilege data access. That explains the role of “Table privileges alone may permit data use that governance and purpose restrictions prohibit”, but the present requirement calls for “Managing identities and accessing all customer tables are distinct authorization duties”: This mechanism explains why the proposed action fits the scenario: Use user-management privileges or the appropriate system administration role without broad data grants.
Question 277
An architecture reviewer proposes the following solution: Capture supported METADATA$ filename and load timestamp information during staging ingestion. The business and technical requirement is: A reporting table needs file ingestion timestamp and original file name for downstream lineage. Which explanation most accurately justifies this choice?
- Controlled external access isolates network destinations and credentials from routine SQL code.
- Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers.
- A task definition may exist yet remain suspended or unable to run under its effective owner privileges.
- Change-based processing limits recomputation when the SQL pattern and source changes support incremental work.
Explanation
Correct Answer
B:Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers. This mechanism explains why the proposed action fits the scenario: Capture supported METADATA$ filename and load timestamp information during staging ingestion. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use supported external access integrations and secret objects for approved network destinations. That explains the role of “Controlled external access isolates network destinations and credentials from routine SQL code”, but the present requirement calls for “Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers”: This mechanism explains why the proposed action fits the scenario: Capture supported METADATA$ filename and load timestamp information during staging ingestion.
C:This mechanism explains why the proposed action fits the scenario: Restore the intended task schedule and EXECUTE TASK privileges then RESUME through approved workflow. That explains the role of “A task definition may exist yet remain suspended or unable to run under its effective owner privileges”, but the present requirement calls for “Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers”: This mechanism explains why the proposed action fits the scenario: Capture supported METADATA$ filename and load timestamp information during staging ingestion.
D: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 “Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers”: This mechanism explains why the proposed action fits the scenario: Capture supported METADATA$ filename and load timestamp information during staging ingestion.
Question 278
An architecture reviewer proposes the following solution: Compare search optimization and targeted materialized views against actual filter patterns. The business and technical requirement is: Several SQL reports use different filter paths on one large table and a single clustering key cannot efficiently serve them all. Which explanation most accurately justifies this choice?
- PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output.
- Window functions compute rankings across a partition while retaining the underlying row granularity.
- Clustering optimizes data locality for one key expression, while other services can target distinct access paths.
- Document AI can extract structured information from unstructured documents but needs confidence and quality checks.
Explanation
Correct Answer
C:Clustering optimizes data locality for one key expression, while other services can target distinct access paths. This mechanism explains why the proposed action fits the scenario: Compare search optimization and targeted materialized views against actual filter patterns. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use supported PIVOT syntax with a defined aggregate and category list. That explains the role of “PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output”, but the present requirement calls for “Clustering optimizes data locality for one key expression, while other services can target distinct access paths”: This mechanism explains why the proposed action fits the scenario: Compare search optimization and targeted materialized views against actual filter patterns.
B:This mechanism explains why the proposed action fits the scenario: Use RANK or DENSE_RANK with a partitioned window expression appropriate to tie behavior. That explains the role of “Window functions compute rankings across a partition while retaining the underlying row granularity”, but the present requirement calls for “Clustering optimizes data locality for one key expression, while other services can target distinct access paths”: This mechanism explains why the proposed action fits the scenario: Compare search optimization and targeted materialized views against actual filter patterns.
D:This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake document processing AI features with human validation gates. That explains the role of “Document AI can extract structured information from unstructured documents but needs confidence and quality checks”, but the present requirement calls for “Clustering optimizes data locality for one key expression, while other services can target distinct access paths”: This mechanism explains why the proposed action fits the scenario: Compare search optimization and targeted materialized views against actual filter patterns.
Question 279
An architecture reviewer proposes the following solution: Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls. The business and technical requirement is: Two partner organizations want to analyze overlapping customer cohorts without freely exchanging individual-level records. Which explanation most accurately justifies this choice?
- Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
- Statement-based history offers precise temporal reference points for eligible Snowflake objects.
- Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data.
- A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
Explanation
Correct Answer
C:Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data. This mechanism explains why the proposed action fits the scenario: Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data”: This mechanism explains why the proposed action fits the scenario: Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
B:This mechanism explains why the proposed action fits the scenario: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported. That explains the role of “Statement-based history offers precise temporal reference points for eligible Snowflake objects”, but the present requirement calls for “Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data”: This mechanism explains why the proposed action fits the scenario: Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
D:This mechanism explains why the proposed action fits the scenario: Use CREATE DATABASE CLONE with supported Time Travel options where applicable. That explains the role of “A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks”, but the present requirement calls for “Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data”: This mechanism explains why the proposed action fits the scenario: Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
Question 280
An architecture reviewer proposes the following solution: Investigate authentication and authorization in the cloud services control path and the selected role. The business and technical requirement is: A connection succeeds but users cannot query protected objects because their privileges are insufficient. Which explanation most accurately justifies this choice?
- Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
- Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
- Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
- Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements.
Explanation
Correct Answer
D:Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements. This mechanism explains why the proposed action fits the scenario: Investigate authentication and authorization in the cloud services control path and the selected role. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Snowsight for manual exploration and a Snowflake CLI or supported connector for repeatable jobs. That explains the role of “Interactive and automated interfaces suit different workflows but share Snowflake's security and object model”, but the present requirement calls for “Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements”: This mechanism explains why the proposed action fits the scenario: Investigate authentication and authorization in the cloud services control path and the selected role.
B:This mechanism explains why the proposed action fits the scenario: Let Snowflake manage storage, compression, and micro-partitions for standard tables. That explains the role of “Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement”, but the present requirement calls for “Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements”: This mechanism explains why the proposed action fits the scenario: Investigate authentication and authorization in the cloud services control path and the selected role.
C:This mechanism explains why the proposed action fits the scenario: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior. That explains the role of “Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries”, but the present requirement calls for “Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements”: This mechanism explains why the proposed action fits the scenario: Investigate authentication and authorization in the cloud services control path and the selected role.