{"id":24222,"date":"2026-09-29T06:08:28","date_gmt":"2026-09-29T06:08:28","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=24222"},"modified":"2026-09-29T06:08:28","modified_gmt":"2026-09-29T06:08:28","slug":"snowflake-snowpro-core-cof-c03-practice-test-questions-and-exam-dumps-part8-q141-160","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-core-cof-c03-practice-test-questions-and-exam-dumps-part8-q141-160\/","title":{"rendered":"Snowflake SnowPro Core COF-C03 Practice Test Questions and Exam Dumps Part8 Q141-160"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/snowpro-core-cof-c03-exam-dumps\"><b>Snowflake SnowPro Core COF-C03 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 141<\/b><\/h3>\n<p><b>Which Snowflake object provides a named reference to a location where data files are stored before loading?<\/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;\">Stream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Task<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pipe<\/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;\">A stage is a Snowflake object that identifies a location where data files can be stored or accessed for loading and unloading operations. Internal stages are managed within Snowflake, while external stages reference locations in supported cloud storage services. Stages are commonly used with commands such as COPY INTO when moving data between files and Snowflake tables. A stage does not itself track changed rows like a stream or schedule SQL like a task. Understanding stages is fundamental to Snowflake data-loading architecture because they provide the connection between file-based data and table operations.<\/span><\/p>\n<h3><b>Question 142<\/b><\/h3>\n<p><b>Which type of stage stores files within Snowflake-managed cloud storage?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External stage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Internal stage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">User-defined view<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External table<\/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;\">An internal stage stores files in Snowflake-managed cloud storage. Internal stages can be associated with a user, table, or created explicitly as named stages. They are useful when data files need to be staged inside Snowflake before being loaded into tables or when query results need to be unloaded into staged files. External stages work differently because they reference storage locations outside Snowflake. Choosing between internal and external staging depends on where the source files reside and how the organization wants to manage data movement and storage.<\/span><\/p>\n<h3><b>Question 143<\/b><\/h3>\n<p><b>Which command uploads local files to an internal Snowflake stage?<\/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;\">PUT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LIST<\/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 PUT command is used to upload local files from a client environment to an internal Snowflake stage. It is commonly used before loading those staged files into a Snowflake table with COPY INTO. PUT therefore represents the movement of files from a local file system into Snowflake-managed staging storage. GET performs the opposite direction for supported operations by downloading files from an internal stage to a local environment. LIST displays staged files. Understanding these commands helps distinguish file transfer operations from the actual table-loading process.<\/span><\/p>\n<h3><b>Question 144<\/b><\/h3>\n<p><b>Which command downloads files from an internal Snowflake stage to a local file system?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PUT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COPY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FETCH<\/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;\">The GET command is used to download files from an internal Snowflake stage to a local file system. It is essentially the reverse direction of PUT, which uploads local files to an internal stage. GET can be useful when users need to retrieve staged files for inspection, processing, or other local operations. COPY INTO serves a different purpose by loading staged data into tables or unloading query results to supported locations. Distinguishing GET from COPY and PUT is important when working with Snowflake&#8217;s file staging and data movement capabilities.<\/span><\/p>\n<h3><b>Question 145<\/b><\/h3>\n<p><b>Which object can define reusable file-format settings such as type, delimiter, and compression?<\/b><\/p>\n<ol>\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;\">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: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A file format object stores reusable settings that describe how Snowflake should interpret data files. Depending on the file type, settings can include delimiters, compression, header handling, quotation characters, null representations, and other file-specific properties. Creating a named file format can simplify repeated loading operations because the same configuration can be referenced by multiple COPY commands or stages. File formats do not store the actual data files. Instead, they provide the rules Snowflake uses to parse or generate files during loading and unloading operations.<\/span><\/p>\n<h3><b>Question 146<\/b><\/h3>\n<p><b>Which Snowflake feature can automatically detect and load new files arriving in a stage?<\/b><\/p>\n<ol>\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<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized view<\/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;\">Snowpipe is designed to continuously load newly arriving files into Snowflake tables. It can use supported cloud-storage event notifications to detect new files and initiate loading without requiring users to repeatedly execute traditional batch-loading commands. Snowpipe is particularly useful when data arrives incrementally throughout the day and should become available for analysis shortly after arrival. It is different from Time Travel, which provides historical data access, and from Search Optimization Service, which improves selective query performance. Snowpipe therefore addresses continuous file-based ingestion rather than query optimization or data recovery.<\/span><\/p>\n<h3><b>Question 147<\/b><\/h3>\n<p><b>What is the primary purpose of a pipe in a Snowpipe data-loading workflow?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define the Snowpipe loading instructions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To store query results permanently<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To replace a virtual warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To provide user authentication<\/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;\">A pipe contains the COPY INTO statement used by Snowpipe to load data from a stage into a Snowflake table. It defines how incoming files should be processed as part of the automated ingestion workflow. A pipe does not replace a warehouse, store permanent query results, or authenticate users. Instead, it represents the loading instructions that Snowpipe uses when processing newly arrived files. Pipes are especially useful when organizations want a repeatable and automated ingestion process rather than manually executing COPY commands whenever new files become available.<\/span><\/p>\n<h3><b>Question 148<\/b><\/h3>\n<p><b>Which Snowflake capability can reduce the need to scan large amounts of table data for highly selective searches?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query tag<\/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;\">Resource monitor<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Result cache<\/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;\">Search Optimization Service is designed to improve query performance for certain highly selective access patterns. It maintains additional search access paths that can help Snowflake locate relevant rows more efficiently instead of scanning unnecessary portions of the underlying data. This can be useful for workloads involving selective equality predicates or other supported search patterns, particularly when queries frequently look for a small subset of records in a large table. Search Optimization Service is different from result caching because it improves data access for qualifying queries rather than simply reusing a previously generated result.<\/span><\/p>\n<h3><b>Question 149<\/b><\/h3>\n<p><b>Which Snowflake feature helps organize table data based on selected columns to improve pruning for suitable queries?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data sharing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Clustering<\/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;\">Snowpipe<\/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;\">Clustering helps organize table data according to selected clustering keys or natural ordering patterns. Better organization can improve micro-partition pruning for queries that filter on relevant columns, potentially reducing the amount of data Snowflake needs to scan. Clustering is particularly useful for large tables where query patterns repeatedly filter or range over particular columns. It does not itself create a separate copy of the table or replace a warehouse. Its purpose is related to physical data organization and query efficiency, while features such as Snowpipe and data sharing address different Snowflake capabilities.<\/span><\/p>\n<h3><b>Question 150<\/b><\/h3>\n<p><b>Which Snowflake capability allows users to share selected data with another Snowflake account without copying the underlying table data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Secure Data Sharing<\/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;\">Zero-copy cloning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search Optimization<\/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;\">Secure Data Sharing allows a provider to share selected Snowflake data with another Snowflake account without creating a traditional physical copy of the underlying shared table data. The provider controls which objects are included in the share, while the consumer can access the shared information according to the permissions and sharing arrangement. This capability is useful for collaboration between organizations, departments, partners, and other Snowflake accounts. Secure Data Sharing is different from zero-copy cloning because sharing is intended for controlled data access, whereas cloning creates an independent Snowflake object environment.<\/span><\/p>\n<h3><b>Question 151<\/b><\/h3>\n<p><b>Which object can be created from a Snowflake share so that a consumer can access shared data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Consumer database<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">User stage<\/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: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A consumer can create a database from a provider&#8217;s share to access the objects made available through Secure Data Sharing. The shared database provides access to the data according to the privileges and objects included by the provider. This approach allows consumers to query shared information without requiring the provider to send traditional copies of the underlying data. The consumer does not directly own or modify the provider&#8217;s source tables through the shared database. This separation helps maintain provider control while still enabling secure analytical access across Snowflake accounts.<\/span><\/p>\n<h3><b>Question 152<\/b><\/h3>\n<p><b>Which Snowflake feature is specifically designed to control which rows a user can see based on a policy?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Masking policy<\/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;\">File format<\/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 row access policy controls whether individual rows are visible to a user or role based on defined policy logic. It can be used to implement row-level security requirements, such as allowing regional managers to see only records associated with their assigned regions. The policy evaluates conditions and determines whether a row should be returned. A masking policy serves a different purpose by controlling how sensitive column values are displayed. Row access policies are therefore appropriate when access must be restricted at the row level rather than simply changing the representation of a column value.<\/span><\/p>\n<h3><b>Question 153<\/b><\/h3>\n<p><b>Which Snowflake feature can dynamically transform sensitive column values based on the role querying the data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Masking policy<\/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<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pipe<\/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;\">A masking policy can dynamically control how sensitive column values are presented based on conditions such as the querying role. For example, authorized users may see an original value while other users see a partially masked or otherwise transformed representation. The underlying stored value remains protected while the returned representation changes according to policy rules. Masking policies are commonly used for sensitive information such as personal identifiers or confidential business values. They differ from row access policies, which determine whether an entire row should be visible rather than how a column value should appear.<\/span><\/p>\n<h3><b>Question 154<\/b><\/h3>\n<p><b>Which Snowflake object is used to automate the execution of SQL statements according to a schedule or dependency?<\/b><\/p>\n<ol>\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;\">Task<\/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;\">Share<\/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 task is a Snowflake object used to automate SQL execution. Tasks can run according to a schedule or can be triggered through task dependencies in a workflow. They are useful for automating transformations, maintenance operations, and recurring data-processing activities. A stream can provide change-tracking information to support incremental processing, but it does not itself schedule SQL execution. A task can be combined with a stream so that changed data is processed automatically. This combination is useful for building event-driven or scheduled data pipelines inside Snowflake.<\/span><\/p>\n<h3><b>Question 155<\/b><\/h3>\n<p><b>Which Snowflake object records metadata about changes made to table data for downstream processing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Task<\/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;\">Stage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pipe<\/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 stream records information about changes to supported source objects, allowing downstream processes to identify newly inserted, updated, or deleted rows. Streams are useful for change data capture and incremental processing because downstream logic does not need to repeatedly compare the entire source table to determine what changed. A task can then consume stream information and execute processing logic on a schedule or through dependencies. The stream itself is not a storage stage or an automated SQL scheduler. It serves primarily as a mechanism for tracking data changes.<\/span><\/p>\n<h3><b>Question 156<\/b><\/h3>\n<p><b>Which Snowflake command can display the definition and properties of a named stage?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DESCRIBE STAGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SHOW STAGE DEFINITION<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VIEW STAGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CHECK STAGE<\/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;\">DESCRIBE STAGE can be used to display information about a stage, including its configuration and relevant properties. This can help administrators inspect how a named stage has been defined and troubleshoot data-loading configurations. SHOW commands can also provide lists of objects, but DESCRIBE is intended to provide descriptive information about a particular object. Examining stage properties is especially useful when verifying external locations, file-format references, and other configuration details before performing loading or unloading operations.<\/span><\/p>\n<h3><b>Question 157<\/b><\/h3>\n<p><b>Which command can list files currently available in a Snowflake stage?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SHOW FILES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LIST<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DESCRIBE FILES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SEARCH FILES<\/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 LIST command is used to display files available in a Snowflake stage. It can help users verify whether expected files have been uploaded or whether files are present in an external or internal staging location. This is particularly useful before running a COPY INTO operation because users can confirm the staged file names and paths. LIST does not load data into a table; it simply provides visibility into staged files. Separating file inspection from data loading helps users troubleshoot missing files and verify staging operations before beginning ingestion.<\/span><\/p>\n<h3><b>Question 158<\/b><\/h3>\n<p><b>Which Snowflake command can display the privileges granted to a role?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SHOW GRANTS TO ROLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LIST ROLE PRIVILEGES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DESCRIBE ROLE ACCESS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CHECK ROLE GRANTS<\/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;\">SHOW GRANTS TO ROLE is used to display privileges granted to a specified role. It can help administrators understand which databases, schemas, tables, warehouses, and other supported objects a role can access. Reviewing grants is important when troubleshooting authorization problems or auditing role-based access. The command does not change privileges; it only reports existing grants. Administrators can use this information alongside role hierarchy and object ownership details to understand the effective access available to users. This supports more accurate access management and least-privilege administration.<\/span><\/p>\n<h3><b>Question 159<\/b><\/h3>\n<p><b>Which Snowflake concept allows a role to inherit privileges from another role in a hierarchy?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data sharing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role hierarchy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File staging<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query acceleration<\/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 role hierarchy allows one role to inherit the privileges granted to another role. This enables organizations to structure access according to job responsibilities and organizational relationships. For example, a higher-level role can inherit privileges from a lower-level functional role rather than requiring every privilege to be granted separately. Role hierarchies can simplify administration when designed carefully. They are part of Snowflake&#8217;s role-based access-control model and should be managed according to least-privilege principles. Understanding inheritance is important because a user&#8217;s effective access may come from multiple roles in the hierarchy.<\/span><\/p>\n<h3><b>Question 160<\/b><\/h3>\n<p><b>Which Snowflake feature provides detailed information about how an individual SQL query was executed?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query History<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query Profile<\/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;\">Information Schema<\/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;\">Query Profile provides detailed execution information for an individual query, including its execution steps and operators. It can help users understand where processing time or resources are being consumed and identify potential performance issues. Query History provides information about executed queries and their status, but Query Profile provides deeper execution-plan details for a specific query. Resource Monitor focuses on credit usage and warehouse-related resource controls, while Information Schema provides metadata about database objects. Query Profile is therefore particularly useful when investigating the execution behavior of a specific SQL statement.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Snowflake SnowPro Core COF-C03 Exam Dumps and Practice Test Dumps. &nbsp; Question 141 Which Snowflake object provides a named reference to a location where data files are stored before loading? Stage Stream Task Pipe Correct Answer: 1 Explanation A stage is a Snowflake object that identifies a location where data files can be [&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\/24222"}],"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=24222"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/24222\/revisions"}],"predecessor-version":[{"id":24223,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/24222\/revisions\/24223"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=24222"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=24222"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=24222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}