SnowPro Core COF-C03 Practice Test 38
Question 370
An architecture reviewer proposes the following solution: Use an appropriate Snowflake stored procedure under defined owner or caller rights. The business and technical requirement is: An operations team needs procedural control flow that executes several SQL statements in a governed routine. Which explanation most accurately justifies this choice?
- STANDARD favors starting additional clusters to minimize query queuing as demand grows.
- Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression.
- FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
- Document AI can extract structured information from unstructured documents but needs confidence and quality checks.
Explanation
Correct Answer
B:Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression. This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights. Confirm the design against supported platform behavior.
Incorrect Answers
A: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. That explains the role of “STANDARD favors starting additional clusters to minimize query queuing as demand grows”, but the present requirement calls for “Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression”: This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights.
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 “Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression”: This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights.
D:This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake document processing AI features with human validation gates. That explains the role of “Document AI can extract structured information from unstructured documents but needs confidence and quality checks”, but the present requirement calls for “Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression”: This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights.
Question 371
An architecture reviewer proposes the following solution: Select the intended warehouse in the session or connection before executing the job. The business and technical requirement is: An analyst has access to multiple warehouses and accidentally runs long ETL SQL on the shared BI warehouse. Which explanation most accurately justifies this choice?
- Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
- Cortex functions can perform language processing close to Snowflake data subject to availability and policy.
- A registry tracks model versions and deployment metadata so inference does not rely on ad-hoc file copies.
- Session warehouse context controls the compute resource charged for a query.
Explanation
Correct Answer
D:Session warehouse context controls the compute resource charged for a query. This mechanism explains why the proposed action fits the scenario: Select the intended warehouse in the session or connection before executing the job. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use a dynamic table with an explicit target lag and warehouse for eligible transformations. That explains the role of “Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules”, but the present requirement calls for “Session warehouse context controls the compute resource charged for a query”: This mechanism explains why the proposed action fits the scenario: Select the intended warehouse in the session or connection before executing the job.
B:This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake Cortex AI SQL functions under approved data security controls. That explains the role of “Cortex functions can perform language processing close to Snowflake data subject to availability and policy”, but the present requirement calls for “Session warehouse context controls the compute resource charged for a query”: This mechanism explains why the proposed action fits the scenario: Select the intended warehouse in the session or connection before executing the job.
C:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake ML model registry features appropriate to the deployed environment. That explains the role of “A registry tracks model versions and deployment metadata so inference does not rely on ad-hoc file copies”, but the present requirement calls for “Session warehouse context controls the compute resource charged for a query”: This mechanism explains why the proposed action fits the scenario: Select the intended warehouse in the session or connection before executing the job.
Question 372
An architecture reviewer proposes the following solution: Move the row restriction into a row access policy on the table or governed view. The business and technical requirement is: A report uses an arbitrary WHERE clause to hide other departments' records but users can bypass the report with SQL. Which explanation most accurately justifies this choice?
- Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.
- Application-level filtering is not a reliable security boundary for users with direct query access.
- Some Snowflake services use serverless credits independently of warehouse runtime.
- Privilege flow follows the role hierarchy and cannot be inferred from role names alone.
Explanation
Correct Answer
B:Application-level filtering is not a reliable security boundary for users with direct query access. This mechanism explains why the proposed action fits the scenario: Move the row restriction into a row access policy on the table or governed view. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles. That explains the role of “Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access”, but the present requirement calls for “Application-level filtering is not a reliable security boundary for users with direct query access”: This mechanism explains why the proposed action fits the scenario: Move the row restriction into a row access policy on the table or governed view.
C:This mechanism explains why the proposed action fits the scenario: Inspect serverless ingestion and task usage independently from user-managed warehouse charges. That explains the role of “Some Snowflake services use serverless credits independently of warehouse runtime”, but the present requirement calls for “Application-level filtering is not a reliable security boundary for users with direct query access”: This mechanism explains why the proposed action fits the scenario: Move the row restriction into a row access policy on the table or governed view.
D: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 “Application-level filtering is not a reliable security boundary for users with direct query access”: This mechanism explains why the proposed action fits the scenario: Move the row restriction into a row access policy on the table or governed view.
Question 373
An architecture reviewer proposes the following solution: Query supported dynamic table information-schema status and refresh history views. The business and technical requirement is: A pipeline team wants to monitor lag and recent failures for every dynamic table in an account. Which explanation most accurately justifies this choice?
- Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
- Network restrictions can reject a connection before a query reaches Snowflake's optimizer.
- Parquet carries structured column data and should not be parsed as plain delimited text.
- Storage integrations manage cloud authentication using controlled trust and permission assignments.
Explanation
Correct Answer
A:Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values. This mechanism explains why the proposed action fits the scenario: Query supported dynamic table information-schema status and refresh history views. Confirm the design against supported platform behavior.
Incorrect Answers
B: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 “Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values”: This mechanism explains why the proposed action fits the scenario: Query supported dynamic table information-schema status and refresh history views.
C:This mechanism explains why the proposed action fits the scenario: Define the correct PARQUET file format and compatible target column mapping. That explains the role of “Parquet carries structured column data and should not be parsed as plain delimited text”, but the present requirement calls for “Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values”: This mechanism explains why the proposed action fits the scenario: Query supported dynamic table information-schema status and refresh history views.
D:This mechanism explains why the proposed action fits the scenario: Use a supported Snowflake storage integration for delegated cloud storage access. That explains the role of “Storage integrations manage cloud authentication using controlled trust and permission assignments”, but the present requirement calls for “Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values”: This mechanism explains why the proposed action fits the scenario: Query supported dynamic table information-schema status and refresh history views.
Question 374
An architecture reviewer proposes the following solution: Use Snowpark DataFrames with transformations executed by Snowflake compute. The business and technical requirement is: Data scientists want to transform tables with Python DataFrame semantics without exporting huge datasets. Which explanation most accurately justifies this choice?
- VARIANT can contain different underlying types, so unconditional string conversion can be incorrect.
- Array access supports positional extraction from nested semi-structured values.
- QAS can offload parts of supported long-running queries to shared compute resources.
- Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
Explanation
Correct Answer
D:Snowpark expresses transformations using supported languages and executes data operations close to governed tables. This mechanism explains why the proposed action fits the scenario: Use Snowpark DataFrames with transformations executed by Snowflake compute. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Inspect TYPEOF and apply type-aware VARIANT transformations before coercion. That explains the role of “VARIANT can contain different underlying types, so unconditional string conversion can be incorrect”, but the present requirement calls for “Snowpark expresses transformations using supported languages and executes data operations close to governed tables”: This mechanism explains why the proposed action fits the scenario: Use Snowpark DataFrames with transformations executed by Snowflake compute.
B:This mechanism explains why the proposed action fits the scenario: Use Snowflake VARIANT array indexing with appropriate type casting. That explains the role of “Array access supports positional extraction from nested semi-structured values”, but the present requirement calls for “Snowpark expresses transformations using supported languages and executes data operations close to governed tables”: This mechanism explains why the proposed action fits the scenario: Use Snowpark DataFrames with transformations executed by Snowflake compute.
C:This mechanism explains why the proposed action fits the scenario: Consider Query Acceleration Service for eligible selective large scans and aggregations. That explains the role of “QAS can offload parts of supported long-running queries to shared compute resources”, but the present requirement calls for “Snowpark expresses transformations using supported languages and executes data operations close to governed tables”: This mechanism explains why the proposed action fits the scenario: Use Snowpark DataFrames with transformations executed by Snowflake compute.
Question 375
An architecture reviewer proposes the following solution: Move authentication to supported secure identity or credential storage and remove literals from source. The business and technical requirement is: A secure automation script currently embeds account passwords directly in a committed repository. Which explanation most accurately justifies this choice?
- VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements.
- Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
- Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently.
- Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset.
Explanation
Correct Answer
B:Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords. This mechanism explains why the proposed action fits the scenario: Move authentication to supported secure identity or credential storage and remove literals from source. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate Virtual Private Snowflake and its dedicated infrastructure requirements. That explains the role of “VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements”, but the present requirement calls for “Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords”: This mechanism explains why the proposed action fits the scenario: Move authentication to supported secure identity or credential storage and remove literals from source.
C:This mechanism explains why the proposed action fits the scenario: Set a statement timeout or warehouse timeout with auto-suspend and monitoring as appropriate. That explains the role of “Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently”, but the present requirement calls for “Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords”: This mechanism explains why the proposed action fits the scenario: Move authentication to supported secure identity or credential storage and remove literals from source.
D:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake Secure Data Sharing as a governed cross-account access pattern. That explains the role of “Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset”, but the present requirement calls for “Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords”: This mechanism explains why the proposed action fits the scenario: Move authentication to supported secure identity or credential storage and remove literals from source.
Question 376
An architecture reviewer proposes the following solution: Delegate policy management to a controlled governance role and review ownership and grants. The business and technical requirement is: A Snowflake account must document creation and modification permissions for sensitive masking policies. Which explanation most accurately justifies this choice?
- Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
- The active session role context determines which object privileges are available.
- Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste.
- Query metadata supports operational reporting of status, user, role and execution context.
Explanation
Correct Answer
A:Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers. This mechanism explains why the proposed action fits the scenario: Delegate policy management to a controlled governance role and review ownership and grants. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Inspect CURRENT_ROLE and effective primary or secondary role grants for the session. That explains the role of “The active session role context determines which object privileges are available”, but the present requirement calls for “Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers”: This mechanism explains why the proposed action fits the scenario: Delegate policy management to a controlled governance role and review ownership and grants.
C:This mechanism explains why the proposed action fits the scenario: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually. That explains the role of “Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste”, but the present requirement calls for “Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers”: This mechanism explains why the proposed action fits the scenario: Delegate policy management to a controlled governance role and review ownership and grants.
D: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 “Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers”: This mechanism explains why the proposed action fits the scenario: Delegate policy management to a controlled governance role and review ownership and grants.
Question 377
An architecture reviewer proposes the following solution: Use the official Snowflake Python Connector with the intended secure session settings. The business and technical requirement is: A Python application must issue authenticated SQL queries against Snowflake from an application container. Which explanation most accurately justifies this choice?
- Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval.
- Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
- Streams track the table changes visible between transactional consumption points without cloning the full table each time.
- The supported connector provides SQL execution over an authenticated client session.
Explanation
Correct Answer
D:The supported connector provides SQL execution over an authenticated client session. This mechanism explains why the proposed action fits the scenario: Use the official Snowflake Python Connector with the intended secure session settings. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Explain target lag as a desired freshness bound and monitor actual refresh timing. That explains the role of “Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval”, but the present requirement calls for “The supported connector provides SQL execution over an authenticated client session”: This mechanism explains why the proposed action fits the scenario: Use the official Snowflake Python Connector with the intended secure session settings.
B: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 “The supported connector provides SQL execution over an authenticated client session”: This mechanism explains why the proposed action fits the scenario: Use the official Snowflake Python Connector with the intended secure session settings.
C:This mechanism explains why the proposed action fits the scenario: Create a stream on the source table to expose its change data capture records. That explains the role of “Streams track the table changes visible between transactional consumption points without cloning the full table each time”, but the present requirement calls for “The supported connector provides SQL execution over an authenticated client session”: This mechanism explains why the proposed action fits the scenario: Use the official Snowflake Python Connector with the intended secure session settings.
Question 378
An architecture reviewer proposes the following solution: Aggregate child rows or select the intended relationship keys before joining. The business and technical requirement is: A developer needs to guarantee a reporting calculation does not duplicate rows when joining one-to-many tables. Which explanation most accurately justifies this choice?
- A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
- ECONOMY prioritizes fuller use of existing clusters before starting more compute.
- Joining a one-to-many table without accounting for cardinality can multiply logical fact values.
- Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
Explanation
Correct Answer
C:Joining a one-to-many table without accounting for cardinality can multiply logical fact values. This mechanism explains why the proposed action fits the scenario: Aggregate child rows or select the intended relationship keys before joining. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands. That explains the role of “A specialized warehouse might provide better memory characteristics for supported Snowpark jobs”, but the present requirement calls for “Joining a one-to-many table without accounting for cardinality can multiply logical fact values”: This mechanism explains why the proposed action fits the scenario: Aggregate child rows or select the intended relationship keys before joining.
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 “Joining a one-to-many table without accounting for cardinality can multiply logical fact values”: This mechanism explains why the proposed action fits the scenario: Aggregate child rows or select the intended relationship keys before joining.
D:This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata. That explains the role of “Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually”, but the present requirement calls for “Joining a one-to-many table without accounting for cardinality can multiply logical fact values”: This mechanism explains why the proposed action fits the scenario: Aggregate child rows or select the intended relationship keys before joining.
Question 379
An architecture reviewer proposes the following solution: Evaluate scaling the warehouse up after confirming memory spill in Query Profile. The business and technical requirement is: A query repeatedly spills to remote storage because a large join cannot fit in available warehouse memory. Which explanation most accurately justifies this choice?
- Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
- Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
- Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
- Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
Explanation
Correct Answer
B:Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query. This mechanism explains why the proposed action fits the scenario: Evaluate scaling the warehouse up after confirming memory spill in Query Profile. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization. That explains the role of “Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution”, but the present requirement calls for “Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query”: This mechanism explains why the proposed action fits the scenario: Evaluate scaling the warehouse up after confirming memory spill in Query Profile.
C: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 “Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query”: This mechanism explains why the proposed action fits the scenario: Evaluate scaling the warehouse up after confirming memory spill in Query Profile.
D:This mechanism explains why the proposed action fits the scenario: Use a dynamic table with an explicit target lag and warehouse for eligible transformations. That explains the role of “Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules”, but the present requirement calls for “Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query”: This mechanism explains why the proposed action fits the scenario: Evaluate scaling the warehouse up after confirming memory spill in Query Profile.
Question 380
An architecture reviewer proposes the following solution: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies. The business and technical requirement is: A legal team requests an inventory of locations where particular personal data elements are copied across schemas. Which explanation most accurately justifies this choice?
- Managing identities and accessing all customer tables are distinct authorization duties.
- Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
- Authorization revocation separates identity lifecycle from destructive changes to stored data.
- OAuth enables delegated token-based authentication while token and role privileges still constrain data access.
Explanation
Correct Answer
B:Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets. This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use user-management privileges or the appropriate system administration role without broad data grants. That explains the role of “Managing identities and accessing all customer tables are distinct authorization duties”, but the present requirement calls for “Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets”: This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.
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 “Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets”: This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.
D:This mechanism explains why the proposed action fits the scenario: Configure a supported OAuth security integration and validate granted session role behavior. That explains the role of “OAuth enables delegated token-based authentication while token and role privileges still constrain data access”, but the present requirement calls for “Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets”: This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.