{"id":21928,"date":"2026-09-25T10:07:00","date_gmt":"2026-09-25T10:07:00","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21928"},"modified":"2026-09-25T10:07:00","modified_gmt":"2026-09-25T10:07:00","slug":"snowflake-snowpro-advanced-data-engineer-practice-test-questions-and-exam-dumps-part13-q241-260","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-advanced-data-engineer-practice-test-questions-and-exam-dumps-part13-q241-260\/","title":{"rendered":"Snowflake SnowPro Advanced Data Engineer Practice Test Questions and Exam Dumps Part13 Q241-260"},"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 241<\/b><\/h3>\n<p><b>Which object stores reusable SQL transformation logic?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table<\/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;\">View<\/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: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A view stores a reusable SQL query definition that can present transformed or filtered data without storing a separate physical copy of the underlying result. Views are useful for abstraction, data access patterns, and reusable transformation logic. Data engineers can use views to expose curated datasets while keeping the underlying tables separate from consumer-facing structures. Unlike materialized views, standard views do not maintain a physically stored result set. Choosing between these objects depends on performance, freshness, storage, and transformation requirements.<\/span><\/p>\n<h3><b>Question 242<\/b><\/h3>\n<p><b>Which privilege permits inserting rows into a table?<\/b><\/p>\n<ol>\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;\">LOAD<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WRITE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MODIFY<\/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 INSERT privilege allows a role to insert rows into a table. Snowflake uses role-based access control to separate object ownership from individual data-operation permissions. When designing data pipelines, engineers should grant only the privileges required by the workload. A transformation task that writes into a target table may require INSERT along with other privileges depending on the SQL operation. Carefully scoped grants reduce unnecessary access while still allowing automated processing to complete successfully.<\/span><\/p>\n<h3><b>Question 243<\/b><\/h3>\n<p><b>Which object can encapsulate procedural SQL logic?<\/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;\">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: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A stored procedure can encapsulate procedural logic and execute multiple operations according to its implementation. Procedures are useful for orchestration, administrative workflows, conditional processing, and reusable database operations. Unlike a simple view, a procedure can contain procedural statements and perform actions rather than merely returning a query result. Data engineers should select procedures when workflow behavior requires procedural control, while simpler transformations can often remain within SQL statements or views.<\/span><\/p>\n<h3><b>Question 244<\/b><\/h3>\n<p><b>Which object is designed for reusable scalar calculations?<\/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;\">User-defined function<\/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: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A user-defined function can encapsulate reusable calculation logic and return a value based on supplied arguments. Scalar UDFs are useful when the same business calculation must be applied consistently across multiple SQL statements or datasets. Centralizing the calculation can reduce duplicated SQL and improve maintainability. Engineers should consider whether the function&#8217;s logic is appropriate for row-level execution and evaluate its performance when used across large datasets.<\/span><\/p>\n<h3><b>Question 245<\/b><\/h3>\n<p><b>Which UDF type returns multiple rows through a table result?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table function<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scalar function<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Aggregate function<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Boolean function<\/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 table function returns a tabular result that can be queried as part of a SQL statement. This makes table functions useful for reusable logic that needs to produce multiple rows or columns rather than a single scalar value. Engineers can use table functions when a transformation needs parameterized, reusable result sets. The distinction between scalar and table functions is important because their invocation patterns and output structures differ.<\/span><\/p>\n<h3><b>Question 246<\/b><\/h3>\n<p><b>Which procedure execution mode uses the caller&#8217;s privileges?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EXECUTE AS OWNER<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EXECUTE AS CALLER<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EXECUTE AS ROLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EXECUTE AS USER<\/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;\">EXECUTE AS CALLER causes a stored procedure to execute using the privileges of the user invoking it, subject to Snowflake&#8217;s authorization rules. This can be useful when the procedure should respect the caller&#8217;s existing access rather than using the procedure owner&#8217;s privileges. Engineers should choose execution context deliberately because it directly affects security behavior. Procedures that need controlled elevated access may use a different execution model when appropriate.<\/span><\/p>\n<h3><b>Question 247<\/b><\/h3>\n<p><b>Which object can expose a curated SQL result without duplicating table data?<\/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;\">Stage<\/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;\">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 exposes the result of its stored SQL definition without creating a separate physical copy of the underlying table data. This makes views useful for presenting filtered, joined, or transformed datasets to downstream consumers. They can also provide an abstraction layer between physical storage and analytical users. Engineers should remember that query performance still depends on the underlying execution plan and data structures because a standard view does not independently materialize its result.<\/span><\/p>\n<h3><b>Question 248<\/b><\/h3>\n<p><b>Which object maintains a physically stored query result?<\/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;\">External table<\/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;\">Directory 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 a stored representation of its query result that Snowflake can maintain automatically. This can improve performance for suitable repeated query patterns because consumers may avoid recomputing the complete underlying transformation each time. Materialized views are different from standard views, which store only the query definition. Engineers should evaluate workload patterns, maintenance overhead, supported SQL constructs, and performance requirements before choosing a materialized view.<\/span><\/p>\n<h3><b>Question 249<\/b><\/h3>\n<p><b>Which table type is automatically temporary for a session?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Permanent table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transient 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;\">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 temporary table exists only within the session in which it is created and is automatically removed when that session ends. Temporary tables are useful for intermediate processing, session-specific transformations, and short-lived analytical workloads. They differ from transient and permanent tables because their lifecycle is tied directly to the session. Engineers should avoid relying on temporary objects for data that must survive beyond the current session or be accessed by other sessions.<\/span><\/p>\n<h3><b>Question 250<\/b><\/h3>\n<p><b>Which table type omits Fail-safe storage?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Permanent table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transient table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hybrid table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary 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;\">Transient tables do not have the Fail-safe protection associated with permanent tables. They are intended for data that does not require the same long-term recovery characteristics. This can make transient tables useful for intermediate or reproducible datasets where extended recovery protection is unnecessary. Engineers should choose table types according to retention, recovery, governance, and workload requirements rather than using transient tables solely as a performance optimization.<\/span><\/p>\n<h3><b>Question 251<\/b><\/h3>\n<p><b>Which command removes all rows while retaining a table definition?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DELETE TABLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CLEAR TABLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TRUNCATE TABLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EMPTY TABLE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">TRUNCATE TABLE removes all rows from a table while retaining the table object and its structure. It is useful when a table needs to be emptied before being repopulated by a pipeline. This differs from dropping the table because the schema object remains available. Engineers should consider transaction behavior, downstream dependencies, and recovery requirements before truncating production tables because the operation removes the existing table contents.<\/span><\/p>\n<h3><b>Question 252<\/b><\/h3>\n<p><b>Which SQL construct filters rows after window calculations?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WHERE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">QUALIFY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">HAVING<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FILTER<\/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;\">QUALIFY filters results after window functions have been evaluated. This makes it particularly useful for queries that rank, sequence, or otherwise calculate window values before selecting the required rows. For example, engineers can use ROW_NUMBER() together with QUALIFY to retain a single record per business key. This avoids nesting the window calculation inside another query solely for filtering purposes and can make analytical transformation SQL easier to read.<\/span><\/p>\n<h3><b>Question 253<\/b><\/h3>\n<p><b>Which function converts a string into a timestamp when parsing succeeds?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TO_TIMESTAMP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PARSE_TIMESTAMP_TEXT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">STRING_TIMESTAMP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CAST_TIMESTAMP_TEXT<\/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;\">TO_TIMESTAMP converts an expression into a timestamp according to the supported input and conversion rules. It is commonly used when ingestion pipelines receive timestamps as strings and transformations need a proper temporal data type. Correct timestamp conversion is important for filtering, ordering, window calculations, and incremental processing. Engineers should account for input formats, time zones, and invalid values when designing robust timestamp transformations.<\/span><\/p>\n<h3><b>Question 254<\/b><\/h3>\n<p><b>Which function safely converts invalid values to NULL?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CAST_SAFE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TRY_CAST<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SAFE_CONVERT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NULL_CAST<\/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;\">TRY_CAST performs a conversion and returns NULL when the conversion cannot be performed instead of raising a conversion error. This behavior is useful when data pipelines contain potentially malformed values and should continue processing valid records. Engineers can use TRY-based conversion functions to make ingestion and transformation logic more resilient. However, silently converting invalid values to NULL can hide source-quality problems, so pipelines should still include appropriate validation and monitoring.<\/span><\/p>\n<h3><b>Question 255<\/b><\/h3>\n<p><b>Which function extracts elements from semi-structured data into rows?<\/b><\/p>\n<ol>\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;\">EXPAND_JSON<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UNNEST_OBJECT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARRAY_ROWS<\/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;\">FLATTEN converts semi-structured data into a relational representation by producing rows for elements within arrays or objects. It is frequently used with VARIANT data when engineers need to transform nested JSON structures into queryable rows. FLATTEN exposes useful metadata such as sequence, key, path, index, and value. Data engineers can combine these outputs with lateral joins and filtering to build structured transformation pipelines from nested source data.<\/span><\/p>\n<h3><b>Question 256<\/b><\/h3>\n<p><b>Which data type can store semi-structured JSON-like values?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">STRING<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VARIANT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BINARY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NUMBER<\/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;\">VARIANT is designed to store semi-structured data such as JSON, XML, and other supported hierarchical values. It allows Snowflake to retain nested structures while providing SQL functionality for querying and transforming the contents. Data engineers frequently use VARIANT during ingestion before extracting selected attributes into relational columns. This approach can be useful when source schemas evolve or contain nested structures that are difficult to model immediately as fixed relational columns.<\/span><\/p>\n<h3><b>Question 257<\/b><\/h3>\n<p><b>Which function creates an object from named key-value pairs?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_AGG<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_KEYS<\/span><\/li>\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_BUILD<\/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;\">OBJECT_CONSTRUCT creates an object from supplied key-value expressions. It is useful when engineers need to construct semi-structured objects during transformations or prepare structured payloads for downstream processing. OBJECT_AGG serves a different purpose by aggregating values into an object across rows. Understanding these distinctions helps data engineers choose the appropriate function when converting relational data into hierarchical representations.<\/span><\/p>\n<h3><b>Question 258<\/b><\/h3>\n<p><b>Which function aggregates values into an object by key?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_KEYS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_AGG<\/span><\/li>\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_VALUES<\/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;\">OBJECT_AGG aggregates key-value pairs into an object across rows. It is useful when a relational dataset needs to be transformed into a hierarchical representation where multiple records contribute properties to a single object. Data engineers can use it in reporting, API-oriented transformations, and semi-structured data preparation. The keys should be managed carefully because duplicate-key behavior and aggregation semantics need to match the intended transformation.<\/span><\/p>\n<h3><b>Question 259<\/b><\/h3>\n<p><b>Which function returns the keys from an object?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_KEYS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_FIELDS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET_OBJECT_KEYS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OBJECT_NAMES<\/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_KEYS returns an array containing the keys from a Snowflake object. It is useful when processing semi-structured data whose attributes need to be inspected dynamically. Engineers can combine it with other semi-structured functions when building metadata-driven transformations or exploring variable JSON structures. Because the returned result is an array rather than a relational rowset, additional processing may be required when each key needs to become an individual row.<\/span><\/p>\n<h3><b>Question 260<\/b><\/h3>\n<p><b>Which function counts rows satisfying a Boolean condition?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CONDITIONAL_COUNT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNT_WHERE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNT_IF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BOOLEAN_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;\">COUNT_IF counts rows for which a specified condition evaluates to true. It is useful for conditional metrics such as counting successful records, failed validations, active entities, or records meeting a business threshold. Using COUNT_IF can simplify aggregation logic compared with manually constructing equivalent conditional expressions. Data engineers should ensure that the Boolean condition correctly represents the intended business rule and understand how NULL values affect the condition&#8217;s evaluation.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Snowflake SnowPro Advanced Data Engineer Exam Dumps and Practice Test Dumps &nbsp; Question 241 Which object stores reusable SQL transformation logic? Table Stage View File format Correct Answer: 3 Explanation: A view stores a reusable SQL query definition that can present transformed or filtered data without storing a separate physical copy of the [&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\/21928"}],"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=21928"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21928\/revisions"}],"predecessor-version":[{"id":21929,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21928\/revisions\/21929"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21928"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21928"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21928"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}