SnowPro Core COF-C03 Practice Test 49
Question 480
An architecture reviewer proposes the following solution: Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers. The business and technical requirement is: A business is comparing its own managed servers with an elastic cloud analytics platform to handle unpredictable reporting demand. Which explanation most accurately justifies this choice?
- Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
- Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage.
- Search provides semantic retrieval over textual content for a retrieval-augmented question-answering pattern.
- Materialized views persist selected computed results but impose storage and maintenance costs.
Explanation
Correct Answer
B:Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage. This mechanism explains why the proposed action fits the scenario: Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers. Confirm the design against supported platform behavior.
Incorrect Answers
A: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. That explains the role of “Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements”, but the present requirement calls for “Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage”: This mechanism explains why the proposed action fits the scenario: Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers.
C: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 “Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage”: This mechanism explains why the proposed action fits the scenario: Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers.
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 “Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage”: This mechanism explains why the proposed action fits the scenario: Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers.
Question 481
An architecture reviewer proposes the following solution: Inspect CURRENT_ROLE and effective primary or secondary role grants for the session. The business and technical requirement is: An application can read a table under one activated primary role but not when it changes its default role. Which explanation most accurately justifies this choice?
- Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
- Query metadata supports operational reporting of status, user, role and execution context.
- The active session role context determines which object privileges are available.
- Row access policies enforce row-level visibility in queries independently of front-end filters.
Explanation
Correct Answer
C:The active session role context determines which object privileges are available. This mechanism explains why the proposed action fits the scenario: Inspect CURRENT_ROLE and effective primary or secondary role grants for the session. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “The active session role context determines which object privileges are available”: This mechanism explains why the proposed action fits the scenario: Inspect CURRENT_ROLE and effective primary or secondary role grants for the session.
B: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 “The active session role context determines which object privileges are available”: This mechanism explains why the proposed action fits the scenario: Inspect CURRENT_ROLE and effective primary or secondary role grants for the session.
D:This mechanism explains why the proposed action fits the scenario: Apply a row access policy that filters rows based on authorized role or mapping context. That explains the role of “Row access policies enforce row-level visibility in queries independently of front-end filters”, but the present requirement calls for “The active session role context determines which object privileges are available”: This mechanism explains why the proposed action fits the scenario: Inspect CURRENT_ROLE and effective primary or secondary role grants for the session.
Question 482
An architecture reviewer proposes the following solution: Use COPY INTO an external stage location with an approved file format and storage integration. The business and technical requirement is: A partner wants to unload daily query results to a secured external cloud-storage location as compressed files. Which explanation most accurately justifies this choice?
- Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
- COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
- Incremental refresh depends on retained source change history; expired metadata can make resumption impossible.
- Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
Explanation
Correct Answer
B:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. This mechanism explains why the proposed action fits the scenario: Use COPY INTO an external stage location with an approved file format and storage integration. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “COPY INTO location supports unloading query output to stage files rather than adding rows to a table”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO an external stage location with an approved file format and storage integration.
C:This mechanism explains why the proposed action fits the scenario: Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps. That explains the role of “Incremental refresh depends on retained source change history; expired metadata can make resumption impossible”, but the present requirement calls for “COPY INTO location supports unloading query output to stage files rather than adding rows to a table”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO an external stage location with an approved file format and storage integration.
D:This mechanism explains why the proposed action fits the scenario: Create a Snowflake task with an appropriate schedule and execution context. That explains the role of “Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary”, but the present requirement calls for “COPY INTO location supports unloading query output to stage files rather than adding rows to a table”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO an external stage location with an approved file format and storage integration.
Question 483
An architecture reviewer proposes the following solution: Inspect Snowflake persisted query result reuse and conditions that invalidate it. The business and technical requirement is: A dashboard reruns identical SELECT statements and stakeholders want to understand why some executions are nearly instantaneous. Which explanation most accurately justifies this choice?
- CTEs structure intermediate logic for readability while still permitting optimizer planning.
- A maximum permits capacity growth but does not force permanent use of all configured clusters.
- Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
- Result caching can return compatible prior query results without reexecuting a full warehouse scan.
Explanation
Correct Answer
D:Result caching can return compatible prior query results without reexecuting a full warehouse scan. This mechanism explains why the proposed action fits the scenario: Inspect Snowflake persisted query result reuse and conditions that invalidate it. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Result caching can return compatible prior query results without reexecuting a full warehouse scan”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake persisted query result reuse and conditions that invalidate it.
B: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 “Result caching can return compatible prior query results without reexecuting a full warehouse scan”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake persisted query result reuse and conditions that invalidate it.
C:This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata. That explains the role of “Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually”, but the present requirement calls for “Result caching can return compatible prior query results without reexecuting a full warehouse scan”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake persisted query result reuse and conditions that invalidate it.
Question 484
An architecture reviewer proposes the following solution: Use a transient table only after approving its limited data-recovery guarantees. The business and technical requirement is: A low-value transient staging table should avoid the additional permanent-table Fail-safe storage window. Which explanation most accurately justifies this choice?
- Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
- Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
- Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features.
- Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
Explanation
Correct Answer
A:Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics. This mechanism explains why the proposed action fits the scenario: Use a transient table only after approving its limited data-recovery guarantees. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Create a Secure Data Share with authorized objects and add the approved consumer account. That explains the role of “Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy”, but the present requirement calls for “Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics”: This mechanism explains why the proposed action fits the scenario: Use a transient table only after approving its limited data-recovery guarantees.
C: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 “Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics”: This mechanism explains why the proposed action fits the scenario: Use a transient table only after approving its limited data-recovery guarantees.
D: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. That explains the role of “Secure views can project approved data to recipients while protecting provider-owned source logic and columns”, but the present requirement calls for “Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics”: This mechanism explains why the proposed action fits the scenario: Use a transient table only after approving its limited data-recovery guarantees.
Question 485
An architecture reviewer proposes the following solution: Combine Snowflake SQL with supported Snowpark and native application development capabilities. The business and technical requirement is: An engineering lead wants to use SQL, Python and application tooling within one governed data platform rather than export every dataset. Which explanation most accurately justifies this choice?
- VARIANT holds flexible structured values without forcing one rigid input schema for every record.
- Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage.
- IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges.
- Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
Explanation
Correct Answer
D:Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces. This mechanism explains why the proposed action fits the scenario: Combine Snowflake SQL with supported Snowpark and native application development capabilities. 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 “Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces”: This mechanism explains why the proposed action fits the scenario: Combine Snowflake SQL with supported Snowpark and native application development capabilities.
B:This mechanism explains why the proposed action fits the scenario: Benchmark end-to-end credits and latency for representative queries before choosing warehouse size. That explains the role of “Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage”, but the present requirement calls for “Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces”: This mechanism explains why the proposed action fits the scenario: Combine Snowflake SQL with supported Snowpark and native application development capabilities.
C:This mechanism explains why the proposed action fits the scenario: Use a supported VS Code Snowflake extension or integration with repository version control. That explains the role of “IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges”, but the present requirement calls for “Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces”: This mechanism explains why the proposed action fits the scenario: Combine Snowflake SQL with supported Snowpark and native application development capabilities.
Question 486
An architecture reviewer proposes the following solution: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely. The business and technical requirement is: An application should authenticate without a long-lived static password embedded in deployment files. Which explanation most accurately justifies this choice?
- Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
- Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data.
- Row access policies enforce row-level visibility in queries independently of front-end filters.
- Column masking can transform visible values for less-privileged roles without changing stored source values.
Explanation
Correct Answer
A:Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle. This mechanism explains why the proposed action fits the scenario: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Restrict grants and implement an approved secure projection with scoped consumer roles. That explains the role of “Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data”, but the present requirement calls for “Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle”: This mechanism explains why the proposed action fits the scenario: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
C:This mechanism explains why the proposed action fits the scenario: Apply a row access policy that filters rows based on authorized role or mapping context. That explains the role of “Row access policies enforce row-level visibility in queries independently of front-end filters”, but the present requirement calls for “Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle”: This mechanism explains why the proposed action fits the scenario: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
D:This mechanism explains why the proposed action fits the scenario: Implement a governed masking expression that exposes only the permitted suffix. That explains the role of “Column masking can transform visible values for less-privileged roles without changing stored source values”, but the present requirement calls for “Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle”: This mechanism explains why the proposed action fits the scenario: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
Question 487
An architecture reviewer proposes the following solution: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases. The business and technical requirement is: A data engineer needs to validate a batch of staged CSV files for parse errors before committing any target rows. Which explanation most accurately justifies this choice?
- A stream offset advances when its changes are consumed by a committed transactional operation.
- The supported connector provides SQL execution over an authenticated client session.
- Private network access relies on cloud routing and DNS as well as Snowflake account policies.
- Bulk copy validation checks how staged rows would parse without treating the test as a production load.
Explanation
Correct Answer
D:Bulk copy validation checks how staged rows would parse without treating the test as a production load. This mechanism explains why the proposed action fits the scenario: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Consume the stream with a committed downstream DML transaction. That explains the role of “A stream offset advances when its changes are consumed by a committed transactional operation”, but the present requirement calls for “Bulk copy validation checks how staged rows would parse without treating the test as a production load”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases.
B: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 “Bulk copy validation checks how staged rows would parse without treating the test as a production load”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases.
C:This mechanism explains why the proposed action fits the scenario: Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint. That explains the role of “Private network access relies on cloud routing and DNS as well as Snowflake account policies”, but the present requirement calls for “Bulk copy validation checks how staged rows would parse without treating the test as a production load”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases.
Question 488
An architecture reviewer proposes the following solution: Investigate local warehouse cache warm-up before attributing the slowdown solely to query text. The business and technical requirement is: An analytics job slows after its warehouse resumes from an extended suspension even though SQL has not changed. Which explanation most accurately justifies this choice?
- Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved.
- ECONOMY prioritizes fuller use of existing clusters before starting more compute.
- Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
- Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence.
Explanation
Correct Answer
C:Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching. This mechanism explains why the proposed action fits the scenario: Investigate local warehouse cache warm-up before attributing the slowdown solely to query text. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules. That explains the role of “Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved”, but the present requirement calls for “Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching”: This mechanism explains why the proposed action fits the scenario: Investigate local warehouse cache warm-up before attributing the slowdown solely to query text.
B:This mechanism explains why the proposed action fits the scenario: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits. That explains the role of “ECONOMY prioritizes fuller use of existing clusters before starting more compute”, but the present requirement calls for “Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching”: This mechanism explains why the proposed action fits the scenario: Investigate local warehouse cache warm-up before attributing the slowdown solely to query text.
D:This mechanism explains why the proposed action fits the scenario: Benchmark a smaller warehouse with representative query sizes and verify service-level objectives. That explains the role of “Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence”, but the present requirement calls for “Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching”: This mechanism explains why the proposed action fits the scenario: Investigate local warehouse cache warm-up before attributing the slowdown solely to query text.
Question 489
An architecture reviewer proposes the following solution: Configure eligible extended Time Travel retention up to the edition's supported maximum. The business and technical requirement is: A regulated table needs historical recovery for more than a day under a supported Snowflake edition. Which explanation most accurately justifies this choice?
- Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
- Individual product authorization reduces inadvertent cross-tenant data access.
- Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
- Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly.
Explanation
Correct Answer
A:Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs. This mechanism explains why the proposed action fits the scenario: Configure eligible extended Time Travel retention up to the edition's supported maximum. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use separate secured listings or shares with scoped recipients and approved views. That explains the role of “Individual product authorization reduces inadvertent cross-tenant data access”, but the present requirement calls for “Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs”: This mechanism explains why the proposed action fits the scenario: Configure eligible extended Time Travel retention up to the edition's supported maximum.
C: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. That explains the role of “Secure views can project approved data to recipients while protecting provider-owned source logic and columns”, but the present requirement calls for “Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs”: This mechanism explains why the proposed action fits the scenario: Configure eligible extended Time Travel retention up to the edition's supported maximum.
D:This mechanism explains why the proposed action fits the scenario: Plan supported cross-region sharing or listing and replication arrangements as required. That explains the role of “Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly”, but the present requirement calls for “Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs”: This mechanism explains why the proposed action fits the scenario: Configure eligible extended Time Travel retention up to the edition's supported maximum.
Question 490
An architecture reviewer proposes the following solution: Correct the design to use independent warehouses reading shared Snowflake tables. The business and technical requirement is: An executive assumes copying the same table into separate warehouses is necessary to isolate dashboards from transformations. Which explanation most accurately justifies this choice?
- Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions.
- IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges.
- Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
- Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
Explanation
Correct Answer
C:Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table. This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Package a supported Snowpark UDF with the correct runtime and package permissions. That explains the role of “Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions”, but the present requirement calls for “Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table”: This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables.
B:This mechanism explains why the proposed action fits the scenario: Use a supported VS Code Snowflake extension or integration with repository version control. That explains the role of “IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges”, but the present requirement calls for “Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table”: This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables.
D: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 “Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table”: This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables.