SnowPro Core COF-C03 Practice Test 60
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.
Question 591
During a pilot, engineers pursued an unrelated workaround: Use common table expressions with the WITH clause to organize query stages. The required outcome remained unsatisfied: A report needs subtotals by region and an overall grand total from one grouped query. Which correction should the team prioritize?
- Create a supported SQL UDF with clear input and output types.
- Use common table expressions with the WITH clause to organize query stages.
- Use ROLLUP or supported GROUPING SETS for the required subtotal levels.
- Use MERGE with defined match keys and explicit update and insert branches.
Explanation
Correct Answer
C:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. The corrective step addresses the missing requirement: A report needs subtotals by region and an overall grand total from one grouped query. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 ROLLUP or supported GROUPING SETS for the required subtotal levels”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
B:CTEs structure intermediate logic for readability while still permitting optimizer planning. That explains the role of “Use common table expressions with the WITH clause to organize query stages”, but the present requirement calls for “Use ROLLUP or supported GROUPING SETS for the required subtotal levels”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
D:MERGE combines conditional matched and unmatched DML paths in one operation. That explains the role of “Use MERGE with defined match keys and explicit update and insert branches”, but the present requirement calls for “Use ROLLUP or supported GROUPING SETS for the required subtotal levels”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
Question 592
During a pilot, engineers pursued an unrelated workaround: Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse. The required outcome remained unsatisfied: Hundreds of dashboard queries are queued during business hours although individual queries finish quickly. Which correction should the team prioritize?
- Evaluate scaling the warehouse up after confirming memory spill in Query Profile.
- Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse.
- Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
- Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously.
Explanation
Correct Answer
C:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. The corrective step addresses the missing requirement: Hundreds of dashboard queries are queued during business hours although individual queries finish quickly. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query. That explains the role of “Evaluate scaling the warehouse up after confirming memory spill in Query Profile”, but the present requirement calls for “Use an appropriately configured multi-cluster warehouse to increase concurrent capacity”: Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
B:Auto-suspend stops idle compute while auto-resume restarts it for eligible queries. That explains the role of “Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse”, but the present requirement calls for “Use an appropriately configured multi-cluster warehouse to increase concurrent capacity”: Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
D:Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds. That explains the role of “Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously”, but the present requirement calls for “Use an appropriately configured multi-cluster warehouse to increase concurrent capacity”: Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
Question 593
During a pilot, engineers pursued an unrelated workaround: Evaluate row access filtering and column masking independently with representative roles. The required outcome remained unsatisfied: A column with telephone numbers must appear partially redacted but remain useful for matching last-four digits in an authorized service desk. Which correction should the team prioritize?
- Evaluate row access filtering and column masking independently with representative roles.
- Restrict grants and implement an approved secure projection with scoped consumer roles.
- Implement a governed masking expression that exposes only the permitted suffix.
- Move the row restriction into a row access policy on the table or governed view.
Explanation
Correct Answer
C:Column masking can transform visible values for less-privileged roles without changing stored source values. The corrective step addresses the missing requirement: A column with telephone numbers must appear partially redacted but remain useful for matching last-four digits in an authorized service desk. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Implement a governed masking expression that exposes only the permitted suffix”: Column masking can transform visible values for less-privileged roles without changing stored source values.
B:Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data. That explains the role of “Restrict grants and implement an approved secure projection with scoped consumer roles”, but the present requirement calls for “Implement a governed masking expression that exposes only the permitted suffix”: Column masking can transform visible values for less-privileged roles without changing stored source values.
D:Application-level filtering is not a reliable security boundary for users with direct query access. That explains the role of “Move the row restriction into a row access policy on the table or governed view”, but the present requirement calls for “Implement a governed masking expression that exposes only the permitted suffix”: Column masking can transform visible values for less-privileged roles without changing stored source values.
Question 594
During a pilot, engineers pursued an unrelated workaround: Use the supported Snowflake JDBC driver with correct account and authentication configuration. The required outcome remained unsatisfied: A BI tool only supports ODBC DSNs and must connect to a Snowflake reporting warehouse. Which correction should the team prioritize?
- Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint.
- Use a Snowflake storage integration and controlled external stage grants.
- Use the supported Snowflake JDBC driver with correct account and authentication configuration.
- Configure a Snowflake ODBC driver and approved connection profile.
Explanation
Correct Answer
D:The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet. The corrective step addresses the missing requirement: A BI tool only supports ODBC DSNs and must connect to a Snowflake reporting warehouse. 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 “Configure a Snowflake ODBC driver and approved connection profile”: The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet.
B: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 “Configure a Snowflake ODBC driver and approved connection profile”: The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet.
C:JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions. That explains the role of “Use the supported Snowflake JDBC driver with correct account and authentication configuration”, but the present requirement calls for “Configure a Snowflake ODBC driver and approved connection profile”: The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet.
Question 595
During a pilot, engineers pursued an unrelated workaround: Use an appropriate Snowflake stored procedure under defined owner or caller rights. The required outcome remained unsatisfied: An analytics team wants reusable named subqueries to make a long Snowflake SELECT easier to review. Which correction should the team prioritize?
- Create a supported SQL UDF with clear input and output types.
- Use ROLLUP or supported GROUPING SETS for the required subtotal levels.
- Use an appropriate Snowflake stored procedure under defined owner or caller rights.
- Use common table expressions with the WITH clause to organize query stages.
Explanation
Correct Answer
D:CTEs structure intermediate logic for readability while still permitting optimizer planning. The corrective step addresses the missing requirement: An analytics team wants reusable named subqueries to make a long Snowflake SELECT easier to review. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 common table expressions with the WITH clause to organize query stages”: CTEs structure intermediate logic for readability while still permitting optimizer planning.
B:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. That explains the role of “Use ROLLUP or supported GROUPING SETS for the required subtotal levels”, but the present requirement calls for “Use common table expressions with the WITH clause to organize query stages”: CTEs structure intermediate logic for readability while still permitting optimizer planning.
C: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 “Use common table expressions with the WITH clause to organize query stages”: CTEs structure intermediate logic for readability while still permitting optimizer planning.
Question 596
During a pilot, engineers pursued an unrelated workaround: Evaluate Virtual Private Snowflake and its dedicated infrastructure requirements. The required outcome remained unsatisfied: A warehouse continues consuming credits all night despite no workload demand. Which correction should the team prioritize?
- Select an edition that explicitly includes the required enterprise security or governance capabilities.
- Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior.
- Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse.
- Evaluate Virtual Private Snowflake and its dedicated infrastructure requirements.
Explanation
Correct Answer
C:Auto-suspend stops idle compute while auto-resume restarts it for eligible queries. The corrective step addresses the missing requirement: A warehouse continues consuming credits all night despite no workload demand. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists. That explains the role of “Select an edition that explicitly includes the required enterprise security or governance capabilities”, but the present requirement calls for “Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse”: Auto-suspend stops idle compute while auto-resume restarts it for eligible queries.
B:Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries. That explains the role of “Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior”, but the present requirement calls for “Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse”: Auto-suspend stops idle compute while auto-resume restarts it for eligible queries.
D:VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements. That explains the role of “Evaluate Virtual Private Snowflake and its dedicated infrastructure requirements”, but the present requirement calls for “Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse”: Auto-suspend stops idle compute while auto-resume restarts it for eligible queries.
Question 597
During a pilot, engineers pursued an unrelated workaround: Create and apply governed Snowflake object tags with approved allowed values where suitable. The required outcome remained unsatisfied: A governance review finds tags applied inconsistently to objects created by different engineering teams. Which correction should the team prioritize?
- Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks.
- Delegate policy management to a controlled governance role and review ownership and grants.
- Create and apply governed Snowflake object tags with approved allowed values where suitable.
- Apply a row access policy that filters rows based on authorized role or mapping context.
Explanation
Correct Answer
A:Consistent tag semantics support reliable downstream policy and reporting behavior. The corrective step addresses the missing requirement: A governance review finds tags applied inconsistently to objects created by different engineering teams. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers. That explains the role of “Delegate policy management to a controlled governance role and review ownership and grants”, but the present requirement calls for “Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks”: Consistent tag semantics support reliable downstream policy and reporting behavior.
C:Tags attach reusable metadata that downstream inventory and governance queries can evaluate. That explains the role of “Create and apply governed Snowflake object tags with approved allowed values where suitable”, but the present requirement calls for “Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks”: Consistent tag semantics support reliable downstream policy and reporting behavior.
D: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 “Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks”: Consistent tag semantics support reliable downstream policy and reporting behavior.
Question 598
During a pilot, engineers pursued an unrelated workaround: Separate transport and authentication diagnostics from later SQL execution errors. The required outcome remained unsatisfied: A data platform receives events from an Apache Kafka cluster and wants a managed integration into Snowflake. Which correction should the team prioritize?
- Separate transport and authentication diagnostics from later SQL execution errors.
- Use the official Snowflake Python Connector with the intended secure session settings.
- Use supported external access integrations and secret objects for approved network destinations.
- Evaluate the supported Snowflake Connector for Kafka and its delivery mode.
Explanation
Correct Answer
D:Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling. The corrective step addresses the missing requirement: A data platform receives events from an Apache Kafka cluster and wants a managed integration into Snowflake. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Network restrictions can reject a connection before a query reaches Snowflake's optimizer. That explains the role of “Separate transport and authentication diagnostics from later SQL execution errors”, but the present requirement calls for “Evaluate the supported Snowflake Connector for Kafka and its delivery mode”: Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
B: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 “Evaluate the supported Snowflake Connector for Kafka and its delivery mode”: Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
C: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 “Evaluate the supported Snowflake Connector for Kafka and its delivery mode”: Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
Question 599
During a pilot, engineers pursued an unrelated workaround: Use an appropriate Snowflake stored procedure under defined owner or caller rights. The required outcome remained unsatisfied: A business report needs the top three invoices per customer while keeping all other columns intact. Which correction should the team prioritize?
- Use an appropriate Snowflake stored procedure under defined owner or caller rights.
- Use MERGE with defined match keys and explicit update and insert branches.
- Use LAG in a partitioned, ordered window expression.
- Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3.
Explanation
Correct Answer
D:Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns. The corrective step addresses the missing requirement: A business report needs the top three invoices per customer while keeping all other columns intact. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3”: Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
B:MERGE combines conditional matched and unmatched DML paths in one operation. That explains the role of “Use MERGE with defined match keys and explicit update and insert branches”, but the present requirement calls for “Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3”: Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
C: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 “Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3”: Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
Question 600
During a pilot, engineers pursued an unrelated workaround: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity. The required outcome remained unsatisfied: A time-critical dashboard prefers responsiveness over minimizing the credits of additional multi-cluster capacity. Which correction should the team prioritize?
- Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
- Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously.
- Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior.
- Select the STANDARD scaling policy for a supported multi-cluster warehouse.
Explanation
Correct Answer
D:Standard policy starts clusters more aggressively to limit waiting under rising concurrency. The corrective step addresses the missing requirement: A time-critical dashboard prefers responsiveness over minimizing the credits of additional multi-cluster capacity. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Select the STANDARD scaling policy for a supported multi-cluster warehouse”: Standard policy starts clusters more aggressively to limit waiting under rising concurrency.
B:Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds. That explains the role of “Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously”, but the present requirement calls for “Select the STANDARD scaling policy for a supported multi-cluster warehouse”: Standard policy starts clusters more aggressively to limit waiting under rising concurrency.
C:Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries. That explains the role of “Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior”, but the present requirement calls for “Select the STANDARD scaling policy for a supported multi-cluster warehouse”: Standard policy starts clusters more aggressively to limit waiting under rising concurrency.