{"id":16951,"date":"2026-09-21T05:31:42","date_gmt":"2026-09-21T05:31:42","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16951"},"modified":"2026-09-21T05:31:42","modified_gmt":"2026-09-21T05:31:42","slug":"microsoft-dp-600-practice-test-questions-and-exam-dumps-part8-q141-160","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-600-practice-test-questions-and-exam-dumps-part8-q141-160\/","title":{"rendered":"Microsoft DP-600 Practice Test Questions and Exam Dumps Part8 Q141-160"},"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 141<\/b><\/h3>\n<p><b>Which Microsoft Fabric item is designed for storing and analyzing data using Kusto Query Language (KQL)?<\/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;\">Notebook<\/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;\">Eventhouse is a Microsoft Fabric item designed for real-time analytics and supports querying event and telemetry data with Kusto Query Language (KQL). It is well suited for high-volume, time-oriented data such as application telemetry, IoT events, and operational logs. A lakehouse supports both files and structured tables, notebooks provide code-based development, and Dataflow Gen2 focuses on data integration and transformation. Therefore, Eventhouse is the appropriate Fabric item when KQL-based analysis of real-time event data is required.<\/span><\/p>\n<h3><b>Question 142<\/b><\/h3>\n<p><b>Which DAX function can return the first non-blank expression from a list of expressions?<\/b><\/p>\n<ol>\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;\">SUM<\/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;\">MAX<\/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;\">COALESCE evaluates multiple expressions and returns the first expression that is not BLANK. It is useful when a measure needs to provide a fallback value when the preferred calculation produces a blank result. For example, a report can use COALESCE to display an alternative value when a primary measure has no result. SUM calculates totals, COUNTROWS counts rows, and MAX returns the largest value. Therefore, COALESCE is the appropriate DAX function when the first available nonblank result is required.<\/span><\/p>\n<h3><b>Question 143<\/b><\/h3>\n<p><b>A data model contains a Date dimension and a Sales fact table. Which relationship direction is generally preferred for a standard star schema?<\/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;\">Fact table to dimension only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dimension to fact table<\/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, filters generally flow from dimension tables toward fact tables. For example, selecting a year from the Date dimension should filter the related Sales fact rows. This creates predictable filtering behavior and helps avoid unnecessary ambiguity that can occur with excessive bidirectional relationships. Bidirectional filtering may be useful in specific scenarios but should not automatically be applied everywhere. Therefore, a dimension-to-fact filtering direction is generally preferred for a conventional star-schema semantic model.<\/span><\/p>\n<h3><b>Question 144<\/b><\/h3>\n<p><b>Which Power Query feature allows a transformation to use a parameterized value that can be changed without rewriting the query logic?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query parameter<\/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;\">Calculation group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Report 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;\">Power Query parameters allow values used by queries and transformations to be defined separately from the transformation logic. A parameter can represent information such as a server name, folder path, date boundary, or environment-specific setting. Changing the parameter can alter the query behavior without requiring the underlying transformation steps to be rewritten. Bookmarks, calculation groups, and tooltips serve reporting or semantic-model purposes rather than controlling Power Query input values. Therefore, a query parameter is the appropriate feature for this requirement.<\/span><\/p>\n<h3><b>Question 145<\/b><\/h3>\n<p><b>Which DAX function can return a value from the previous period when working with a properly configured date table?<\/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;\">PREVIOUSMONTH<\/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;\">DISTINCT<\/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;\">PREVIOUSMONTH returns a table containing dates from the previous month in the current evaluation context and is commonly used in time-intelligence calculations. It can be combined with functions such as CALCULATE to create measures comparing current-period results with the previous month. DATE constructs a date, FORMAT changes the displayed representation of a value, and DISTINCT returns unique values. Therefore, PREVIOUSMONTH is the appropriate DAX function when a calculation needs to evaluate the previous month&#8217;s date context.<\/span><\/p>\n<h3><b>Question 146<\/b><\/h3>\n<p><b>Which Microsoft Fabric capability allows a report to consume a centrally managed model containing relationships and business measures?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Semantic model<\/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;\">Data pipeline<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OneLake shortcut<\/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 semantic model provides a centralized analytical layer containing tables, relationships, measures, hierarchies, and other business logic. Reports can connect to the semantic model and use its standardized definitions rather than recreating calculations independently. Eventstream is intended for streaming data, data pipelines orchestrate data-processing activities, and OneLake shortcuts provide references to external data. Therefore, a semantic model is the appropriate Fabric capability when reports need to consume centrally managed analytical definitions.<\/span><\/p>\n<h3><b>Question 147<\/b><\/h3>\n<p><b>Which Power Query operation converts rows into columns based on values in a selected field?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unpivot<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pivot Column<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Merge Queries<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove Duplicates<\/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;\">Pivot Column transforms values from a selected column into separate columns, using another column to provide the values placed in those new columns. This is useful when source data is stored in a long format but the analytical requirement calls for a wider structure. Unpivot performs the opposite type of reshaping by converting columns into rows. Merge Queries combines related tables, while Remove Duplicates eliminates repeated records. Therefore, Pivot Column is the appropriate Power Query operation when values need to become separate columns.<\/span><\/p>\n<h3><b>Question 148<\/b><\/h3>\n<p><b>Which DAX function can return the rank of a value relative to other values in a specified context?<\/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;\">SUMX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNTX<\/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: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">RANKX evaluates an expression over a table and determines the relative rank of a value within that set. It is useful for scenarios such as ranking products by revenue, customers by sales, or employees by performance. SUMX calculates a sum of row-level expressions, COUNTX counts results from an expression, and AVERAGEX calculates an average. Therefore, RANKX is the appropriate DAX function when a report requires a ranking based on a measure or expression.<\/span><\/p>\n<h3><b>Question 149<\/b><\/h3>\n<p><b>A developer needs to inspect how filters affect a measure during evaluation. Which DAX function can return a table representing the values currently visible for a column?<\/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;\">SUM<\/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;\">MAX<\/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;\">VALUES can return the distinct values visible for a specified column under the current evaluation context. This makes it useful when developing DAX expressions that need to work with the values currently available after filters have been applied. It can also help create more advanced calculations involving the current context. SUM performs numerical aggregation, FORMAT changes display formatting, and MAX returns the highest value. Therefore, VALUES is the appropriate function when a calculation needs access to the distinct values currently represented in a column.<\/span><\/p>\n<h3><b>Question 150<\/b><\/h3>\n<p><b>Which Fabric capability can help identify whether a report or semantic model depends on another analytical item before that item is changed?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lineage view<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Slicer<\/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;\">DAX variable<\/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;\">Lineage view displays dependencies between supported Fabric and Power BI items and can help identify upstream and downstream relationships. Before changing a semantic model, dataflow, or other analytical item, developers can review lineage to determine which reports or models may depend on it. This supports impact analysis and helps reduce unexpected effects from changes. Slicers filter data, tooltips provide contextual information, and DAX variables store intermediate expressions. Therefore, lineage view is the appropriate capability for dependency analysis before making changes.<\/span><\/p>\n<h3><b>Question 151<\/b><\/h3>\n<p><b>Which DAX function returns 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;\">YEAR<\/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;\">DAY<\/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: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The DAY function returns the day-of-month component from a date value, producing an integer from 1 through 31 depending on the date. It can be useful when calculations or classifications require the numeric day component. YEAR extracts the year, MONTH returns the month number, and WEEKDAY returns a number representing the day of the week. Therefore, DAY is the correct DAX function when a calculation needs to retrieve the day portion of a date.<\/span><\/p>\n<h3><b>Question 152<\/b><\/h3>\n<p><b>A semantic model contains an inactive relationship between OrderDate and a Date table. Which DAX function can activate a specific inactive relationship for a calculation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">USERELATIONSHIP<\/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;\">CONCATENATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FORMAT<\/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;\">USERELATIONSHIP allows a DAX calculation to activate an existing inactive relationship for the duration of that calculation. This is particularly useful when a fact table contains multiple date columns, such as OrderDate and ShipDate, that connect to the same Date dimension. The model can keep one relationship active by default while calculations selectively use another relationship when needed. DISTINCTCOUNT counts unique values, CONCATENATE combines text, and FORMAT changes value representation. Therefore, USERELATIONSHIP is the appropriate function for this scenario.<\/span><\/p>\n<h3><b>Question 153<\/b><\/h3>\n<p><b>Which Microsoft Fabric capability can be used to monitor and investigate events generated by applications and other real-time sources?<\/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;\">Report bookmark<\/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;\">Semantic model<\/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;\">Eventhouse is designed for real-time analytical workloads involving event and telemetry data. It provides a suitable environment for storing and querying large volumes of continuously generated events and can support KQL-based analysis. This makes it useful for investigating application activity, operational events, and other real-time information. Bookmarks manage report states, calculation groups support reusable semantic calculations, and semantic models provide a business-oriented analytical layer. Therefore, Eventhouse is the appropriate choice for monitoring and investigating supported real-time event data.<\/span><\/p>\n<h3><b>Question 154<\/b><\/h3>\n<p><b>Which Power Query operation can remove rows where a required column contains blank or null values?<\/b><\/p>\n<ol>\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;\">Merge Queries<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pivot Column<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Append Queries<\/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;\">Power Query provides row-removal operations that can be used to exclude records containing blank, null, or otherwise unwanted values. Removing such rows can be useful when a required field must contain a valid value before data is loaded into the analytical model. Merge Queries combines related tables, Pivot Column reshapes data, and Append Queries combines rows from multiple tables. Therefore, a Remove Rows transformation is appropriate when records with missing required values need to be excluded during data preparation.<\/span><\/p>\n<h3><b>Question 155<\/b><\/h3>\n<p><b>Which DAX function can concatenate text values from multiple rows into a single text result?<\/b><\/p>\n<ol>\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;\">SUMX<\/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;\">MINX<\/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;\">CONCATENATEX iterates over a table and concatenates the resulting text expressions into a single text value. It is useful for creating comma-separated lists or other dynamically generated textual summaries based on the current filter context. SUMX performs numerical summation over row-level expressions, COUNTROWS counts rows, and MINX returns the minimum result from an expression. Therefore, CONCATENATEX is the appropriate DAX function when text from multiple rows needs to be combined into one result.<\/span><\/p>\n<h3><b>Question 156<\/b><\/h3>\n<p><b>Which Microsoft Fabric feature can help an organization identify approved or trusted analytical content for broader consumption?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Endorsement<\/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;\">Notebook<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data pipeline<\/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;\">Fabric and Power BI endorsement capabilities help organizations communicate that analytical content has been reviewed or is recommended for use. Depending on organizational governance practices, content can be promoted or certified to help users identify trusted resources. This can be especially valuable in environments containing many reports and semantic models created by different teams. Eventstream handles real-time events, notebooks support code-based processing, and data pipelines orchestrate workflows. Therefore, endorsement is the appropriate feature for communicating organizational trust in analytical content.<\/span><\/p>\n<h3><b>Question 157<\/b><\/h3>\n<p><b>Which DAX function can return a date shifted by a specified number of months?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EDATE<\/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;\">DISTINCT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COUNT<\/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;\">EDATE returns a date that occurs a specified number of months before or after a starting date. It can be useful for calculations involving rolling periods, maturity dates, subscription periods, or other month-based date shifts. FORMAT changes the displayed representation of a value, DISTINCT returns unique values, and COUNT counts qualifying values. Therefore, EDATE is the appropriate DAX function when a calculation needs to shift a date by a specified number of months.<\/span><\/p>\n<h3><b>Question 158<\/b><\/h3>\n<p><b>A report contains several visuals, but a user should be able to return to a predefined filter and navigation state with one click. Which feature is suitable?<\/b><\/p>\n<ol>\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;\">Dataflow<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row-level security<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object-level security<\/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;\">Bookmarks capture a predefined state of a report, including supported filter, slicer, visibility, and navigation settings. They can be connected to buttons or other report elements so users can quickly return to a saved view. Dataflows prepare and transform data, row-level security restricts records according to user context, and object-level security controls access to model objects. Therefore, a bookmark is the appropriate feature when users need one-click access to a predefined report state.<\/span><\/p>\n<h3><b>Question 159<\/b><\/h3>\n<p><b>Which semantic-model technique can help prevent ambiguous filtering caused by unnecessary bidirectional relationships?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Prefer single-direction relationships where appropriate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Make every relationship bidirectional<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove all dimension tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duplicate every measure<\/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;\">Single-direction relationships can provide more predictable filter propagation and help reduce ambiguity in a semantic model. In a conventional star schema, filters generally flow from dimensions to fact tables, which creates a clear analytical path. Bidirectional relationships can be useful for specific requirements but should not be enabled indiscriminately because multiple filter paths can produce unexpected behavior or ambiguity. Removing dimensions would weaken the model, while duplicating measures does not address relationship behavior. Therefore, using single-direction relationships where appropriate is the preferred modeling technique.<\/span><\/p>\n<h3><b>Question 160<\/b><\/h3>\n<p><b>Which Microsoft Fabric feature allows a developer to use SQL queries directly against tables in a Warehouse?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQL query editor<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Report bookmark<\/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;\">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;\">The SQL query editor provides an interface for writing and executing SQL queries against supported Fabric SQL resources, including Warehouse data. It is useful for developers and analysts who prefer SQL for inspecting tables, filtering records, joining data, and validating analytical results. Report bookmarks manage report states, Eventstream handles real-time event processing, and calculation groups provide reusable semantic calculations. Therefore, the SQL query editor is the appropriate feature when a developer needs to directly query Warehouse tables using SQL.<\/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 141 Which Microsoft Fabric item is designed for storing and analyzing data using Kusto Query Language (KQL)? Eventhouse Lakehouse Notebook Dataflow Gen2 Correct Answer: 1 Explanation Eventhouse is a Microsoft Fabric item designed for real-time analytics and supports querying event and telemetry data [&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\/16951"}],"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=16951"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16951\/revisions"}],"predecessor-version":[{"id":16952,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16951\/revisions\/16952"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16951"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16951"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16951"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}