{"id":16971,"date":"2026-09-21T05:42:27","date_gmt":"2026-09-21T05:42:27","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16971"},"modified":"2026-09-21T05:42:27","modified_gmt":"2026-09-21T05:42:27","slug":"microsoft-dp-600-practice-test-questions-and-exam-dumps-part16-q301-320","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-600-practice-test-questions-and-exam-dumps-part16-q301-320\/","title":{"rendered":"Microsoft DP-600 Practice Test Questions and Exam Dumps Part16 Q301-320"},"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 301<\/b><\/h3>\n<p><b>Which semantic-model storage mode keeps data at the source and sends queries to that source when users interact with a report?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Import<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Direct Lake<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DirectQuery<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dual<\/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;\">DirectQuery keeps the underlying data at its source instead of importing the complete dataset into the semantic model. When users interact with report visuals, queries are sent to the underlying source to retrieve the required results. This approach can be useful when data needs to remain at the source or when importing the full dataset is impractical. Import mode stores data in the model, while Direct Lake reads supported Fabric Delta data directly from OneLake. Therefore, DirectQuery is the appropriate storage mode for source-based query execution.<\/span><\/p>\n<h3><b>Question 302<\/b><\/h3>\n<p><b>Which DAX function can shift a date column by a specified number of intervals such as months or years?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DATEADD<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TODAY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">YEAR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WEEKDAY<\/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;\">DATEADD shifts the dates in a date column by a specified number of intervals, such as days, months, quarters, or years. It is useful for time-intelligence calculations where the required comparison period is not limited to the same period of the previous year. For example, DATEADD can shift a date context forward or backward by one month. TODAY returns the current date, YEAR extracts a year, and WEEKDAY returns a day-of-week value. Therefore, DATEADD is the appropriate function for shifting date contexts.<\/span><\/p>\n<h3><b>Question 303<\/b><\/h3>\n<p><b>Which Fabric item is designed to store structured analytical data in Delta tables while also providing access to files in OneLake?<\/b><\/p>\n<ol>\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;\">Report<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dataflow<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dashboard<\/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 Fabric lakehouse combines data-lake storage with analytical capabilities and uses OneLake as its underlying storage foundation. It provides areas for files and structured tables, with lakehouse tables commonly stored in Delta format. This makes a lakehouse suitable for data engineering and analytical workloads that need both file-based storage and structured tabular data. Reports and dashboards focus on presentation, while dataflows primarily provide transformation and integration capabilities. Therefore, a lakehouse is the appropriate Fabric item for this combined storage scenario.<\/span><\/p>\n<h3><b>Question 304<\/b><\/h3>\n<p><b>Which DAX function can return the largest numeric value directly from a column?<\/b><\/p>\n<ol>\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;\">MAX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SUM<\/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: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">MAX returns the largest value in a specified column. It is appropriate when the maximum value can be obtained directly from the column without first evaluating a row-level expression. MAXX is different because it evaluates an expression for each row of a table and then returns the largest resulting value. SUM calculates a total, while MEDIAN returns the middle value of a dataset. Therefore, MAX is the appropriate DAX function when the requirement is simply to identify the largest value stored in a column.<\/span><\/p>\n<h3><b>Question 305<\/b><\/h3>\n<p><b>A report contains a detailed page for individual customers. Users should be able to right-click a customer in another visual and navigate to that page with the selected customer automatically applied as a filter. Which feature should be configured?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Drillthrough<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tooltip<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bookmark<\/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;\">Drillthrough allows users to navigate from one report visual to a dedicated detail page while carrying the selected data context to that page. For example, a customer detail page can use CustomerID as its drillthrough field so that selecting a customer from a summary visual opens the page filtered to that customer. Tooltips provide additional information on hover, bookmarks save report states, and field parameters dynamically change fields or measures. Therefore, Drillthrough is the appropriate feature for this contextual navigation requirement.<\/span><\/p>\n<h3><b>Question 306<\/b><\/h3>\n<p><b>Which Power Query transformation removes rows that contain errors from a query result?<\/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;\">Fill Down<\/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;\">Remove Errors eliminates rows containing errors from the selected column or query. This can be useful when invalid source values should not continue into downstream transformations or the final analytical dataset. Replace Errors takes a different approach by substituting an alternative value for the error rather than deleting the affected row. Remove Duplicates handles repeated records, while Fill Down propagates values into subsequent rows. Therefore, Remove Errors is the appropriate transformation when error-containing rows should be excluded from the query result.<\/span><\/p>\n<h3><b>Question 307<\/b><\/h3>\n<p><b>Which DAX function can replace a blank expression with a specified alternative value while leaving nonblank results unchanged?<\/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;\">COALESCE<\/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;\">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;\">COALESCE returns the first expression that is not blank, making it useful for providing fallback values. A common example is returning zero when a measure would otherwise return BLANK. Unlike more complex conditional logic, COALESCE can handle several possible expressions in sequence and select the first available nonblank result. IF can also handle conditions but requires explicit logical expressions, while SWITCH evaluates multiple branches and VALUES returns distinct values. Therefore, COALESCE is the most direct function for replacing blank results with an alternative.<\/span><\/p>\n<h3><b>Question 308<\/b><\/h3>\n<p><b>Which KQL operator can create a new calculated column based on an expression involving existing columns?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">extend<\/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;\">summarize<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">where<\/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 KQL extend operator adds calculated columns to the query result using expressions based on existing fields or other calculations. For example, an analyst can create a duration column by subtracting a start timestamp from an end timestamp. Unlike project, which controls the columns returned, extend adds new calculated fields while retaining the existing columns. Summarize performs aggregation, and where filters records. Therefore, extend is the appropriate KQL operator when a query needs to derive a new column from existing data.<\/span><\/p>\n<h3><b>Question 309<\/b><\/h3>\n<p><b>Which Power BI semantic-model property can assign a field to a category such as Web URL, Image URL, or geographic information?<\/b><\/p>\n<ol>\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;\">Display folder<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Perspective<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hierarchy<\/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;\">Data category assigns semantic metadata to a column so Power BI can interpret the field appropriately. Examples include Web URL, Image URL, latitude, longitude, city, and country or region categories. This metadata can influence how Power BI treats or presents the field in reports and visuals. Display folders organize fields, perspectives expose selected model objects, and hierarchies create navigable levels. Therefore, Data category is the appropriate semantic-model property when a field needs to be identified according to its business or data type.<\/span><\/p>\n<h3><b>Question 310<\/b><\/h3>\n<p><b>Which DAX function can return a table grouped by specified columns and optionally include calculated 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;\">SUMMARIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DIVIDE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ISBLANK<\/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;\">SUMMARIZE creates a table grouped according to specified columns and can include additional expressions in the resulting table. It is useful for advanced DAX scenarios where grouped intermediate results are required for further calculations. FILTER returns rows satisfying a condition, DIVIDE performs arithmetic division, and ISBLANK checks whether an expression is blank. SUMMARIZE should be used with an understanding of filter and evaluation context because its behavior can vary depending on how the expression is constructed. Therefore, SUMMARIZE is the appropriate function for grouped table results.<\/span><\/p>\n<h3><b>Question 311<\/b><\/h3>\n<p><b>Which Fabric capability allows a user to promote supported analytical content from one lifecycle stage to another?<\/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;\">OneLake shortcut<\/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;\">Tooltip<\/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;\">Deployment pipelines provide a structured lifecycle process for promoting supported content between environments such as development, test, and production. They help teams manage changes separately from the production version and provide a repeatable promotion process for supported Fabric and Power BI items. OneLake shortcuts reference data, data categories provide semantic metadata, and tooltips enhance report interactions. Therefore, a deployment pipeline is the appropriate capability when analytical content needs to move through controlled lifecycle stages.<\/span><\/p>\n<h3><b>Question 312<\/b><\/h3>\n<p><b>Which DAX function can return the day number from a date value?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MONTH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">YEAR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DAY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DATE<\/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;\">DAY extracts the day component from a date and returns its numeric day value. For example, applying DAY to a date such as July 18 returns 18. MONTH extracts the month number, YEAR extracts the year, and DATE constructs a date from separate year, month, and day values. DAY can be useful in calculations or classifications that depend on the day portion of a date. Therefore, DAY is the appropriate DAX function when the requirement is to retrieve the numeric day from an existing date value.<\/span><\/p>\n<h3><b>Question 313<\/b><\/h3>\n<p><b>Which Fabric lakehouse area contains managed tables that can be queried through the lakehouse&#8217;s SQL analytics endpoint?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Files<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shortcuts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reports<\/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 Tables area of a Fabric lakehouse contains structured tables that can be queried through supported lakehouse analytical experiences, including the SQL analytics endpoint. These tables are commonly stored using the Delta format and provide a structured representation of data for analytical workloads. The Files area is intended for file-based storage, while reports are presentation artifacts. Shortcuts provide references to data rather than representing a separate report or semantic object. Therefore, Tables is the appropriate lakehouse area for managed structured tables.<\/span><\/p>\n<h3><b>Question 314<\/b><\/h3>\n<p><b>Which DAX function can calculate a value while changing filters and return a scalar result rather than a table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CALCULATETABLE<\/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;\">FILTER<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">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;\">CALCULATE evaluates a scalar expression after modifying the filter context. It is fundamental to DAX because it allows measures to apply additional filters, remove existing filters, or change how data is evaluated. CALCULATETABLE performs similar filter-context modification but returns a table expression instead. FILTER returns a filtered table, while VALUES returns distinct values. Therefore, CALCULATE is the appropriate function when a calculation needs modified filter context and the final result is a scalar value such as a total, average, or ratio.<\/span><\/p>\n<h3><b>Question 315<\/b><\/h3>\n<p><b>Which Power Query feature can identify the number and distribution of distinct values within a column during data preparation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Column distribution<\/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;\">Query folding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Applied steps<\/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;\">Column distribution provides information about the distribution of values within a column, including the number of distinct and unique values represented in the data. This can help developers identify patterns, repeated values, or columns with unexpected distributions during data preparation. Column quality focuses on valid, empty, and error values, while query folding concerns source-side execution of transformations. Applied steps display the sequence of transformations. Therefore, Column distribution is the appropriate feature for examining the distribution of values within a column.<\/span><\/p>\n<h3><b>Question 316<\/b><\/h3>\n<p><b>Which DAX function can return the current month number from a date expression?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MONTH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">YEAR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DAY<\/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;\">MONTH extracts the month component from a date expression and returns its numeric value from 1 through 12. It can be used in date classifications, filtering logic, and calculations that need to identify the month associated with a record. DATE creates a date from individual components, YEAR extracts the year, and DAY extracts the day of the month. Therefore, MONTH is the appropriate DAX function when a calculation needs to retrieve the numeric month from an existing date.<\/span><\/p>\n<h3><b>Question 317<\/b><\/h3>\n<p><b>Which Fabric security mechanism is intended to classify sensitive information and apply organizational protection policies to supported data assets?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sensitivity label<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Drillthrough<\/span><\/li>\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;\">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;\">Sensitivity labels are used to classify and protect sensitive information according to an organization&#8217;s information-protection policies. Labels can communicate the sensitivity level of content and, depending on the configured environment and supported services, can participate in protection and governance controls. Drillthrough provides report navigation, display folders organize semantic-model fields, and field parameters allow users to switch fields or measures dynamically. Therefore, sensitivity labels are the appropriate mechanism when the requirement concerns classification and protection of sensitive analytical content.<\/span><\/p>\n<h3><b>Question 318<\/b><\/h3>\n<p><b>Which DAX function can return a scalar value from an expression when exactly one value exists, while allowing an alternate result otherwise?<\/b><\/p>\n<ol>\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;\">VALUES<\/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: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">SELECTEDVALUE returns the single value of a column when exactly one distinct value exists in the current filter context. It can also specify an alternate result to return when multiple or no values are present. HASONEVALUE only tests whether one distinct value exists and returns a Boolean result, while VALUES returns a table of distinct values. ALL removes filters. Therefore, SELECTEDVALUE is the appropriate function when the calculation needs to retrieve the actual selected scalar value and optionally provide a fallback result.<\/span><\/p>\n<h3><b>Question 319<\/b><\/h3>\n<p><b>Which Power Query transformation can replace one value with another value throughout a selected column?<\/b><\/p>\n<ol>\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;\">Fill Down<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove Rows<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Group By<\/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;\">Replace Values changes matching values in a selected column according to the replacement specified by the developer. It is useful for standardizing inconsistent source values, correcting known data issues, or mapping one representation to another. Fill Down propagates an existing value into subsequent rows, Remove Rows deletes records, and Group By creates aggregations. Replace Values therefore provides a direct way to substitute one value for another during Power Query data preparation without restructuring the entire dataset.<\/span><\/p>\n<h3><b>Question 320<\/b><\/h3>\n<p><b>Which DAX function can calculate the average of an expression evaluated for every row in a table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MEDIANX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AVERAGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AVERAGEX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SUMX<\/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;\">AVERAGEX evaluates an expression for each row of a table and then calculates the average of the resulting values. It is useful when the value being averaged must be derived from multiple fields rather than read directly from a single column. For example, AVERAGEX can calculate the average revenue per transaction when revenue is computed from quantity and price. AVERAGE works directly on a column, MEDIANX calculates a median, and SUMX calculates a sum. Therefore, AVERAGEX is appropriate for row-level expression averages.<\/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 301 Which semantic-model storage mode keeps data at the source and sends queries to that source when users interact with a report? Import Direct Lake DirectQuery Dual Correct Answer: 3 Explanation DirectQuery keeps the underlying data at its source instead of importing 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\/16971"}],"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=16971"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16971\/revisions"}],"predecessor-version":[{"id":16972,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16971\/revisions\/16972"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16971"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16971"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16971"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}