{"id":24226,"date":"2026-09-29T06:09:01","date_gmt":"2026-09-29T06:09:01","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=24226"},"modified":"2026-09-29T06:09:01","modified_gmt":"2026-09-29T06:09:01","slug":"snowflake-snowpro-core-cof-c03-practice-test-questions-and-exam-dumps-part10-q181-200","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-core-cof-c03-practice-test-questions-and-exam-dumps-part10-q181-200\/","title":{"rendered":"Snowflake SnowPro Core COF-C03 Practice Test Questions and Exam Dumps Part10 Q181-200"},"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 181<\/b><\/h3>\n<p><b>Which Snowflake warehouse property specifies the minimum number of clusters available in a multi-cluster warehouse?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MIN_CLUSTER_COUNT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAX_CLUSTER_COUNT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WAREHOUSE_SIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SCALING_POLICY<\/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;\">MIN_CLUSTER_COUNT specifies the minimum number of clusters that a multi-cluster virtual warehouse maintains when it is running. A multi-cluster warehouse can scale within the configured minimum and maximum cluster boundaries according to workload demand and its scaling policy. MIN_CLUSTER_COUNT therefore establishes the lower capacity boundary, while MAX_CLUSTER_COUNT establishes the upper boundary. WAREHOUSE_SIZE determines the size of each individual cluster rather than the number of clusters. Understanding these settings is important when configuring compute resources for workloads that experience changing concurrency requirements.<\/span><\/p>\n<h3><b>Question 182<\/b><\/h3>\n<p><b>Which setting controls how a multi-cluster warehouse adds or removes clusters in response to workload demand?<\/b><\/p>\n<ol>\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;\">SCALING_POLICY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WAREHOUSE_SIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">STATEMENT_TIMEOUT_IN_SECONDS<\/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;\">SCALING_POLICY controls how Snowflake manages the addition and removal of clusters in a multi-cluster warehouse. The setting helps determine whether Snowflake prioritizes faster response to queued work or attempts to conserve credits while adjusting cluster capacity. It therefore affects the behavior of multi-cluster scaling rather than the size of each cluster. WAREHOUSE_SIZE controls the compute capacity of an individual cluster, while AUTO_SUSPEND concerns warehouse inactivity. Selecting an appropriate scaling policy requires considering workload concurrency, performance expectations, and the organization&#8217;s approach to compute consumption.<\/span><\/p>\n<h3><b>Question 183<\/b><\/h3>\n<p><b>Which warehouse property determines the compute size of each cluster in a virtual warehouse?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAX_CLUSTER_COUNT<\/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;\">WAREHOUSE_SIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MIN_CLUSTER_COUNT<\/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;\">WAREHOUSE_SIZE determines the size of the compute resources allocated to each cluster of a virtual warehouse. Snowflake provides different warehouse sizes, with larger sizes generally providing more compute resources and potentially greater processing capacity. This setting is separate from cluster count. A multi-cluster warehouse can have several clusters, but each cluster uses the configured warehouse size. MAX_CLUSTER_COUNT and MIN_CLUSTER_COUNT define the range of cluster counts, while AUTO_SUSPEND controls inactivity-based suspension. Understanding the distinction helps administrators scale individual cluster capacity separately from concurrency capacity.<\/span><\/p>\n<h3><b>Question 184<\/b><\/h3>\n<p><b>Which parameter can limit how long a SQL statement is allowed to run before Snowflake terminates it?<\/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;\">STATEMENT_TIMEOUT_IN_SECONDS<\/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;\">MAX_CLUSTER_COUNT<\/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;\">STATEMENT_TIMEOUT_IN_SECONDS specifies the maximum amount of time a statement can execute before Snowflake terminates it due to exceeding the configured limit. This setting can help organizations prevent unexpectedly long-running queries from consuming compute resources indefinitely. It is different from AUTO_SUSPEND, which controls warehouse suspension after inactivity. QUERY_TAG is used to label queries for identification and monitoring, while MAX_CLUSTER_COUNT controls the upper number of clusters in a multi-cluster warehouse. Timeout settings should be selected carefully because legitimate complex queries may require longer execution times.<\/span><\/p>\n<h3><b>Question 185<\/b><\/h3>\n<p><b>Which Snowflake feature allows administrators to attach descriptive metadata to SQL statements for tracking and analysis?<\/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;\">Stream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pipe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">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;\">A query tag allows users or administrators to associate descriptive text with SQL statements. Tags can help identify applications, teams, workloads, business processes, or other categories when reviewing query activity. This information can be particularly useful when analyzing Query History or investigating resource consumption by workload. A query tag does not alter the query&#8217;s business logic or provide authorization. Streams track data changes, pipes support Snowpipe loading definitions, and stages identify file locations. Query tagging is therefore primarily a monitoring, organization, and workload-identification capability.<\/span><\/p>\n<h3><b>Question 186<\/b><\/h3>\n<p><b>Which Snowflake object is designed to store reusable procedural logic that can be invoked by users or applications?<\/b><\/p>\n<ol>\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;\">Stored procedure<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External table<\/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 stored procedure encapsulates reusable logic that can be executed when needed. Snowflake stored procedures can contain SQL and, depending on the supported language and implementation, procedural logic for performing multiple operations. They are useful for automating complex workflows, centralizing reusable business logic, and reducing repeated SQL across applications or administrative processes. A view provides a reusable query definition, while an external table provides SQL access to externally stored data. Resource monitors are administrative controls for monitoring and managing credit usage rather than procedural programming objects.<\/span><\/p>\n<h3><b>Question 187<\/b><\/h3>\n<p><b>Which Snowflake capability can automatically execute a task after another task in a defined task graph completes successfully?<\/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 dependency<\/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;\">Query tag<\/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;\">Task dependencies allow Snowflake tasks to be organized into workflows where one task can depend on another. This enables task graphs in which downstream tasks execute according to defined relationships and scheduling conditions. Such workflows can support multi-step data transformations and processing pipelines. A stream can provide information about data changes but does not itself establish task execution order. File formats describe file interpretation, while query tags identify SQL statements. Task dependencies therefore provide the mechanism for coordinating multiple automated SQL operations within a Snowflake workflow.<\/span><\/p>\n<h3><b>Question 188<\/b><\/h3>\n<p><b>Which statement about a Snowflake stream is correct?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It permanently stores a second copy of every changed row<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It schedules SQL execution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It records change information that can be consumed by downstream processing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It replaces a virtual warehouse<\/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 Snowflake stream records change information for a supported source object so downstream processing can identify changes since the relevant stream position. It is commonly used for change data capture and incremental processing. A stream does not function as a permanent duplicate table containing an independent copy of all changed records. It also does not schedule SQL execution; that responsibility belongs to tasks. Streams are especially useful when combined with tasks, allowing organizations to process only newly changed information rather than repeatedly scanning an entire source dataset.<\/span><\/p>\n<h3><b>Question 189<\/b><\/h3>\n<p><b>Which Snowflake capability allows a table to be queried through a predefined SQL statement without storing a separate copy of its results?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Standard view<\/span><\/li>\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;\">External 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: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A standard view stores a SQL query definition that represents data from one or more underlying objects. When users query the view, Snowflake evaluates the underlying query rather than treating the view as an independent physical copy of the source data. Standard views are useful for simplifying complex SQL, exposing selected columns, and providing controlled logical representations of data. A materialized view is different because Snowflake maintains stored results for supported query patterns. External stages identify file locations, while streams track changes. Therefore, a standard view is the appropriate choice for a reusable virtual query representation.<\/span><\/p>\n<h3><b>Question 190<\/b><\/h3>\n<p><b>Which Snowflake object is specifically designed to maintain precomputed results for supported queries?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Secure view<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Standard view<\/span><\/li>\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;\">External table<\/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 materialized view maintains stored results derived from its defining query, allowing Snowflake to use those results for eligible workloads. This can improve performance when queries repeatedly access data that benefits from precomputation. Snowflake manages the maintenance of the materialized data as the underlying information changes, subject to the feature&#8217;s supported behavior. A standard view does not maintain results in the same way, while a secure view primarily addresses protection of the view definition. External tables provide access to externally stored data rather than maintaining precomputed relational results.<\/span><\/p>\n<h3><b>Question 191<\/b><\/h3>\n<p><b>Which Snowflake feature allows sensitive values to be transformed according to the role or context of the querying user?<\/b><\/p>\n<ol>\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;\">Masking policy<\/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;\">Search optimization<\/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 masking policy can control how sensitive column values are presented to users based on conditions defined by the policy. For example, a policy may allow an authorized role to view a complete value while returning a masked representation to other roles. This provides dynamic protection without requiring separate physical copies of the data for different users. Row access policies address a different requirement by controlling which rows are visible. Resource monitors manage credit usage, while search optimization supports certain selective query patterns. Masking policies are therefore central to column-level data protection.<\/span><\/p>\n<h3><b>Question 192<\/b><\/h3>\n<p><b>Which policy is appropriate when users from different regions should see only rows belonging to their assigned region?<\/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;\">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 is appropriate when visibility must be restricted according to individual rows. For example, a policy can evaluate a user&#8217;s role or another security attribute and allow access only to records associated with an authorized region. The data remains stored in the same table, but Snowflake applies the policy when determining which rows can be returned. A masking policy instead controls the representation of values within columns. Row access policies are therefore useful for implementing row-level security requirements across departments, regions, customers, or other logical groups.<\/span><\/p>\n<h3><b>Question 193<\/b><\/h3>\n<p><b>Which Snowflake capability can help enforce column-level protection without creating separate copies of sensitive data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic data masking<\/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;\">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: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Dynamic data masking can protect sensitive column values by applying a masking policy when data is accessed. Depending on the policy conditions, users may see the original value, a partially obscured value, or another transformed representation. This allows different users to access the same underlying table while receiving different representations of protected information. Zero-copy cloning addresses efficient object duplication, Snowpipe supports continuous file ingestion, and Time Travel provides historical data access. Dynamic masking is therefore the feature most directly associated with controlling how sensitive column values are displayed.<\/span><\/p>\n<h3><b>Question 194<\/b><\/h3>\n<p><b>Which Snowflake feature provides historical access to data before a specified point in time?<\/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;\">Resource Monitor<\/span><\/li>\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;\">Snowpipe<\/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;\">Time Travel allows authorized users to access historical versions of data within the applicable retention period. Queries can reference an earlier point in time to investigate changes, compare historical states, or support recovery operations. This capability is useful for situations such as accidental data modifications, dropped objects, and historical analysis. Time Travel is not intended to replace backup strategies for every scenario, and its availability depends on the retention configuration and object type. It should also be distinguished from Fail-safe, which serves a separate disaster-recovery purpose.<\/span><\/p>\n<h3><b>Question 195<\/b><\/h3>\n<p><b>Which Snowflake recovery mechanism is intended primarily for disaster recovery after the Time Travel period?<\/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;\">Fail-safe<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search Optimization<\/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: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Fail-safe is designed primarily as a disaster-recovery mechanism after the applicable Time Travel period has ended for eligible permanent data. It is not intended as a normal user-accessible historical querying feature. Fail-safe recovery is handled by Snowflake rather than being a general-purpose interface for users to browse historical versions of data. This distinction is important because Time Travel is the normal mechanism for user-controlled historical access and recovery during its retention period. Understanding both features helps administrators establish realistic expectations for data protection and recovery procedures.<\/span><\/p>\n<h3><b>Question 196<\/b><\/h3>\n<p><b>Which Snowflake feature allows a database object to be copied efficiently without immediately duplicating all underlying storage?<\/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;\">Data masking<\/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;\">Query acceleration<\/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 creates supported Snowflake objects efficiently by initially sharing underlying storage with the source object. This means the clone can be created quickly without immediately producing a complete physical duplicate of all unchanged data. As the clone is modified, additional storage may be used for data that differs from the source. Zero-copy cloning is useful for development environments, testing, experimentation, and other situations where an isolated copy of a database, schema, or table is needed. It differs from traditional data copying because unchanged data does not need to be duplicated immediately.<\/span><\/p>\n<h3><b>Question 197<\/b><\/h3>\n<p><b>Which Snowflake capability is most directly associated with querying files that remain in an external cloud storage location?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stored procedure<\/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;\">An external table provides a table-like SQL interface to data files that remain in an external cloud storage location. Instead of first loading the files into Snowflake-managed table storage, users can query metadata and values associated with supported external files through the external table. This approach is useful for data lake architectures and scenarios where data should remain in object storage. External tables commonly work with external stages that identify the storage location. Temporary tables and stored procedures address different requirements, while resource monitors manage credit-related controls.<\/span><\/p>\n<h3><b>Question 198<\/b><\/h3>\n<p><b>Which Snowflake loading option can control how COPY INTO responds when individual files contain errors?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ON_ERROR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SKIP_HEADER<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FIELD_DELIMITER<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RECORD_DELIMITER<\/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;\">The ON_ERROR option controls how a COPY INTO loading operation handles errors encountered while processing staged files. Depending on the selected behavior, Snowflake can stop processing, continue with certain files or rows, or apply another supported error-handling strategy. This option is important when designing reliable ingestion workflows because malformed or unexpected records can otherwise interrupt a load. SKIP_HEADER controls header rows, FIELD_DELIMITER identifies field boundaries, and RECORD_DELIMITER identifies record boundaries. ON_ERROR therefore addresses error-handling behavior rather than the physical interpretation of file fields.<\/span><\/p>\n<h3><b>Question 199<\/b><\/h3>\n<p><b>Which file format option specifies that the first row of a delimited file should be skipped during loading?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NULL_IF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SKIP_HEADER<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FIELD_OPTIONALLY_ENCLOSED_BY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RECORD_DELIMITER<\/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;\">SKIP_HEADER specifies how many initial rows in a delimited data file should be skipped during loading. It is commonly used when the first row contains column headings rather than actual data records. For example, a CSV file with a single header row can use an appropriate SKIP_HEADER setting so the header is not inserted into the target table as data. NULL_IF handles values interpreted as NULL, FIELD_OPTIONALLY_ENCLOSED_BY controls optional field enclosure characters, and RECORD_DELIMITER identifies record boundaries. Therefore, SKIP_HEADER is specifically related to leading rows.<\/span><\/p>\n<h3><b>Question 200<\/b><\/h3>\n<p><b>Which Snowflake command can display information about tables available in the current database or schema context?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SHOW TABLES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LIST TABLES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DESCRIBE DATABASE TABLES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DISPLAY TABLES<\/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 TABLES can display information about tables visible within the relevant Snowflake context. It is useful for discovering existing tables and reviewing basic metadata such as names, schemas, and other object information. DESCRIBE TABLE serves a different purpose by providing details about a specific table&#8217;s structure, such as its columns and data types. LIST is generally associated with files in stages rather than database tables. SHOW TABLES is therefore an appropriate administrative and discovery command when users need to identify tables available in their Snowflake environment.<\/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 181 Which Snowflake warehouse property specifies the minimum number of clusters available in a multi-cluster warehouse? MIN_CLUSTER_COUNT MAX_CLUSTER_COUNT WAREHOUSE_SIZE SCALING_POLICY Correct Answer: 1 Explanation MIN_CLUSTER_COUNT specifies the minimum number of clusters that a multi-cluster virtual warehouse maintains when it is running. [&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\/24226"}],"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=24226"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/24226\/revisions"}],"predecessor-version":[{"id":24227,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/24226\/revisions\/24227"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=24226"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=24226"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=24226"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}