SnowPro Core COF-C03 Practice Test 35
Question 340
An architecture reviewer proposes the following solution: Enforce policy-based governance and classification alongside least-privilege data access. The business and technical requirement is: A data steward wants to block use of unapproved customer personal data in a marketing dataset despite role grants. Which explanation most accurately justifies this choice?
- Network policies constrain permitted source addresses independently from SQL object grants.
- Table privileges alone may permit data use that governance and purpose restrictions prohibit.
- Authorization revocation separates identity lifecycle from destructive changes to stored data.
- Federated SSO centralizes login assurance and deprovisioning for interactive employees.
Explanation
Correct Answer
B:Table privileges alone may permit data use that governance and purpose restrictions prohibit. This mechanism explains why the proposed action fits the scenario: Enforce policy-based governance and classification alongside least-privilege data access. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges. That explains the role of “Network policies constrain permitted source addresses independently from SQL object grants”, but the present requirement calls for “Table privileges alone may permit data use that governance and purpose restrictions prohibit”: This mechanism explains why the proposed action fits the scenario: Enforce policy-based governance and classification alongside least-privilege data access.
C:This mechanism explains why the proposed action fits the scenario: Revoke their assigned access roles or object grants through the controlled role hierarchy. That explains the role of “Authorization revocation separates identity lifecycle from destructive changes to stored data”, but the present requirement calls for “Table privileges alone may permit data use that governance and purpose restrictions prohibit”: This mechanism explains why the proposed action fits the scenario: Enforce policy-based governance and classification alongside least-privilege data access.
D:This mechanism explains why the proposed action fits the scenario: Configure supported federated single sign-on with the organization's identity provider. That explains the role of “Federated SSO centralizes login assurance and deprovisioning for interactive employees”, but the present requirement calls for “Table privileges alone may permit data use that governance and purpose restrictions prohibit”: This mechanism explains why the proposed action fits the scenario: Enforce policy-based governance and classification alongside least-privilege data access.
Question 341
An architecture reviewer proposes the following solution: Consume the stream with a committed downstream DML transaction. The business and technical requirement is: A task keeps processing the same stream delta because a developer queries the stream without consuming changes inside committed DML. Which explanation most accurately justifies this choice?
- Network restrictions can reject a connection before a query reaches Snowflake's optimizer.
- File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
- A stream offset advances when its changes are consumed by a committed transactional operation.
- Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers.
Explanation
Correct Answer
C:A stream offset advances when its changes are consumed by a committed transactional operation. This mechanism explains why the proposed action fits the scenario: Consume the stream with a committed downstream DML transaction. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Separate transport and authentication diagnostics from later SQL execution errors. That explains the role of “Network restrictions can reject a connection before a query reaches Snowflake's optimizer”, but the present requirement calls for “A stream offset advances when its changes are consumed by a committed transactional operation”: This mechanism explains why the proposed action fits the scenario: Consume the stream with a committed downstream DML transaction.
B:This mechanism explains why the proposed action fits the scenario: Tune staged file sizing and compression based on Snowflake loading best practices. That explains the role of “File granularity and format affect parallelism and parsing overhead for warehouse-based loads”, but the present requirement calls for “A stream offset advances when its changes are consumed by a committed transactional operation”: This mechanism explains why the proposed action fits the scenario: Consume the stream with a committed downstream DML transaction.
D:This mechanism explains why the proposed action fits the scenario: Capture supported METADATA$ filename and load timestamp information during staging ingestion. That explains the role of “Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers”, but the present requirement calls for “A stream offset advances when its changes are consumed by a committed transactional operation”: This mechanism explains why the proposed action fits the scenario: Consume the stream with a committed downstream DML transaction.
Question 342
An architecture reviewer proposes the following solution: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands. The business and technical requirement is: A project requires memory-heavy Python processing alongside SQL and is considering Snowpark-optimized compute. Which explanation most accurately justifies this choice?
- Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved.
- A fair warehouse performance test must separate cache effects from the resource configuration change.
- Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering.
- A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
Explanation
Correct Answer
D:A specialized warehouse might provide better memory characteristics for supported Snowpark jobs. This mechanism explains why the proposed action fits the scenario: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands. 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 “A specialized warehouse might provide better memory characteristics for supported Snowpark jobs”: This mechanism explains why the proposed action fits the scenario: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands.
B:This mechanism explains why the proposed action fits the scenario: Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes. That explains the role of “A fair warehouse performance test must separate cache effects from the resource configuration change”, but the present requirement calls for “A specialized warehouse might provide better memory characteristics for supported Snowpark jobs”: This mechanism explains why the proposed action fits the scenario: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands.
C:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake Search Optimization Service for eligible point-lookup access patterns. That explains the role of “Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering”, but the present requirement calls for “A specialized warehouse might provide better memory characteristics for supported Snowpark jobs”: This mechanism explains why the proposed action fits the scenario: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands.
Question 343
An architecture reviewer proposes the following solution: Configure an approved Snowflake ODBC driver and connection context. The business and technical requirement is: A reporting vendor requires an ODBC data source for scheduled extract-refresh queries. Which explanation most accurately justifies this choice?
- VARIANT holds flexible structured values without forcing one rigid input schema for every record.
- Structured query generation and unstructured semantic retrieval solve different information-access problems.
- Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
- ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication.
Explanation
Correct Answer
D:ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication. This mechanism explains why the proposed action fits the scenario: Configure an approved Snowflake ODBC driver and connection context. 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 “ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication”: This mechanism explains why the proposed action fits the scenario: Configure an approved Snowflake ODBC driver and connection context.
B:This mechanism explains why the proposed action fits the scenario: Use Cortex Analyst for governed structured semantic SQL and Cortex Search for text retrieval as appropriate. That explains the role of “Structured query generation and unstructured semantic retrieval solve different information-access problems”, but the present requirement calls for “ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication”: This mechanism explains why the proposed action fits the scenario: Configure an approved Snowflake ODBC driver and connection context.
C:This mechanism explains why the proposed action fits the scenario: Evaluate scaling the warehouse up after confirming memory spill in Query Profile. That explains the role of “Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query”, but the present requirement calls for “ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication”: This mechanism explains why the proposed action fits the scenario: Configure an approved Snowflake ODBC driver and connection context.
Question 344
An architecture reviewer proposes the following solution: Review Snowflake Trust Center findings and supported remediation recommendations. The business and technical requirement is: A security team needs to inspect account posture findings and policy violations from built-in Snowflake security monitoring. Which explanation most accurately justifies this choice?
- Privilege flow follows the role hierarchy and cannot be inferred from role names alone.
- Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking.
- 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.
Explanation
Correct Answer
C:Centralized posture views help detect configuration and security risks that object grants alone miss. This mechanism explains why the proposed action fits the scenario: Review Snowflake Trust Center findings and supported remediation recommendations. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships. That explains the role of “Privilege flow follows the role hierarchy and cannot be inferred from role names alone”, but the present requirement calls for “Centralized posture views help detect configuration and security risks that object grants alone miss”: This mechanism explains why the proposed action fits the scenario: Review Snowflake Trust Center findings and supported remediation recommendations.
B: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 “Centralized posture views help detect configuration and security risks that object grants alone miss”: This mechanism explains why the proposed action fits the scenario: Review Snowflake Trust Center findings and supported remediation recommendations.
D: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. That explains the role of “SQL execution requires an accessible running or resumable warehouse, separate from table read rights”, but the present requirement calls for “Centralized posture views help detect configuration and security risks that object grants alone miss”: This mechanism explains why the proposed action fits the scenario: Review Snowflake Trust Center findings and supported remediation recommendations.
Question 345
An architecture reviewer proposes the following solution: Explain target lag as a desired freshness bound and monitor actual refresh timing. The business and technical requirement is: A dynamic table has TARGET_LAG='10 minutes', but an analyst expects exactly one refresh at each ten-minute boundary. Which explanation most accurately justifies this choice?
- Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
- Internal stages allow Snowflake-managed file staging without direct external cloud bucket access.
- Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval.
- Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches.
Explanation
Correct Answer
C:Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval. This mechanism explains why the proposed action fits the scenario: Explain target lag as a desired freshness bound and monitor actual refresh timing. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval”: This mechanism explains why the proposed action fits the scenario: Explain target lag as a desired freshness bound and monitor actual refresh timing.
B:This mechanism explains why the proposed action fits the scenario: Create or use a supported internal Snowflake stage with appropriate file format and grants. That explains the role of “Internal stages allow Snowflake-managed file staging without direct external cloud bucket access”, but the present requirement calls for “Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval”: This mechanism explains why the proposed action fits the scenario: Explain target lag as a desired freshness bound and monitor actual refresh timing.
D:This mechanism explains why the proposed action fits the scenario: Use COPY INTO a target table from a configured external stage and CSV file format. That explains the role of “Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches”, but the present requirement calls for “Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval”: This mechanism explains why the proposed action fits the scenario: Explain target lag as a desired freshness bound and monitor actual refresh timing.
Question 346
An architecture reviewer proposes the following solution: Use ROW_NUMBER with PARTITION BY and QUALIFY to filter to the most recent row. The business and technical requirement is: A sales table contains multiple updates per customer and a report needs the most recent order per customer. Which explanation most accurately justifies this choice?
- QUALIFY can filter rows using window-function results after analytic calculation.
- Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries.
- A fair warehouse performance test must separate cache effects from the resource configuration change.
- JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
Explanation
Correct Answer
A:QUALIFY can filter rows using window-function results after analytic calculation. 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. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Benchmark increasing warehouse size rather than adding multi-cluster capacity first. That explains the role of “Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries”, but the present requirement calls for “QUALIFY can filter rows using window-function results after analytic calculation”: 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.
C:This mechanism explains why the proposed action fits the scenario: Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes. That explains the role of “A fair warehouse performance test must separate cache effects from the resource configuration change”, but the present requirement calls for “QUALIFY can filter rows using window-function results after analytic calculation”: 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.
D:This mechanism explains why the proposed action fits the scenario: Apply explicit semi-structured NULL and missing-value checks with the appropriate Snowflake predicates. That explains the role of “JSON null and SQL NULL or absent paths can behave differently in comparisons and casts”, but the present requirement calls for “QUALIFY can filter rows using window-function results after analytic calculation”: 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.
Question 347
An architecture reviewer proposes the following solution: Use the Snowflake Connector for Python with bound parameters and approved authentication. The business and technical requirement is: A Python analyst must issue parameterized SQL and fetch structured results from a notebook client. Which explanation most accurately justifies this choice?
- The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation.
- Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
- Connection and authentication failures precede warehouse execution and are not solved by adding compute capacity.
- Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions.
Explanation
Correct Answer
A:The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation. This mechanism explains why the proposed action fits the scenario: Use the Snowflake Connector for Python with bound parameters and approved authentication. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Evaluate scaling the warehouse up after confirming memory spill in Query Profile. That explains the role of “Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query”, but the present requirement calls for “The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation”: This mechanism explains why the proposed action fits the scenario: Use the Snowflake Connector for Python with bound parameters and approved authentication.
C:This mechanism explains why the proposed action fits the scenario: Check the cloud services authentication and network access path before tuning warehouse size. That explains the role of “Connection and authentication failures precede warehouse execution and are not solved by adding compute capacity”, but the present requirement calls for “The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation”: This mechanism explains why the proposed action fits the scenario: Use the Snowflake Connector for Python with bound parameters and approved authentication.
D:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake hybrid tables for the supported transactional access pattern. That explains the role of “Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions”, but the present requirement calls for “The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation”: This mechanism explains why the proposed action fits the scenario: Use the Snowflake Connector for Python with bound parameters and approved authentication.
Question 348
An architecture reviewer proposes the following solution: Evaluate row access filtering and column masking independently with representative roles. The business and technical requirement is: Two governance policies on a sensitive table are being tested and the team needs to know which rows and columns each policy affects. Which explanation most accurately justifies this choice?
- Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
- Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow.
- Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure.
- Row access governs record visibility while masking governs values in visible rows, so they must be tested separately.
Explanation
Correct Answer
D:Row access governs record visibility while masking governs values in visible rows, so they must be tested separately. This mechanism explains why the proposed action fits the scenario: Evaluate row access filtering and column masking independently with representative roles. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Create the intended role hierarchy using role-to-role grants. That explains the role of “Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually”, but the present requirement calls for “Row access governs record visibility while masking governs values in visible rows, so they must be tested separately”: This mechanism explains why the proposed action fits the scenario: Evaluate row access filtering and column masking independently with representative roles.
B:This mechanism explains why the proposed action fits the scenario: Replace broad account administration with a custom reader role and intended warehouse usage privileges. That explains the role of “Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow”, but the present requirement calls for “Row access governs record visibility while masking governs values in visible rows, so they must be tested separately”: This mechanism explains why the proposed action fits the scenario: Evaluate row access filtering and column masking independently with representative roles.
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 “Row access governs record visibility while masking governs values in visible rows, so they must be tested separately”: This mechanism explains why the proposed action fits the scenario: Evaluate row access filtering and column masking independently with representative roles.
Question 349
An architecture reviewer proposes the following solution: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table. The business and technical requirement is: An intermediate dynamic table should update only when a downstream consumer needs fresh rows. Which explanation most accurately justifies this choice?
- DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
- Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
- Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
- The loader needs explicit format rules to distinguish metadata rows from data records.
Explanation
Correct Answer
A:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. This mechanism explains why the proposed action fits the scenario: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table. Confirm the design against supported platform behavior.
Incorrect Answers
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 “DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer”: This mechanism explains why the proposed action fits the scenario: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table.
C:This mechanism explains why the proposed action fits the scenario: Evaluate the supported Snowflake Connector for Kafka and its delivery mode. That explains the role of “Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling”, but the present requirement calls for “DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer”: This mechanism explains why the proposed action fits the scenario: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table.
D:This mechanism explains why the proposed action fits the scenario: Set the correct CSV header-handling option in the file format. That explains the role of “The loader needs explicit format rules to distinguish metadata rows from data records”, but the present requirement calls for “DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer”: This mechanism explains why the proposed action fits the scenario: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table.
Question 350
An architecture reviewer proposes the following solution: Use MERGE with defined match keys and explicit update and insert branches. The business and technical requirement is: A load contains changed customer records and the target dimension should update matches while inserting new identifiers. Which explanation most accurately justifies this choice?
- MERGE combines conditional matched and unmatched DML paths in one operation.
- Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size.
- Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources.
- Result caching can return compatible prior query results without reexecuting a full warehouse scan.
Explanation
Correct Answer
A:MERGE combines conditional matched and unmatched DML paths in one operation. This mechanism explains why the proposed action fits the scenario: Use MERGE with defined match keys and explicit update and insert branches. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Inspect join cardinality, join keys and query plan before simply adding compute. That explains the role of “Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size”, but the present requirement calls for “MERGE combines conditional matched and unmatched DML paths in one operation”: This mechanism explains why the proposed action fits the scenario: Use MERGE with defined match keys and explicit update and insert branches.
C:This mechanism explains why the proposed action fits the scenario: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size. That explains the role of “Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources”, but the present requirement calls for “MERGE combines conditional matched and unmatched DML paths in one operation”: This mechanism explains why the proposed action fits the scenario: Use MERGE with defined match keys and explicit update and insert branches.
D:This mechanism explains why the proposed action fits the scenario: Inspect Snowflake persisted query result reuse and conditions that invalidate it. That explains the role of “Result caching can return compatible prior query results without reexecuting a full warehouse scan”, but the present requirement calls for “MERGE combines conditional matched and unmatched DML paths in one operation”: This mechanism explains why the proposed action fits the scenario: Use MERGE with defined match keys and explicit update and insert branches.