{"id":21914,"date":"2026-09-25T10:04:26","date_gmt":"2026-09-25T10:04:26","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21914"},"modified":"2026-09-25T10:04:26","modified_gmt":"2026-09-25T10:04:26","slug":"snowflake-snowpro-advanced-data-engineer-practice-test-questions-and-exam-dumps-part6-q101-120","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-advanced-data-engineer-practice-test-questions-and-exam-dumps-part6-q101-120\/","title":{"rendered":"Snowflake SnowPro Advanced Data Engineer Practice Test Questions and Exam Dumps Part6 Q101-120"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/snowpro-advanced-data-engineer-exam-dumps\"><b>Snowflake SnowPro Advanced Data Engineer Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 101<\/b><\/h3>\n<p><b>Which feature creates an independent copy of a table without immediate full data duplication?<\/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;\">Temporary stage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Zero-copy clone<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Secure view<\/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;\">Snowflake zero-copy cloning creates a new database object that initially references the existing micro-partition data rather than making a complete physical copy. This makes cloning useful for development, testing, experimentation, and other environments that need an isolated object quickly. As the source and clone change independently, additional storage can be consumed by newly created or modified micro-partitions. Data engineers can therefore use cloning to create practical development environments while avoiding the immediate storage cost of duplicating an entire dataset.<\/span><\/p>\n<h3><b>Question 102<\/b><\/h3>\n<p><b>Which option distinguishes SQL NULL from JSON null in VARIANT data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IS_NULL_VALUE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NULL_CHECK<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JSON_NULL_TEST<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VARIANT_NULL<\/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;\">IS_NULL_VALUE helps determine whether a VARIANT expression contains a JSON null value. This distinction is important because SQL NULL and JSON null are different concepts in Snowflake&#8217;s semi-structured data model. A SQL NULL represents the absence of a SQL value, while JSON null is an explicit null value within JSON content. Data engineers working with VARIANT columns should account for this distinction when filtering, transforming, and validating semi-structured records. Correct null handling prevents unexpected results in analytical transformations and downstream data-quality checks.<\/span><\/p>\n<h3><b>Question 103<\/b><\/h3>\n<p><b>Which function converts a JSON string into a VARIANT value?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TO_VARIANT<\/span><\/li>\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;\">JSON_CONVERT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CAST_JSON<\/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;\">PARSE_JSON converts a string containing valid JSON into a Snowflake VARIANT value. This allows structured JSON content to be queried using Snowflake&#8217;s semi-structured data capabilities. Once parsed, engineers can access nested objects and arrays using path expressions or functions designed for VARIANT data. This is different from simply storing the JSON as plain text because the parsed representation can be navigated and processed as semi-structured data. Proper validation is still important because malformed JSON input can cause parsing failures.<\/span><\/p>\n<h3><b>Question 104<\/b><\/h3>\n<p><b>Which function returns the number of elements in an array?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_SIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARRAY_LENGTH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARRAY_SIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ELEMENT_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;\">ARRAY_SIZE returns the number of elements in a Snowflake array. It is useful when processing semi-structured data stored in VARIANT values where arrays can contain variable numbers of elements. Engineers can use the function in transformations, validation rules, and conditional logic to determine whether an array contains expected content. When combined with other semi-structured functions, it can help build robust pipelines for nested data. Understanding array-specific functions is important when transforming JSON payloads that contain repeated elements or collections.<\/span><\/p>\n<h3><b>Question 105<\/b><\/h3>\n<p><b>Which function reveals the Snowflake data type of an expression?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TYPEOF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DATA_TYPE_OF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VALUE_TYPE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EXPRESSION_KIND<\/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;\">TYPEOF returns a string describing the data type of an expression. It is especially useful when working with VARIANT values because semi-structured data can contain different underlying types within the same column. Engineers can use TYPEOF during profiling, validation, and transformation logic to determine whether a value represents an object, array, string, number, Boolean, or another supported type. This can make ingestion pipelines more resilient when source systems produce heterogeneous JSON structures that require different processing paths.<\/span><\/p>\n<h3><b>Question 106<\/b><\/h3>\n<p><b>Which function aggregates values into a Snowflake array?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARRAY_BUILD<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARRAY_AGG<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COLLECT_ARRAY_VALUES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GROUP_ARRAY<\/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;\">ARRAY_AGG aggregates values from multiple rows into an array. It is useful when a transformation needs to represent related values as a collection rather than separate records. For example, a data engineer can group transaction attributes or related identifiers into an array associated with a parent entity. The resulting array can then be stored or further processed as semi-structured data. Ordering requirements should be considered when deterministic element order is important, because aggregation behavior should not be assumed to provide an arbitrary order unless ordering is explicitly defined.<\/span><\/p>\n<h3><b>Question 107<\/b><\/h3>\n<p><b>Which function builds an object from key-value pairs?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_CONSTRUCT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_CREATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JSON_OBJECT_BUILD<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">KEY_VALUE_OBJECT<\/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;\">OBJECT_CONSTRUCT creates an OBJECT value from supplied key-value pairs. It is useful for dynamically constructing semi-structured records during transformations. Data engineers can use it to combine selected relational columns into a JSON-like object, making it convenient to produce nested or flexible output structures. The function is particularly valuable when preparing data for downstream systems that consume semi-structured payloads. Engineers should understand how NULL values and keys are handled so that generated objects contain the intended attributes and do not unexpectedly omit information.<\/span><\/p>\n<h3><b>Question 108<\/b><\/h3>\n<p><b>What does TARGET_LAG control for a dynamic table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage retention<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Desired freshness<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query timeout<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File expiration<\/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;\">TARGET_LAG specifies the desired freshness of a dynamic table relative to its upstream data. Snowflake uses this target when determining when the dynamic table should refresh. A shorter target generally represents a stronger freshness requirement, while a longer target permits more delay between upstream changes and refreshed results. Data engineers should select a target appropriate to business requirements rather than automatically choosing the smallest possible value. Refresh frequency, dependencies, workload characteristics, and compute consumption should all be considered when designing dynamic-table pipelines.<\/span><\/p>\n<h3><b>Question 109<\/b><\/h3>\n<p><b>Which dynamic table setting allows refresh timing to follow downstream demand?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TARGET_LAG = AUTO<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TARGET_LAG = DOWNSTREAM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REFRESH = CASCADE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DEPENDENCY = FOLLOW<\/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;\">TARGET_LAG = DOWNSTREAM allows a dynamic table&#8217;s refresh behavior to be driven by the freshness requirements of downstream dynamic tables that depend on it. This can be useful when building chains of dynamic tables because upstream objects do not necessarily need independent freshness targets. Instead, the dependency relationship can help coordinate refresh requirements through the pipeline. This design can reduce unnecessary refresh activity when intermediate results do not need to be refreshed more frequently than the downstream consumers require.<\/span><\/p>\n<h3><b>Question 110<\/b><\/h3>\n<p><b>Which refresh mode can process a dynamic table using complete recomputation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FULL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TOTAL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COMPLETE_SCAN<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REBUILD<\/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 FULL refresh mode recomputes the dynamic table result rather than relying exclusively on incremental change processing. Full refreshes can be useful when a query cannot efficiently support incremental refresh or when the workload requires complete recomputation. The appropriate refresh mode depends on the query definition and workload characteristics. Data engineers should evaluate refresh behavior because full recomputation can require more processing than incremental approaches. Understanding refresh modes is important when designing dynamic-table pipelines with predictable performance and resource requirements.<\/span><\/p>\n<h3><b>Question 111<\/b><\/h3>\n<p><b>Which Snowflake object provides maintained precomputed query results?<\/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;\">External table<\/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<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A materialized view stores maintained, precomputed results derived from its underlying query. Snowflake can maintain the materialized data as underlying information changes, allowing eligible queries to benefit from previously computed results. Materialized views differ from standard views because a standard view stores query logic rather than maintaining its own persisted query result. They can be useful for frequently accessed transformations or aggregations where repeatedly computing the same logic would otherwise consume additional resources. Engineers should evaluate maintenance overhead and query patterns before choosing this design.<\/span><\/p>\n<h3><b>Question 112<\/b><\/h3>\n<p><b>Which command can exchange the contents of two tables efficiently?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EXCHANGE TABLES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SWAP WITH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TABLE_SWITCH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REPLACE CONTENTS<\/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 supports SWAP WITH for exchanging the data and metadata of two compatible tables through an efficient metadata operation. This can be useful in deployment workflows where a newly prepared table needs to replace an existing production table with minimal operational complexity. Instead of copying all records between objects, the operation exchanges their identities and associated metadata. Data engineers can use this pattern for controlled table replacement scenarios, but they should carefully verify dependencies, permissions, object characteristics, and downstream references before performing a swap.<\/span><\/p>\n<h3><b>Question 113<\/b><\/h3>\n<p><b>Which statement creates a table using another table&#8217;s structure and data reference?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CREATE TABLE AS VIEW<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CREATE TABLE FROM STAGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CREATE TABLE &#8230; CLONE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CREATE TABLE &#8230; MIRROR<\/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;\">CREATE TABLE &#8230; CLONE creates a clone of an existing table using Snowflake&#8217;s zero-copy cloning capabilities. The new table initially references the source table&#8217;s existing micro-partitions rather than physically duplicating the complete dataset. This is useful for development environments, testing, experimentation, and controlled data-management workflows. The clone becomes independently changeable after creation, and later modifications can result in additional storage consumption. Cloning provides a fast way to create isolated table environments while minimizing immediate physical data duplication.<\/span><\/p>\n<h3><b>Question 114<\/b><\/h3>\n<p><b>Which function extracts a value from a VARIANT object using a path?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PATH_VALUE<\/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;\">JSON_LOCATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_PATH<\/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;\">GET_PATH retrieves a value from semi-structured data using a specified path. It is useful when working with nested objects stored in VARIANT values and when the desired location needs to be expressed explicitly. Snowflake also provides path notation for many common access patterns, but GET_PATH can make path-based extraction explicit in transformation logic. Data engineers should account for missing paths and differing source structures when designing transformations because semi-structured data may not consistently contain every expected attribute.<\/span><\/p>\n<h3><b>Question 115<\/b><\/h3>\n<p><b>What does COPY INTO&#8217;s FILE_FORMAT reference define?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Source parsing rules<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse scaling policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table retention period<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role inheritance behavior<\/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 file format associated with COPY INTO defines how Snowflake interprets staged files during loading or unloading. Depending on the format, settings can specify delimiters, compression, quotation characters, headers, null representations, and other parsing behavior. Reusable named file formats help standardize ingestion configurations across pipelines. Data engineers should ensure the selected format matches the actual source files because incorrect parsing settings can produce shifted columns, malformed records, unexpected NULL values, or failed loads. Centralizing file-format definitions can also simplify operational maintenance.<\/span><\/p>\n<h3><b>Question 116<\/b><\/h3>\n<p><b>Which option skips the first rows of a delimited input file?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OMIT_ROWS<\/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;\">IGNORE_FIRST<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">HEADER_OFFSET<\/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 Snowflake should skip when processing supported delimited files. This is commonly used when source files contain column-header rows that should not be loaded as data. For example, a CSV file with one header row can use an appropriate SKIP_HEADER setting so that only actual records are processed. Engineers should confirm the source format before applying the option because incorrectly skipping rows can remove legitimate data. Consistent source-file conventions make header handling easier to automate.<\/span><\/p>\n<h3><b>Question 117<\/b><\/h3>\n<p><b>Which file-format option treats spaces around fields as removable?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SPACE_CLEANUP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TRIM_SPACE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">STRIP_SPACES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FIELD_TRIMMER<\/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;\">TRIM_SPACE is a file-format option that controls whether spaces surrounding fields are removed during supported data loading operations. This can help normalize incoming delimited data when source systems introduce unnecessary whitespace around values. Without appropriate handling, leading or trailing spaces may cause unexpected comparisons, duplicate-looking records, or validation issues. Data engineers should apply trimming deliberately because whitespace can sometimes be meaningful. File-format configuration should therefore reflect the source system&#8217;s actual data conventions and the semantic requirements of downstream transformations.<\/span><\/p>\n<h3><b>Question 118<\/b><\/h3>\n<p><b>Which option allows a field to be enclosed only when necessary?<\/b><\/p>\n<ol>\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;\">CONDITIONAL_QUOTE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OPTIONAL_FIELD_QUOTES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FLEXIBLE_ENCLOSURE<\/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;\">FIELD_OPTIONALLY_ENCLOSED_BY specifies a character that can optionally surround fields in supported delimited files. This is useful for source formats where values may be enclosed only when they contain delimiters, special characters, or other content requiring protection. Correctly configuring field enclosure helps Snowflake interpret complex delimited records without incorrectly splitting values. Engineers should match this setting to the conventions used by the producing system. Incorrect enclosure settings can result in parsing errors or improperly separated fields during ingestion.<\/span><\/p>\n<h3><b>Question 119<\/b><\/h3>\n<p><b>Which command can recover a dropped schema during its retention period?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RESTORE SCHEMA<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UNDROP SCHEMA<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RECOVER SCHEMA<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REBUILD 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;\">UNDROP SCHEMA can restore a dropped schema when the schema remains recoverable under the applicable Snowflake retention rules. Recovery through UNDROP can help reverse accidental deletion without recreating the schema and its objects manually. The ability to recover depends on object type and available retention conditions. Data engineers should still maintain appropriate operational controls and recovery procedures because retention-based recovery is not unlimited. Understanding object recovery commands is important when designing safe administrative processes for environments containing critical production data.<\/span><\/p>\n<h3><b>Question 120<\/b><\/h3>\n<p><b>Which Snowflake feature can automatically maintain a searchable optimization structure for selective lookups?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query Acceleration 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;\">Search Optimization Service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse Result Cache<\/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;\">Snowflake&#8217;s Search Optimization Service creates and maintains additional structures that can accelerate highly selective lookup queries on eligible tables. It is particularly useful when queries frequently search for specific values without naturally benefiting from conventional clustering. The service is different from Automatic Clustering, which organizes micro-partitions according to clustering keys, and from result caching, which reuses previously computed results. Data engineers should evaluate query patterns before enabling search optimization because the service introduces maintenance considerations and is most valuable for appropriate selective-access workloads.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Snowflake SnowPro Advanced Data Engineer Exam Dumps and Practice Test Dumps &nbsp; Question 101 Which feature creates an independent copy of a table without immediate full data duplication? Materialized view Temporary stage Zero-copy clone Secure view Correct Answer: 3 Explanation: Snowflake zero-copy cloning creates a new database object that initially references the existing [&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\/21914"}],"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=21914"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21914\/revisions"}],"predecessor-version":[{"id":21915,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21914\/revisions\/21915"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21914"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21914"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21914"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}