{"id":16973,"date":"2026-09-21T05:42:50","date_gmt":"2026-09-21T05:42:50","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16973"},"modified":"2026-09-21T05:42:50","modified_gmt":"2026-09-21T05:42:50","slug":"microsoft-dp-600-practice-test-questions-and-exam-dumps-part17-q321-340","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-600-practice-test-questions-and-exam-dumps-part17-q321-340\/","title":{"rendered":"Microsoft DP-600 Practice Test Questions and Exam Dumps Part17 Q321-340"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/dp-600-exam-dumps\"><b>Microsoft DP-600 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 321<\/b><\/h3>\n<p><b>Which DAX function can return the first expression that is not blank from multiple expressions?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FILTER<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SWITCH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COALESCE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALL<\/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;\">COALESCE evaluates multiple expressions and returns the first one that is not BLANK. It is useful when a calculation has a preferred result but needs one or more fallback values if the preferred expression is blank. For example, a measure can return a primary value and then use an alternative calculation when the first result is unavailable. FILTER returns a filtered table, SWITCH evaluates conditions or matching values, and ALL removes filters. Therefore, COALESCE is the appropriate DAX function for selecting the first available nonblank result.<\/span><\/p>\n<h3><b>Question 322<\/b><\/h3>\n<p><b>Which Fabric feature allows a user to analyze a semantic model from Excel or another external analytical experience without creating a separate copy of the model data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Build permission<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OneLake shortcut<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Eventstream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dataflow Gen2<\/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;\">Build permission allows users to create new content based on an existing semantic model, including supported external analytical scenarios such as analyzing data through Excel. The permission provides the ability to reuse the model rather than requiring users to duplicate its underlying data. OneLake shortcuts provide references to data, Eventstream handles streaming workloads, and Dataflow Gen2 performs data preparation. Therefore, Build permission is the relevant permission when users need to consume a semantic model as a source for additional analytical work.<\/span><\/p>\n<h3><b>Question 323<\/b><\/h3>\n<p><b>Which Kusto Query Language operator groups records and can calculate multiple aggregations within each group?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">project<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">summarize<\/span><\/li>\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;\">extend<\/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 summarize operator groups records according to one or more expressions and can calculate aggregations such as count, sum, average, minimum, and maximum for each group. For example, a KQL query can group application events by application name while calculating both the number of events and their average duration. Project controls returned columns, where filters records, and extend creates calculated columns. Therefore, summarize is the appropriate KQL operator when grouped analytical results require one or more aggregations.<\/span><\/p>\n<h3><b>Question 324<\/b><\/h3>\n<p><b>Which semantic-model feature allows a field to be organized inside a named folder without changing its underlying data or calculation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Display folder<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data category<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Relationship<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Calculation group<\/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;\">Display folders organize measures and columns into named groups within the semantic-model interface. They are especially useful in large models where many calculations or fields need to be arranged logically for report authors. A display folder does not alter the field&#8217;s underlying values or calculation logic. Data categories provide semantic metadata, relationships define connections between tables, and calculation groups provide reusable calculation items. Therefore, Display folder is the appropriate feature when the objective is simply to improve the organization and discoverability of model fields.<\/span><\/p>\n<h3><b>Question 325<\/b><\/h3>\n<p><b>A report contains a measure that should calculate sales only for products belonging to the &#8220;Accessories&#8221; category while retaining other relevant report filters. Which DAX function is commonly used to create this calculation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VALUES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CALCULATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DISTINCT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNTROWS<\/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;\">CALCULATE is commonly used to modify filter context for a measure. It can apply a filter such as Product Category equal to Accessories while retaining other applicable filters unless they are explicitly changed. This makes CALCULATE fundamental for creating filtered business measures. VALUES returns a table of distinct values, DISTINCT produces unique values, and COUNTROWS counts rows in a table expression. Therefore, CALCULATE is the appropriate DAX function when a measure needs to evaluate sales under an additional category-specific filter.<\/span><\/p>\n<h3><b>Question 326<\/b><\/h3>\n<p><b>Which Power Query transformation is appropriate for replacing errors with a specified value rather than removing the affected rows?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove Errors<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replace Errors<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove Duplicates<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Filter Rows<\/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;\">Replace Errors substitutes error values with a value specified by the developer. This is useful when an error should be converted into a meaningful default or corrected representation rather than causing the entire record to be removed. Remove Errors takes the opposite approach by deleting rows containing errors. Remove Duplicates handles repeated records, while Filter Rows restricts the result based on conditions. Therefore, Replace Errors is the appropriate transformation when erroneous values need to be replaced while preserving the affected rows.<\/span><\/p>\n<h3><b>Question 327<\/b><\/h3>\n<p><b>Which Fabric item is most appropriate for storing relational data and supporting T-SQL-based analytical queries in a warehouse-style environment?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Eventhouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lakehouse<\/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;\">Notebook<\/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;\">Fabric Warehouse is designed for relational analytical workloads and provides a SQL-centric environment based on T-SQL. It is suitable for structured data, relational objects, and analytical queries where users expect traditional warehouse capabilities. Eventhouse is optimized for event and real-time analytics, while Lakehouse provides data-lake-oriented storage and analytical capabilities. Notebooks provide code-based development rather than a relational warehouse environment. Therefore, Warehouse is the appropriate Fabric item when T-SQL-based relational analytics is the primary requirement.<\/span><\/p>\n<h3><b>Question 328<\/b><\/h3>\n<p><b>Which DAX function can remove filters from a calculation while preserving filters coming from other columns that are not specified?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REMOVEFILTERS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FORMAT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CONCATENATEX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MEDIAN<\/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;\">REMOVEFILTERS clears filters from the specified table or columns while leaving other filter context unaffected unless those areas are also explicitly modified. It is useful when a measure needs to ignore a particular dimension but continue respecting selections from other dimensions. FORMAT changes value representation, CONCATENATEX combines text values, and MEDIAN calculates a middle value. Therefore, REMOVEFILTERS is appropriate when a DAX calculation needs precise control over which filters are removed without broadly clearing the entire evaluation context.<\/span><\/p>\n<h3><b>Question 329<\/b><\/h3>\n<p><b>Which Power Query transformation can aggregate records by one or more columns and calculate results such as Sum, Count, or Average?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Group By<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Split Column<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replace Values<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unpivot Columns<\/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;\">Group By creates aggregated results based on one or more selected columns. It can calculate operations such as Sum, Count Rows, Average, Minimum, and Maximum for groups of records. For example, sales transactions can be grouped by region to calculate total revenue for each region. Split Column separates values into multiple fields, Replace Values substitutes matching values, and Unpivot Columns converts columns into rows. Therefore, Group By is the appropriate Power Query transformation when records need to be summarized by one or more grouping fields.<\/span><\/p>\n<h3><b>Question 330<\/b><\/h3>\n<p><b>Which DAX function can return the current filter-context value when exactly one value is selected, with an optional alternate result?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VALUES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">HASONEVALUE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SELECTEDVALUE<\/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: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">SELECTEDVALUE returns a scalar value when exactly one distinct value is present in the current filter context. It also allows an alternate result to be specified when multiple or no values are selected. This makes it useful for dynamic titles, labels, and calculations based on user selections. HASONEVALUE only tests whether one distinct value exists, VALUES returns a table, and FILTER returns rows that satisfy a condition. Therefore, SELECTEDVALUE is the appropriate function when the actual selected scalar value is required.<\/span><\/p>\n<h3><b>Question 331<\/b><\/h3>\n<p><b>Which Fabric capability provides a centralized location for discovering data assets, understanding their properties, and locating relevant analytical content?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OneLake catalog<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deployment pipeline<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Performance Analyzer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bookmark<\/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 OneLake catalog helps users discover and explore data assets across Microsoft Fabric. It provides a centralized experience for finding relevant items and understanding available data resources, supporting data discovery and governance workflows. Deployment pipelines are used for lifecycle management, Performance Analyzer investigates report performance, and bookmarks preserve report states. Therefore, OneLake catalog is the appropriate Fabric capability when users need to locate and explore available data assets rather than manage deployment or report interactions.<\/span><\/p>\n<h3><b>Question 332<\/b><\/h3>\n<p><b>Which DAX function evaluates a condition and returns one result when true and another when false?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAXX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VALUES<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DISTINCTCOUNT<\/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;\">IF evaluates a logical condition and returns one expression when the condition evaluates to TRUE and another expression when it evaluates to FALSE. It is commonly used for conditional classifications, thresholds, flags, and business rules. MAXX evaluates expressions across rows, VALUES returns distinct values, and DISTINCTCOUNT counts unique values. IF is especially useful when a calculation has two possible outcomes. Therefore, IF is the appropriate DAX function when a calculation needs to return different results according to a Boolean condition.<\/span><\/p>\n<h3><b>Question 333<\/b><\/h3>\n<p><b>Which KQL operator is used to restrict the columns returned by a query while optionally creating calculated expressions?<\/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;\">project<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">count<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">summarize<\/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 project operator controls which columns are returned by a Kusto Query Language query. It can also rename columns or create calculated expressions as part of the resulting projection. This makes project useful for producing a focused query result containing only the fields needed for analysis. Where filters records, count calculates the number of records, and summarize performs grouped aggregation. Therefore, project is the appropriate KQL operator when the query should control the columns included in its final output.<\/span><\/p>\n<h3><b>Question 334<\/b><\/h3>\n<p><b>Which semantic-model relationship direction is generally preferred in a standard star schema to provide predictable filtering?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Both directions for every relationship<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">From fact tables to dimensions only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">From dimensions toward fact tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">No filter direction<\/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;\">In a standard star schema, filtering generally flows from dimension tables toward fact tables. For example, selecting a product category in a Product dimension can filter the related rows in a Sales fact table. This design provides predictable filter propagation and helps avoid unnecessary ambiguity. Bidirectional relationships can be useful in specific modeling scenarios but should not be enabled indiscriminately. Therefore, dimension-to-fact filtering is the commonly preferred direction for relationships in a well-designed star schema.<\/span><\/p>\n<h3><b>Question 335<\/b><\/h3>\n<p><b>Which Power Query feature allows a developer to inspect the sequence of transformations that have been applied to a query?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Applied Steps<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Column Quality<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data Category<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lineage View<\/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;\">Applied Steps displays the sequence of transformation operations performed on a Power Query query. Each step represents a stage in the query&#8217;s transformation process, allowing developers to review, modify, reorder, or remove transformations where appropriate. Column Quality provides information about valid, empty, and error values, Data Category belongs to semantic modeling, and Lineage View shows dependencies among analytical assets. Therefore, Applied Steps is the appropriate feature for reviewing the transformation sequence applied within a Power Query query.<\/span><\/p>\n<h3><b>Question 336<\/b><\/h3>\n<p><b>Which DAX function can rank a value against other values in a table according to an expression?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RANKX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RANK<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ORDERBY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TOPVALUE<\/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;\">RANKX evaluates an expression across a table and determines the rank of a value relative to the other evaluated values. It is useful for creating rankings such as top customers by revenue, products by sales, or regions by performance. The function supports different ordering options and can be combined with filter context to produce context-sensitive rankings. The other listed names do not provide the same standard DAX functionality. Therefore, RANKX is the appropriate DAX function for ranking values based on an expression.<\/span><\/p>\n<h3><b>Question 337<\/b><\/h3>\n<p><b>Which Fabric development feature is intended to maintain a history of supported workspace item changes through a connected Git repository?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deployment pipeline<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git integration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Eventstream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQL analytics endpoint<\/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;\">Git integration allows supported Fabric workspace items to synchronize with a Git repository, enabling source-control workflows and change tracking. Developers can work with repository-based versions of supported items and synchronize changes between the workspace and source control. Deployment pipelines address lifecycle promotion between environments, Eventstream handles streaming data, and SQL analytics endpoints provide SQL access to structured lakehouse data. Therefore, Git integration is the appropriate feature when source-control history and repository synchronization are required.<\/span><\/p>\n<h3><b>Question 338<\/b><\/h3>\n<p><b>Which DAX function can count the number of nonblank values in a numeric column?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNTROWS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DISTINCTCOUNT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SUM<\/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;\">COUNT counts nonblank values in a column and is useful when the requirement is to determine how many populated numeric or date entries exist. It does not remove duplicates from the count. COUNTROWS counts rows in a table, DISTINCTCOUNT counts unique values, and SUM calculates a numeric total. Therefore, COUNT is the appropriate DAX function when the requirement is specifically to count nonblank values in a column, regardless of whether some values are repeated.<\/span><\/p>\n<h3><b>Question 339<\/b><\/h3>\n<p><b>Which Fabric lakehouse feature allows users to reference supported external data without creating another physical copy of that data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OneLake shortcut<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse view<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Calculation group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Field parameter<\/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 OneLake shortcut provides a logical reference to supported data stored elsewhere without requiring a separate physical copy in the destination location. This can help organizations reduce duplication and maintain centralized data while still making it accessible to Fabric workloads. A warehouse view represents reusable SQL logic, a calculation group manages reusable semantic calculations, and a field parameter controls dynamic report fields or measures. Therefore, OneLake shortcut is the appropriate feature when external data should be accessed without duplicating its underlying storage.<\/span><\/p>\n<h3><b>Question 340<\/b><\/h3>\n<p><b>Which DAX function can evaluate an expression for each row and return the highest resulting value?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAXX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SUMX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AVERAGEX<\/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;\">MAXX is an iterator that evaluates an expression for each row in a specified table and returns the largest resulting value. It is useful when the maximum cannot be obtained directly from a column because the value must first be calculated. For example, MAXX can evaluate Quantity multiplied by Unit Price for each transaction and return the largest calculated transaction value. MAX works directly on a column, SUMX calculates a total, and AVERAGEX calculates an average. Therefore, MAXX is the appropriate function for row-level maximum calculations.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft DP-600 Exam Dumps and Practice Test Dumps. &nbsp; Question 321 Which DAX function can return the first expression that is not blank from multiple expressions? FILTER SWITCH COALESCE ALL Correct Answer: 3 Explanation COALESCE evaluates multiple expressions and returns the first one that is not BLANK. It is useful when a calculation [&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\/16973"}],"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=16973"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16973\/revisions"}],"predecessor-version":[{"id":16974,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16973\/revisions\/16974"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16973"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16973"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16973"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}