SnowPro Core COF-C03 Practice Test 59
Question 580
During a pilot, engineers pursued an unrelated workaround: Move authentication to supported secure identity or credential storage and remove literals from source. The required outcome remained unsatisfied: An analyst has access to multiple warehouses and accidentally runs long ETL SQL on the shared BI warehouse. Which correction should the team prioritize?
- Select the intended warehouse in the session or connection before executing the job.
- Use the supported Snowflake CLI and authenticated configuration for scripted deployment.
- Move authentication to supported secure identity or credential storage and remove literals from source.
- Validate the supported Snowflake account identifier and connection endpoint configuration.
Explanation
Correct Answer
A:Session warehouse context controls the compute resource charged for a query. The corrective step addresses the missing requirement: An analyst has access to multiple warehouses and accidentally runs long ETL SQL on the shared BI warehouse. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:CLI workflows allow controlled automation and environment selection without fragile UI clicking. That explains the role of “Use the supported Snowflake CLI and authenticated configuration for scripted deployment”, but the present requirement calls for “Select the intended warehouse in the session or connection before executing the job”: Session warehouse context controls the compute resource charged for a query.
C:Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords. That explains the role of “Move authentication to supported secure identity or credential storage and remove literals from source”, but the present requirement calls for “Select the intended warehouse in the session or connection before executing the job”: Session warehouse context controls the compute resource charged for a query.
D:Client connections must target the correct account and supported hostname rather than an arbitrary database display label. That explains the role of “Validate the supported Snowflake account identifier and connection endpoint configuration”, but the present requirement calls for “Select the intended warehouse in the session or connection before executing the job”: Session warehouse context controls the compute resource charged for a query.
Question 581
During a pilot, engineers pursued an unrelated workaround: Attach Snowflake governance policies at the data object instead of implementing separate app-only filters. The required outcome remained unsatisfied: A report uses an arbitrary WHERE clause to hide other departments' records but users can bypass the report with SQL. Which correction should the team prioritize?
- Attach Snowflake governance policies at the data object instead of implementing separate app-only filters.
- Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks.
- Use Snowflake-supported access history with an authorized investigation role.
- Move the row restriction into a row access policy on the table or governed view.
Explanation
Correct Answer
D:Application-level filtering is not a reliable security boundary for users with direct query access. The corrective step addresses the missing requirement: A report uses an arbitrary WHERE clause to hide other departments' records but users can bypass the report with SQL. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Data-level controls travel with queries across clients and minimize inconsistent authorization behavior. That explains the role of “Attach Snowflake governance policies at the data object instead of implementing separate app-only filters”, but the present requirement calls for “Move the row restriction into a row access policy on the table or governed view”: Application-level filtering is not a reliable security boundary for users with direct query access.
B:Consistent tag semantics support reliable downstream policy and reporting behavior. That explains the role of “Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks”, but the present requirement calls for “Move the row restriction into a row access policy on the table or governed view”: Application-level filtering is not a reliable security boundary for users with direct query access.
C:Access history exposes which objects or columns were referenced, supporting data governance investigation. That explains the role of “Use Snowflake-supported access history with an authorized investigation role”, but the present requirement calls for “Move the row restriction into a row access policy on the table or governed view”: Application-level filtering is not a reliable security boundary for users with direct query access.
Question 582
During a pilot, engineers pursued an unrelated workaround: Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation. The required outcome remained unsatisfied: A pipeline team wants to monitor lag and recent failures for every dynamic table in an account. Which correction should the team prioritize?
- Consume the stream with a committed downstream DML transaction.
- Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table.
- Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation.
- Query supported dynamic table information-schema status and refresh history views.
Explanation
Correct Answer
D:Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values. The corrective step addresses the missing requirement: A pipeline team wants to monitor lag and recent failures for every dynamic table in an account. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:A stream offset advances when its changes are consumed by a committed transactional operation. That explains the role of “Consume the stream with a committed downstream DML transaction”, but the present requirement calls for “Query supported dynamic table information-schema status and refresh history views”: Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
B:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. That explains the role of “Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table”, but the present requirement calls for “Query supported dynamic table information-schema status and refresh history views”: Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
C:Change-based processing limits recomputation when the SQL pattern and source changes support incremental work. That explains the role of “Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation”, but the present requirement calls for “Query supported dynamic table information-schema status and refresh history views”: Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
Question 583
During a pilot, engineers pursued an unrelated workaround: Use supported PIVOT syntax with a defined aggregate and category list. The required outcome remained unsatisfied: Data scientists want to transform tables with Python DataFrame semantics without exporting huge datasets. Which correction should the team prioritize?
- Use LAG in a partitioned, ordered window expression.
- Create a supported SQL UDF with clear input and output types.
- Use Snowpark DataFrames with transformations executed by Snowflake compute.
- Use supported PIVOT syntax with a defined aggregate and category list.
Explanation
Correct Answer
C:Snowpark expresses transformations using supported languages and executes data operations close to governed tables. The corrective step addresses the missing requirement: Data scientists want to transform tables with Python DataFrame semantics without exporting huge datasets. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset. That explains the role of “Use LAG in a partitioned, ordered window expression”, but the present requirement calls for “Use Snowpark DataFrames with transformations executed by Snowflake compute”: Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
B:A UDF encapsulates deterministic reusable expression logic in a governed database object. That explains the role of “Create a supported SQL UDF with clear input and output types”, but the present requirement calls for “Use Snowpark DataFrames with transformations executed by Snowflake compute”: Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
D:PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output. That explains the role of “Use supported PIVOT syntax with a defined aggregate and category list”, but the present requirement calls for “Use Snowpark DataFrames with transformations executed by Snowflake compute”: Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
Question 584
During a pilot, engineers pursued an unrelated workaround: Check effective session context and precedence of explicit USE statements over connection defaults. The required outcome remained unsatisfied: A secure automation script currently embeds account passwords directly in a committed repository. Which correction should the team prioritize?
- Move authentication to supported secure identity or credential storage and remove literals from source.
- Use the supported Snowflake CLI and authenticated configuration for scripted deployment.
- Validate the supported Snowflake account identifier and connection endpoint configuration.
- Check effective session context and precedence of explicit USE statements over connection defaults.
Explanation
Correct Answer
A:Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords. The corrective step addresses the missing requirement: A secure automation script currently embeds account passwords directly in a committed repository. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:CLI workflows allow controlled automation and environment selection without fragile UI clicking. That explains the role of “Use the supported Snowflake CLI and authenticated configuration for scripted deployment”, but the present requirement calls for “Move authentication to supported secure identity or credential storage and remove literals from source”: Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
C:Client connections must target the correct account and supported hostname rather than an arbitrary database display label. That explains the role of “Validate the supported Snowflake account identifier and connection endpoint configuration”, but the present requirement calls for “Move authentication to supported secure identity or credential storage and remove literals from source”: Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
D:An explicit session command changes the active namespace used for later unqualified SQL references. That explains the role of “Check effective session context and precedence of explicit USE statements over connection defaults”, but the present requirement calls for “Move authentication to supported secure identity or credential storage and remove literals from source”: Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
Question 585
During a pilot, engineers pursued an unrelated workaround: Use Snowflake-supported access history with an authorized investigation role. The required outcome remained unsatisfied: A Snowflake account must document creation and modification permissions for sensitive masking policies. Which correction should the team prioritize?
- Apply a row access policy that filters rows based on authorized role or mapping context.
- Delegate policy management to a controlled governance role and review ownership and grants.
- Use Snowflake-supported access history with an authorized investigation role.
- Evaluate row access filtering and column masking independently with representative roles.
Explanation
Correct Answer
B:Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers. The corrective step addresses the missing requirement: A Snowflake account must document creation and modification permissions for sensitive masking policies. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Row access policies enforce row-level visibility in queries independently of front-end filters. That explains the role of “Apply a row access policy that filters rows based on authorized role or mapping context”, but the present requirement calls for “Delegate policy management to a controlled governance role and review ownership and grants”: Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
C:Access history exposes which objects or columns were referenced, supporting data governance investigation. That explains the role of “Use Snowflake-supported access history with an authorized investigation role”, but the present requirement calls for “Delegate policy management to a controlled governance role and review ownership and grants”: Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
D:Row access governs record visibility while masking governs values in visible rows, so they must be tested separately. That explains the role of “Evaluate row access filtering and column masking independently with representative roles”, but the present requirement calls for “Delegate policy management to a controlled governance role and review ownership and grants”: Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
Question 586
During a pilot, engineers pursued an unrelated workaround: Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint. The required outcome remained unsatisfied: A Python application must issue authenticated SQL queries against Snowflake from an application container. Which correction should the team prioritize?
- Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint.
- Use the official Snowflake Python Connector with the intended secure session settings.
- Use a Snowflake storage integration and controlled external stage grants.
- Use supported external access integrations and secret objects for approved network destinations.
Explanation
Correct Answer
B:The supported connector provides SQL execution over an authenticated client session. The corrective step addresses the missing requirement: A Python application must issue authenticated SQL queries against Snowflake from an application container. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Private network access relies on cloud routing and DNS as well as Snowflake account policies. That explains the role of “Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint”, but the present requirement calls for “Use the official Snowflake Python Connector with the intended secure session settings”: The supported connector provides SQL execution over an authenticated client session.
C:Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access. That explains the role of “Use a Snowflake storage integration and controlled external stage grants”, but the present requirement calls for “Use the official Snowflake Python Connector with the intended secure session settings”: The supported connector provides SQL execution over an authenticated client session.
D:Controlled external access isolates network destinations and credentials from routine SQL code. That explains the role of “Use supported external access integrations and secret objects for approved network destinations”, but the present requirement calls for “Use the official Snowflake Python Connector with the intended secure session settings”: The supported connector provides SQL execution over an authenticated client session.
Question 587
During a pilot, engineers pursued an unrelated workaround: Use LAG in a partitioned, ordered window expression. The required outcome remained unsatisfied: A developer needs to guarantee a reporting calculation does not duplicate rows when joining one-to-many tables. Which correction should the team prioritize?
- Use LAG in a partitioned, ordered window expression.
- Create a supported SQL UDF with clear input and output types.
- Aggregate child rows or select the intended relationship keys before joining.
- Use an appropriate Snowflake stored procedure under defined owner or caller rights.
Explanation
Correct Answer
C:Joining a one-to-many table without accounting for cardinality can multiply logical fact values. The corrective step addresses the missing requirement: A developer needs to guarantee a reporting calculation does not duplicate rows when joining one-to-many tables. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset. That explains the role of “Use LAG in a partitioned, ordered window expression”, but the present requirement calls for “Aggregate child rows or select the intended relationship keys before joining”: Joining a one-to-many table without accounting for cardinality can multiply logical fact values.
B:A UDF encapsulates deterministic reusable expression logic in a governed database object. That explains the role of “Create a supported SQL UDF with clear input and output types”, but the present requirement calls for “Aggregate child rows or select the intended relationship keys before joining”: Joining a one-to-many table without accounting for cardinality can multiply logical fact values.
D:Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression. That explains the role of “Use an appropriate Snowflake stored procedure under defined owner or caller rights”, but the present requirement calls for “Aggregate child rows or select the intended relationship keys before joining”: Joining a one-to-many table without accounting for cardinality can multiply logical fact values.
Question 588
During a pilot, engineers pursued an unrelated workaround: Assign ingestion to its own appropriately sized virtual warehouse. The required outcome remained unsatisfied: A query repeatedly spills to remote storage because a large join cannot fit in available warehouse memory. Which correction should the team prioritize?
- Assign ingestion to its own appropriately sized virtual warehouse.
- Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
- Evaluate scaling the warehouse up after confirming memory spill in Query Profile.
- Use the ECONOMY scaling policy on the supported auto-scale warehouse.
Explanation
Correct Answer
C:Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query. The corrective step addresses the missing requirement: A query repeatedly spills to remote storage because a large join cannot fit in available warehouse memory. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Workload warehouse separation isolates query contention and cost attribution across departments. That explains the role of “Assign ingestion to its own appropriately sized virtual warehouse”, but the present requirement calls for “Evaluate scaling the warehouse up after confirming memory spill in Query Profile”: Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
B:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. That explains the role of “Use an appropriately configured multi-cluster warehouse to increase concurrent capacity”, but the present requirement calls for “Evaluate scaling the warehouse up after confirming memory spill in Query Profile”: Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
D:Economy favors better cluster utilization before adding parallel compute capacity. That explains the role of “Use the ECONOMY scaling policy on the supported auto-scale warehouse”, but the present requirement calls for “Evaluate scaling the warehouse up after confirming memory spill in Query Profile”: Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
Question 589
During a pilot, engineers pursued an unrelated workaround: Combine role-based access with monitored egress controls and approved data governance policies. The required outcome remained unsatisfied: A legal team requests an inventory of locations where particular personal data elements are copied across schemas. Which correction should the team prioritize?
- Attach Snowflake governance policies at the data object instead of implementing separate app-only filters.
- Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.
- Apply a row access policy that filters rows based on authorized role or mapping context.
- Combine role-based access with monitored egress controls and approved data governance policies.
Explanation
Correct Answer
B:Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets. The corrective step addresses the missing requirement: A legal team requests an inventory of locations where particular personal data elements are copied across schemas. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Data-level controls travel with queries across clients and minimize inconsistent authorization behavior. That explains the role of “Attach Snowflake governance policies at the data object instead of implementing separate app-only filters”, but the present requirement calls for “Use data classification, catalog tags and lineage to identify relevant data objects and dependencies”: Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
C:Row access policies enforce row-level visibility in queries independently of front-end filters. That explains the role of “Apply a row access policy that filters rows based on authorized role or mapping context”, but the present requirement calls for “Use data classification, catalog tags and lineage to identify relevant data objects and dependencies”: Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
D:Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation. That explains the role of “Combine role-based access with monitored egress controls and approved data governance policies”, but the present requirement calls for “Use data classification, catalog tags and lineage to identify relevant data objects and dependencies”: Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
Question 590
During a pilot, engineers pursued an unrelated workaround: Use supported external access integrations and secret objects for approved network destinations. The required outcome remained unsatisfied: A Java analytics service requires a stable database interface for pooled SQL connections. Which correction should the team prioritize?
- Configure a supported API integration with the required external-function security boundary.
- Use supported external access integrations and secret objects for approved network destinations.
- Use the official Snowflake Python Connector with the intended secure session settings.
- Use the supported Snowflake JDBC driver with correct account and authentication configuration.
Explanation
Correct Answer
D:JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions. The corrective step addresses the missing requirement: A Java analytics service requires a stable database interface for pooled SQL connections. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions. That explains the role of “Configure a supported API integration with the required external-function security boundary”, but the present requirement calls for “Use the supported Snowflake JDBC driver with correct account and authentication configuration”: JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions.
B:Controlled external access isolates network destinations and credentials from routine SQL code. That explains the role of “Use supported external access integrations and secret objects for approved network destinations”, but the present requirement calls for “Use the supported Snowflake JDBC driver with correct account and authentication configuration”: JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions.
C:The supported connector provides SQL execution over an authenticated client session. That explains the role of “Use the official Snowflake Python Connector with the intended secure session settings”, but the present requirement calls for “Use the supported Snowflake JDBC driver with correct account and authentication configuration”: JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions.