SnowPro Core COF-C03 Practice Test 31
Question 300
An architecture reviewer proposes the following solution: Explain that suspending compute does not delete persisted Snowflake table data. The business and technical requirement is: A product owner expects a suspended warehouse to erase cached table contents from durable storage. Which explanation most accurately justifies this choice?
- Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports.
- Warehouse lifecycle controls active compute rather than durable database storage.
- Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index.
- Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
Explanation
Correct Answer
B:Warehouse lifecycle controls active compute rather than durable database storage. This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Snowflake Notebooks where available with governed compute and access. That explains the role of “Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports”, but the present requirement calls for “Warehouse lifecycle controls active compute rather than durable database storage”: This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data.
C: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 “Warehouse lifecycle controls active compute rather than durable database storage”: This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data.
D: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 “Warehouse lifecycle controls active compute rather than durable database storage”: This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data.
Question 301
An architecture reviewer proposes the following solution: Assign an available warehouse with USAGE to the connecting role and update the client context. The business and technical requirement is: A connector breaks when its user default warehouse is dropped but its SELECT grants remain valid. Which explanation most accurately justifies this choice?
- Centralized posture views help detect configuration and security risks that object grants alone miss.
- SQL execution requires an accessible running or resumable warehouse, separate from table read rights.
- Table privileges alone may permit data use that governance and purpose restrictions prohibit.
- Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking.
Explanation
Correct Answer
B:SQL execution requires an accessible running or resumable warehouse, separate from table read rights. This mechanism explains why the proposed action fits the scenario: Assign an available warehouse with USAGE to the connecting role and update the client context. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Review Snowflake Trust Center findings and supported remediation recommendations. That explains the role of “Centralized posture views help detect configuration and security risks that object grants alone miss”, but the present requirement calls for “SQL execution requires an accessible running or resumable warehouse, separate from table read rights”: This mechanism explains why the proposed action fits the scenario: Assign an available warehouse with USAGE to the connecting role and update the client context.
C: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 “SQL execution requires an accessible running or resumable warehouse, separate from table read rights”: This mechanism explains why the proposed action fits the scenario: Assign an available warehouse with USAGE to the connecting role and update the client context.
D:This mechanism explains why the proposed action fits the scenario: Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls. That explains the role of “Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking”, but the present requirement calls for “SQL execution requires an accessible running or resumable warehouse, separate from table read rights”: This mechanism explains why the proposed action fits the scenario: Assign an available warehouse with USAGE to the connecting role and update the client context.
Question 302
An architecture reviewer proposes the following solution: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants. The business and technical requirement is: A nightly export must place only approved columns of a sensitive table into a partner's storage area. Which explanation most accurately justifies this choice?
- Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
- Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
- The supported connector provides SQL execution over an authenticated client session.
- File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe.
Explanation
Correct Answer
B:Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table. This mechanism explains why the proposed action fits the scenario: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Create an eligible dynamic table with TARGET_LAG and a refresh warehouse. That explains the role of “Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval”, but the present requirement calls for “Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table”: This mechanism explains why the proposed action fits the scenario: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants.
C: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 “Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table”: This mechanism explains why the proposed action fits the scenario: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants.
D:This mechanism explains why the proposed action fits the scenario: Check pipe status, stage path and cloud notification integration for missed messages. That explains the role of “File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe”, but the present requirement calls for “Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table”: This mechanism explains why the proposed action fits the scenario: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants.
Question 303
An architecture reviewer proposes the following solution: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing. The business and technical requirement is: An administrator wants to use an aggressive latency-oriented scale-out policy for urgent interactive reports. Which explanation most accurately justifies this choice?
- PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output.
- QUALIFY can filter rows using window-function results after analytic calculation.
- Large intermediate joins that exceed memory can create costly remote spill and longer runtimes.
- STANDARD favors starting additional clusters to minimize query queuing as demand grows.
Explanation
Correct Answer
D:STANDARD favors starting additional clusters to minimize query queuing as demand grows. This mechanism explains why the proposed action fits the scenario: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing. 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 “STANDARD favors starting additional clusters to minimize query queuing as demand grows”: This mechanism explains why the proposed action fits the scenario: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing.
B:This mechanism explains why the proposed action fits the scenario: Use ROW_NUMBER with PARTITION BY and QUALIFY to filter to the most recent row. That explains the role of “QUALIFY can filter rows using window-function results after analytic calculation”, but the present requirement calls for “STANDARD favors starting additional clusters to minimize query queuing as demand grows”: This mechanism explains why the proposed action fits the scenario: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing.
C:This mechanism explains why the proposed action fits the scenario: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy. That explains the role of “Large intermediate joins that exceed memory can create costly remote spill and longer runtimes”, but the present requirement calls for “STANDARD favors starting additional clusters to minimize query queuing as demand grows”: This mechanism explains why the proposed action fits the scenario: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing.
Question 304
An architecture reviewer proposes the following solution: Use separate secured listings or shares with scoped recipients and approved views. The business and technical requirement is: A data exchange platform needs to offer separate products to departments without creating one shared account-wide PUBLIC data grant. Which explanation most accurately justifies this choice?
- Replication propagates supported database state between accounts rather than rebuilding tables through files.
- Historical storage can remain recoverable or billable according to the table type and retention rules.
- Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially.
- Individual product authorization reduces inadvertent cross-tenant data access.
Explanation
Correct Answer
D:Individual product authorization reduces inadvertent cross-tenant data access. This mechanism explains why the proposed action fits the scenario: Use separate secured listings or shares with scoped recipients and approved views. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Configure authorized database replication and monitor refresh status. That explains the role of “Replication propagates supported database state between accounts rather than rebuilding tables through files”, but the present requirement calls for “Individual product authorization reduces inadvertent cross-tenant data access”: This mechanism explains why the proposed action fits the scenario: Use separate secured listings or shares with scoped recipients and approved views.
B:This mechanism explains why the proposed action fits the scenario: Review the Time Travel and Fail-safe retention windows and storage effects. That explains the role of “Historical storage can remain recoverable or billable according to the table type and retention rules”, but the present requirement calls for “Individual product authorization reduces inadvertent cross-tenant data access”: This mechanism explains why the proposed action fits the scenario: Use separate secured listings or shares with scoped recipients and approved views.
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 “Individual product authorization reduces inadvertent cross-tenant data access”: This mechanism explains why the proposed action fits the scenario: Use separate secured listings or shares with scoped recipients and approved views.
Question 305
An architecture reviewer proposes the following solution: Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work. The business and technical requirement is: An ingestion team needs to explain whether metadata management is the responsibility of individual virtual warehouse nodes. Which explanation most accurately justifies this choice?
- Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
- Session warehouse context controls the compute resource charged for a query.
- Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
- Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
Explanation
Correct Answer
C:Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements. This mechanism explains why the proposed action fits the scenario: Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate a supported externally managed Iceberg table and compatible catalog integration. That explains the role of “Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes”, but the present requirement calls for “Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements”: This mechanism explains why the proposed action fits the scenario: Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work.
B:This mechanism explains why the proposed action fits the scenario: Select the intended warehouse in the session or connection before executing the job. That explains the role of “Session warehouse context controls the compute resource charged for a query”, but the present requirement calls for “Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements”: This mechanism explains why the proposed action fits the scenario: Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work.
D:This mechanism explains why the proposed action fits the scenario: Execute supported Snowflake SQL transformations using an appropriate compute warehouse. That explains the role of “Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls”, but the present requirement calls for “Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements”: This mechanism explains why the proposed action fits the scenario: Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work.
Question 306
An architecture reviewer proposes the following solution: Revoke their assigned access roles or object grants through the controlled role hierarchy. The business and technical requirement is: Several contractors should lose access to a shared dataset at contract end without changing the table contents. Which explanation most accurately justifies this choice?
- Masking policies condition returned column values based on authorized execution context.
- Data lineage reveals how downstream analytical objects depend on upstream sources.
- Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
- Authorization revocation separates identity lifecycle from destructive changes to stored data.
Explanation
Correct Answer
D:Authorization revocation separates identity lifecycle from destructive changes to stored data. This mechanism explains why the proposed action fits the scenario: Revoke their assigned access roles or object grants through the controlled role hierarchy. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Attach an appropriate dynamic data masking policy to protected columns. That explains the role of “Masking policies condition returned column values based on authorized execution context”, but the present requirement calls for “Authorization revocation separates identity lifecycle from destructive changes to stored data”: This mechanism explains why the proposed action fits the scenario: Revoke their assigned access roles or object grants through the controlled role hierarchy.
B:This mechanism explains why the proposed action fits the scenario: Inspect supported Snowflake data lineage for the table and view dependency chain. That explains the role of “Data lineage reveals how downstream analytical objects depend on upstream sources”, but the present requirement calls for “Authorization revocation separates identity lifecycle from destructive changes to stored data”: This mechanism explains why the proposed action fits the scenario: Revoke their assigned access roles or object grants through the controlled role hierarchy.
C: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 “Authorization revocation separates identity lifecycle from destructive changes to stored data”: This mechanism explains why the proposed action fits the scenario: Revoke their assigned access roles or object grants through the controlled role hierarchy.
Question 307
An architecture reviewer proposes the following solution: Define an auto-ingest Snowpipe with a stage and supported cloud event notifications. The business and technical requirement is: A partner uploads new small files throughout the hour and the team wants serverless ingestion without scheduling warehouse-based batch jobs. Which explanation most accurately justifies this choice?
- Controlled external access isolates network destinations and credentials from routine SQL code.
- Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
- Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
- Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
Explanation
Correct Answer
C:Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification. This mechanism explains why the proposed action fits the scenario: Define an auto-ingest Snowpipe with a stage and supported cloud event notifications. 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 “Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification”: This mechanism explains why the proposed action fits the scenario: Define an auto-ingest Snowpipe with a stage and supported cloud event notifications.
B:This mechanism explains why the proposed action fits the scenario: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants. That explains the role of “Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table”, but the present requirement calls for “Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification”: This mechanism explains why the proposed action fits the scenario: Define an auto-ingest Snowpipe with a stage and supported cloud event notifications.
D: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 “Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification”: This mechanism explains why the proposed action fits the scenario: Define an auto-ingest Snowpipe with a stage and supported cloud event notifications.
Question 308
An architecture reviewer proposes the following solution: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits. The business and technical requirement is: A noninteractive batch reporting warehouse should conserve credits even if some queries wait briefly. Which explanation most accurately justifies this choice?
- ECONOMY prioritizes fuller use of existing clusters before starting more compute.
- Parsing JSON converts text into structured semi-structured values suitable for path operations.
- FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
- LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset.
Explanation
Correct Answer
A:ECONOMY prioritizes fuller use of existing clusters before starting more compute. This mechanism explains why the proposed action fits the scenario: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits. Confirm the design against supported platform behavior.
Incorrect Answers
B: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 “ECONOMY prioritizes fuller use of existing clusters before starting more compute”: This mechanism explains why the proposed action fits the scenario: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits.
C:This mechanism explains why the proposed action fits the scenario: Use LATERAL FLATTEN against the relevant VARIANT path. That explains the role of “FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values”, but the present requirement calls for “ECONOMY prioritizes fuller use of existing clusters before starting more compute”: This mechanism explains why the proposed action fits the scenario: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits.
D: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 “ECONOMY prioritizes fuller use of existing clusters before starting more compute”: This mechanism explains why the proposed action fits the scenario: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits.
Question 309
An architecture reviewer proposes the following solution: Create a supported zero-copy clone of the database. The business and technical requirement is: A development team needs a quick independent sandbox copy of a production database with minimal initial duplicate storage. Which explanation most accurately justifies this choice?
- Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
- Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
- Historical storage can remain recoverable or billable according to the table type and retention rules.
- Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
Explanation
Correct Answer
B:Cloning initially shares immutable micro-partitions and forks logically when later writes change data. This mechanism explains why the proposed action fits the scenario: Create a supported zero-copy clone of the database. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Cloning initially shares immutable micro-partitions and forks logically when later writes change data”: This mechanism explains why the proposed action fits the scenario: Create a supported zero-copy clone of the database.
C:This mechanism explains why the proposed action fits the scenario: Review the Time Travel and Fail-safe retention windows and storage effects. That explains the role of “Historical storage can remain recoverable or billable according to the table type and retention rules”, but the present requirement calls for “Cloning initially shares immutable micro-partitions and forks logically when later writes change data”: This mechanism explains why the proposed action fits the scenario: Create a supported zero-copy clone of the database.
D:This mechanism explains why the proposed action fits the scenario: Use a transient table only after approving its limited data-recovery guarantees. That explains the role of “Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics”, but the present requirement calls for “Cloning initially shares immutable micro-partitions and forks logically when later writes change data”: This mechanism explains why the proposed action fits the scenario: Create a supported zero-copy clone of the database.
Question 310
An architecture reviewer proposes the following solution: Allocate distinct warehouses to the jobs and use the same authorized database storage objects. The business and technical requirement is: A Snowflake user wants both high compute isolation and a single consistent dataset across a machine-learning job and reporting app. Which explanation most accurately justifies this choice?
- VARIANT holds flexible structured values without forcing one rigid input schema for every record.
- Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data.
- Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption.
- ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication.
Explanation
Correct Answer
B:Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data. This mechanism explains why the proposed action fits the scenario: Allocate distinct warehouses to the jobs and use the same authorized database storage objects. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Store semi-structured payloads in VARIANT and extract typed fields in downstream queries. That explains the role of “VARIANT holds flexible structured values without forcing one rigid input schema for every record”, but the present requirement calls for “Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data”: This mechanism explains why the proposed action fits the scenario: Allocate distinct warehouses to the jobs and use the same authorized database storage objects.
C:This mechanism explains why the proposed action fits the scenario: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region. That explains the role of “Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption”, but the present requirement calls for “Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data”: This mechanism explains why the proposed action fits the scenario: Allocate distinct warehouses to the jobs and use the same authorized database storage objects.
D:This mechanism explains why the proposed action fits the scenario: Configure an approved Snowflake ODBC driver and connection context. That explains the role of “ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication”, but the present requirement calls for “Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data”: This mechanism explains why the proposed action fits the scenario: Allocate distinct warehouses to the jobs and use the same authorized database storage objects.