Snowpro Core Recertification Free Sample Questions

The Search Optimization Service can be configured for specific columns. By targeting only the columns used in point-lookup queries (e.g., WHERE column = 'value'), the size of the search access path and its associated maintenance and storage costs can be significantly reduced. Increasing warehouse size affects compute, not storage costs of this service. Disabling the service removes the performance benefit. Reclustering the table is a different optimization technique that wouldn't reduce the search access path's storage cost.

Dynamic Tables are designed for building declarative data pipelines. You define the target table using a SQL query, and Snowflake automatically manages the refresh process to keep it synchronized with the source tables. This abstracts away the complexity of managing streams, tasks, and dependencies, which is the primary drawback of the traditional approach for this use case. Materialized views are for accelerating queries on a single table, not for complex multi-table transformations.

An API Integration is required to securely store the credentials needed to authenticate with the Git provider (e.g., GitHub, GitLab).

A Git Repository Stage is a new type of stage object that represents the linked Git repository within Snowflake, allowing you to access files from it.

The statement is false. The 'Suspend & Notify' action allows currently running queries to complete before suspending the warehouse. Only the 'Suspend Immediately & Notify' action will cancel all running queries and statements before suspending the warehouse.

Snowpark Container Services enables the deployment of OCI-compliant containers directly within Snowflake's compute infrastructure. This is the ideal solution for running containerized applications like complex ML models, ensuring data remains within Snowflake's security boundary and eliminating the need for external infrastructure management. External Functions call out to external services, while Java/Python UDFs/UDTFs run code within Snowflake's environment but do not support full container deployment.

Snowflake Data Clean Rooms provide a secure environment where multiple parties can collaborate on sensitive data without sharing the raw data itself. Each party maintains control over their data, and they can run joint queries with predefined restrictions to protect privacy. This directly addresses the requirement for privacy-preserving analysis without data movement. While Secure Data Sharing with policies is a component, the 'Clean Room' concept holistically addresses this specific multi-party collaboration use case.

Hybrid Tables, the core of Snowflake's Unistore workload, are designed for Hybrid Transactional/Analytical Processing (HTAP). They use a row-based storage engine for fast, single-row operations (transactional) while integrating with Snowflake's existing columnar engine for fast analytical scans. This allows a single table to efficiently serve both types of queries.

The IS_ROLE_IN_SESSION() function is specifically designed to be used within masking and row access policies. It checks if the specified role (e.g., 'ANALYST') is in the hierarchy of the current active primary or secondary roles for the user executing the query. This allows for conditional logic within the policy body. CURRENT_ROLE() only returns the primary active role, and CURRENT_USER() returns the user name, not their roles.

Streamlit in Snowflake allows users to build, deploy, and share interactive data applications using Python, all within Snowflake's secure environment. It is specifically designed for rapidly creating data-centric web apps without needing front-end web development skills. Snowsight is for dashboards, and the Python Connector is a library for connecting to Snowflake from an external Python application, but it doesn't provide the application framework or hosting.

The RESULT_SCAN command is used to retrieve results from a previous query. When Snowflake can reuse the results of a previously executed query from the result cache, it does so without engaging a virtual warehouse for computation. This is a key performance and cost-saving feature. The local disk cache is used for data, not query results, and if a warehouse were used, the query profile would show compute activity.