{"id":13479,"date":"2026-09-16T09:14:10","date_gmt":"2026-09-16T09:14:10","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=13479"},"modified":"2026-09-16T09:14:10","modified_gmt":"2026-09-16T09:14:10","slug":"snowflake-snowpro-core-practice-test-questions-and-exam-dumps-part9-q161-180","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-core-practice-test-questions-and-exam-dumps-part9-q161-180\/","title":{"rendered":"Snowflake SnowPro Core Practice Test Questions and Exam Dumps Part9 Q161-180"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/snowpro-core-recertification-exam-dumps\"><b>Snowflake SnowPro Core Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 161<\/b><\/h3>\n<p><b>Which Snowflake feature allows users to recover or query historical versions of data within the configured retention period?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fail-safe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time Travel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowpipe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search Optimization Service<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowflake Time Travel allows users to access historical versions of data within the applicable retention period. It can be used to query data as it existed at an earlier point in time and, in supported scenarios, recover objects or data that were accidentally changed or deleted. Time Travel is different from Fail-safe, which is intended as a separate recovery mechanism after the Time Travel period. Snowpipe is designed for continuous data ingestion, while Search Optimization Service improves certain selective query patterns. Therefore, Time Travel is the appropriate feature for accessing historical data.<\/span><\/p>\n<h3><b>Question 162<\/b><\/h3>\n<p><b>Which Snowflake object is primarily used to provide a location for files before they are loaded into tables?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stream<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A stage provides a location where data files can be stored or referenced before loading them into Snowflake tables. Stages can be internal to Snowflake or can reference external cloud storage locations. Commands such as COPY INTO can use staged files as input for loading data. A warehouse provides compute resources, a role controls access, and a stream tracks changes to table data. Understanding stages is essential for Snowflake data-loading workflows because they provide the bridge between files and table-loading operations.<\/span><\/p>\n<h3><b>Question 163<\/b><\/h3>\n<p><b>Which command is commonly used to load data from staged files into a Snowflake table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COPY INTO<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LOAD TABLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">INSERT FILES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IMPORT DATA<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">COPY INTO is a primary Snowflake SQL command for loading data from staged files into tables. It can work with internal or external stages and can use file-format definitions or inline file-format options to interpret incoming data. COPY INTO supports various loading options that help control how files are processed and how errors are handled. LOAD TABLE, INSERT FILES, and IMPORT DATA are not the standard Snowflake commands for bulk-loading staged files. Therefore, COPY INTO is the correct choice for this data-loading operation.<\/span><\/p>\n<h3><b>Question 164<\/b><\/h3>\n<p><b>Which Snowflake feature can automatically suspend a virtual warehouse after it remains idle for a configured period?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto-resume<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time Travel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto-suspend<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fail-safe<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Auto-suspend allows a virtual warehouse to automatically stop running after it has remained inactive for a configured amount of time. This is an important cost-management feature because a suspended warehouse does not continue consuming compute credits simply because it was previously running. Auto-resume can complement auto-suspend by automatically starting the warehouse when a new workload requires it. Time Travel provides historical data access, while Fail-safe relates to recovery. Therefore, auto-suspend is specifically responsible for automatically stopping an idle warehouse.<\/span><\/p>\n<h3><b>Question 165<\/b><\/h3>\n<p><b>Which Snowflake security model is primarily based on assigning privileges to roles and then assigning roles to users?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Attribute-based encryption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role-based access control<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File-based authorization<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse-based authentication<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowflake primarily uses role-based access control, commonly called RBAC, to manage access to resources. Privileges can be granted to roles, and roles can then be assigned to users or incorporated into role hierarchies. This model makes access management easier because administrators can manage permissions at the role level rather than individually granting every privilege to every user. The other choices do not describe Snowflake&#8217;s primary authorization model. RBAC is therefore a fundamental concept for understanding how Snowflake controls access to databases, schemas, tables, views, warehouses, and other objects.<\/span><\/p>\n<h3><b>Question 166<\/b><\/h3>\n<p><b>Which Snowflake object is used to define the structure and format of files being loaded or unloaded?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource Monitor<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File format<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Snowflake file format object defines how data files should be interpreted when loading or unloading data. File formats can specify characteristics such as CSV delimiters, field enclosures, compression, and other relevant file properties. They can be created as reusable database objects or specified directly within commands when appropriate. Resource Monitors manage credit consumption, streams track table changes, and roles control permissions. File formats are therefore particularly important in data-loading and unloading workflows because they tell Snowflake how to interpret the structure of external files.<\/span><\/p>\n<h3><b>Question 167<\/b><\/h3>\n<p><b>Which Snowflake capability allows a new table to initially share the same underlying micro-partitions as an existing table without physically copying the data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Zero-copy cloning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowpipe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time Travel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Result caching<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Zero-copy cloning allows Snowflake objects such as tables to be cloned without immediately creating a separate physical copy of the underlying data. The clone initially references the same underlying micro-partitions as the source. As changes are made to either object, Snowflake uses its storage architecture to maintain the appropriate data versions. This approach can make development, testing, and temporary environments much faster and more storage-efficient than traditional full data copies. Snowpipe handles ingestion, Time Travel provides historical access, and result caching serves query results.<\/span><\/p>\n<h3><b>Question 168<\/b><\/h3>\n<p><b>Which Snowflake feature is designed to continuously load newly arrived files from a cloud storage location?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized View<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource Monitor<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowpipe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row Access Policy<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowpipe is designed for continuous or near-continuous ingestion of newly arrived files into Snowflake. Instead of requiring users to manually execute a bulk load whenever new files arrive, Snowpipe can automatically load data as files become available through supported notification mechanisms. This makes it useful for event-driven ingestion pipelines. Materialized Views are designed for query performance, Resource Monitors manage credit usage, and Row Access Policies control data visibility. Therefore, Snowpipe is the Snowflake feature most directly associated with continuously ingesting newly arrived files.<\/span><\/p>\n<h3><b>Question 169<\/b><\/h3>\n<p><b>Which Snowflake cache can return a previously computed query result when the same eligible query is executed again?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Result cache<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Metadata cache<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stage cache<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role cache<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowflake can use a result cache to return a previously computed result for an eligible query rather than executing the complete query again. This can significantly improve response time and reduce unnecessary compute usage when the cached result remains valid and the query meets the conditions for reuse. Result caching is different from warehouse-level caching, which involves data accessed by a running warehouse. Metadata is also used for query optimization, but it is not the same as storing the complete query result. Therefore, result cache is the correct answer.<\/span><\/p>\n<h3><b>Question 170<\/b><\/h3>\n<p><b>Which Snowflake object is used to monitor and control credit consumption for warehouses and other supported resources?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource Monitor<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File Format<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Resource Monitor helps administrators monitor Snowflake credit usage and can be configured with thresholds and actions. Organizations can use resource monitors to receive notifications or take supported actions when consumption approaches configured limits. This makes them useful for cost governance and preventing unexpected compute consumption. Stages are associated with files, streams track data changes, and file formats define how files are interpreted. Resource Monitors therefore provide a mechanism for managing and monitoring credit consumption rather than storing data or processing files.<\/span><\/p>\n<h3><b>Question 171<\/b><\/h3>\n<p><b>Which Snowflake data type is most appropriate for storing true\/false values?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BOOLEAN<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARRAY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TIMESTAMP<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">BOOLEAN is the Snowflake data type intended to represent logical true or false values. It is useful for fields such as active status, approval status, availability indicators, or other binary logical conditions. DATE represents calendar dates, ARRAY represents ordered collections of values, and TIMESTAMP types represent date-and-time information. Choosing appropriate data types helps maintain correct data representation and can improve query clarity and data processing. Therefore, when a column logically contains true or false values, BOOLEAN is the appropriate Snowflake data type.<\/span><\/p>\n<h3><b>Question 172<\/b><\/h3>\n<p><b>Which Snowflake capability allows data to be shared with another Snowflake account without requiring the provider to create a traditional copy of the shared data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Zero-copy Data Sharing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local file transfer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query caching<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowflake Secure Data Sharing allows providers to share selected database objects with consumers without requiring traditional duplication of the underlying shared data. The provider controls what is made available, while the consumer can access the shared data according to the configured sharing arrangement. This architecture reduces the need to create and maintain separate copies for each consumer and can support efficient collaboration across organizations or Snowflake accounts. Warehouse replication and query caching serve different purposes, while local file transfer is not the primary mechanism for Secure Data Sharing.<\/span><\/p>\n<h3><b>Question 173<\/b><\/h3>\n<p><b>Which Snowflake command is used to change the size of an existing virtual warehouse?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALTER WAREHOUSE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MODIFY COMPUTE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CHANGE WAREHOUSE SIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UPDATE WAREHOUSE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">ALTER WAREHOUSE is used to modify properties of an existing Snowflake virtual warehouse, including its size and other supported configuration settings. Changing warehouse size can increase or decrease available compute capacity and may affect both performance and credit consumption. Organizations should therefore consider workload requirements and cost implications when resizing warehouses. MODIFY COMPUTE, CHANGE WAREHOUSE SIZE, and UPDATE WAREHOUSE are not the standard Snowflake SQL syntax for modifying warehouse configuration. ALTER WAREHOUSE is the appropriate command for changing an existing warehouse&#8217;s properties.<\/span><\/p>\n<h3><b>Question 174<\/b><\/h3>\n<p><b>Which Snowflake object provides a way to expose a query result as a logical table without storing a separate copy of the underlying data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">View<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource Monitor<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A view is a logical representation based on a SQL query. It generally does not store a separate physical copy of the underlying table data like a materialized view does. When users query a standard view, Snowflake evaluates the underlying query as needed. Views are useful for simplifying complex queries, presenting selected columns, and supporting controlled data access. Stages store or reference files, warehouses provide compute resources, and Resource Monitors manage credit consumption. Therefore, a standard view is the appropriate object for exposing query results as a logical table-like interface.<\/span><\/p>\n<h3><b>Question 175<\/b><\/h3>\n<p><b>Which Snowflake feature is specifically designed to provide recovery access after the Time Travel retention period has ended?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fail-safe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowpipe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search Optimization Service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto-suspend<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Fail-safe is a separate Snowflake recovery mechanism that follows the Time Travel period. It is intended primarily for disaster recovery and is not designed as a general-purpose historical data-access feature. Time Travel should normally be used when users need to query or restore historical data within the configured retention period. Fail-safe provides additional recovery protection after that period under Snowflake&#8217;s applicable service behavior. Snowpipe supports data ingestion, Search Optimization Service improves certain search workloads, and auto-suspend controls warehouse activity. Therefore, Fail-safe is the correct answer.<\/span><\/p>\n<h3><b>Question 176<\/b><\/h3>\n<p><b>Which Snowflake feature can automatically cluster table data over time when a clustering key has been defined?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search Optimization Service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Automatic Clustering<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowpipe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time Travel<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Automatic Clustering can maintain the clustering of eligible tables when a clustering key has been defined. As data changes over time, the physical organization of micro-partitions may become less aligned with the desired clustering strategy. Automatic Clustering can perform background maintenance to improve organization according to the defined clustering key. Search Optimization Service addresses a different class of selective search workloads, Snowpipe handles continuous file ingestion, and Time Travel provides historical access. Automatic Clustering is therefore the feature associated with ongoing maintenance of clustering for appropriately configured tables.<\/span><\/p>\n<h3><b>Question 177<\/b><\/h3>\n<p><b>Which statement best describes Snowflake&#8217;s separation of storage and compute?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Each table must have its own warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage and compute are independent resources<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouses permanently store all table data<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Compute resources cannot be resized<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A fundamental characteristic of Snowflake architecture is the separation of storage and compute. Data is stored independently from virtual warehouses, while warehouses provide compute resources for executing workloads. This allows organizations to use multiple warehouses against the same stored data and independently scale compute resources according to workload requirements. Warehouses do not permanently contain the table data, and they can be resized or configured based on operational needs. This separation is one of the key architectural concepts that enables Snowflake&#8217;s flexible workload management and resource isolation.<\/span><\/p>\n<h3><b>Question 178<\/b><\/h3>\n<p><b>Which Snowflake function can convert a JSON-formatted string into a semi-structured value?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PARSE_JSON<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FLATTEN<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET_PATH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARRAY_CONSTRUCT<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">PARSE_JSON converts a string containing valid JSON into a Snowflake semi-structured value that can be stored and queried, commonly through the VARIANT data type. After parsing, users can access nested fields and arrays using Snowflake&#8217;s semi-structured data functionality. FLATTEN is used to expand nested arrays or objects into rows, while GET_PATH can retrieve values from structured paths and ARRAY_CONSTRUCT creates arrays. Therefore, when the requirement is to interpret a JSON string as semi-structured data, PARSE_JSON is the appropriate function.<\/span><\/p>\n<h3><b>Question 179<\/b><\/h3>\n<p><b>Which Snowflake privilege is generally required to allow a role to use a database?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SELECT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">USAGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">INSERT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UPDATE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The USAGE privilege is generally required on a database for a role to access objects within that database, subject to the additional privileges required on the relevant schema and object. Snowflake access control often involves privileges at multiple levels. For example, a role may need USAGE on the database and schema along with an object-specific privilege such as SELECT on a table. SELECT controls querying of applicable objects, while INSERT and UPDATE control data modification. Therefore, USAGE is the appropriate privilege for making the database available for access.<\/span><\/p>\n<h3><b>Question 180<\/b><\/h3>\n<p><b>Which Snowflake feature is most appropriate for restricting access to specific rows based on a user&#8217;s role or other conditions?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized View<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File Format<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row Access Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource Monitor<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Row Access Policy provides fine-grained control over which rows users can access. The policy can evaluate conditions involving roles or other relevant attributes and determine whether particular rows should be visible to the querying user. This allows multiple users to query the same underlying table while receiving different results according to their authorization context. Materialized Views are primarily performance-oriented, File Formats describe file structures, and Resource Monitors manage credit usage. Therefore, Row Access Policy is the correct feature when the requirement is to restrict visibility at the row level.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Snowflake SnowPro Core Exam Dumps and Practice Test Dumps. &nbsp; Question 161 Which Snowflake feature allows users to recover or query historical versions of data within the configured retention period? Fail-safe Time Travel Snowpipe Search Optimization Service Correct Answer: 2 Explanation: Snowflake Time Travel allows users to access historical versions of data within [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13479"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=13479"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13479\/revisions"}],"predecessor-version":[{"id":13509,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13479\/revisions\/13509"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=13479"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=13479"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=13479"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}