How would you determine the size of the virtual warehouse used for a task?
Correct Answer: D
The size of the virtual warehouse for a task can be configured to handle concurrency automatically using a Multi-cluster warehouse (MCW). This is because tasks are designed to run their body on a schedule, and MCW allows for scaling compute resources to match the task's execution needs without manual intervention. References: [ COF-C03 ] SnowPro Core Certification Exam Study Guide
Question 487
What is a machine learning and data science partner within the Snowflake Partner Ecosystem?
Correct Answer: D
Data Robot is recognized as a machine learning and data science partner within the Snowflake Partner Ecosystem. It provides an enterprise AI platform that enables users to build and deploy accurate predictive models quickly. As a partner, Data Robot integrates with Snowflake to enhance data science capabilities2. References: [ COF-C03 ] SnowPro Core Certification Exam Study Guide Snowflake Documentation on Machine Learning & Data Science Partners https://docs.snowflake.com/en/user-guide/ecosystem-analytics.html
Question 488
What happens to the shared objects for users in a consumer account from a share, once a database has been created in that account?
Correct Answer: C
Once a database has been created in a consumer account from a share, the shared objects become accessible to users in that account.The shared objects are not transferred or copied; they remain in the provider's account and are accessible to the consumer account
Question 489
Which view or feature can be used to analyze query performance and identify which operations are the most time-consuming?
Correct Answer: C
Query Profile displays the execution plan for an individual query as a set of operator nodes. Each node represents an operation such as a table scan, filter, join, aggregate, sort, or data unload and shows the percentage of the query duration consumed by that operation. The Most Expensive Nodes pane identifies the operators that required the greatest execution time, allowing users to focus on the primary bottlenecks. QUERY_HISTORY provides statement-level timing, warehouse, status, and resource metrics but does not by itself provide the same operator-level graphical analysis. WAREHOUSE_LOAD_HISTORY helps evaluate warehouse load and queuing, while Search Optimization Service is a performance feature rather than a diagnostic view. Therefore, Query Profile is the appropriate tool for determining which individual operations consume the most execution time.
