Hard DP-600 practice questions

An analyst maintains a semantic model with 15 base measures. The business wants each measure to be viewable as Current, Year-to-Date, and Prior Year without creating 45 separate measures. Additionally, the YTD variant should display as currency while a new 'Percent of Total' variant must display as a percentage — all using the same underlying measures. Which combination of features should the analyst implement to meet these requirements with minimal measure duplication?

An analytics engineer has built two calculation groups in a Fabric semantic model: one named 'Time Intelligence' (containing items like YTD, MTD) and another named 'Currency Conversion' (converting measures to EUR and USD). Users report that when they apply a YTD calculation item together with a EUR conversion item on the same visual, the results are inconsistent depending on which group's logic runs first. The engineer must ensure that time intelligence is always evaluated before currency conversion is applied. What should the engineer configure?

You manage a composite semantic model that combines a DirectQuery connection to a multi-billion-row fact table in a Fabric warehouse with several imported dimension tables. Users report that high-level dashboard visuals showing yearly and monthly revenue totals are slow because every query hits the warehouse. Detailed drill-through visuals at the transaction level are used rarely but must remain fully accurate. What should you implement to improve the performance of the aggregated visuals while preserving detail-level accuracy?

You are building a composite semantic model in Power BI Desktop. A large fact table uses DirectQuery against a Fabric warehouse. A shared Date dimension is used both to filter the DirectQuery fact table and to filter a smaller Import-mode fact table for a different report page. You want cross-highlighting and relationship filtering to work efficiently against both fact tables without generating unnecessary queries back to the source. Which storage mode should you set on the Date dimension table?

You are optimizing a DAX query that produces a table of product categories with total sales. A colleague wrote it using SUMMARIZE with the aggregation expression placed directly inside the SUMMARIZE function, and profiling shows slow performance and high CallbackDataID activity in the storage engine. You want to rewrite the query so that the grouping is done efficiently and the aggregation runs in a proper row context without the performance issues of computing extended columns inside SUMMARIZE. Which approach should you use?

You built a calculation group named 'Time Intelligence' with items for MTD, QTD, and YTD in an enterprise semantic model. Business users report that when they apply the 'YTD' calculation item to a non-additive measure such as [Distinct Customers], the result is misleading because a year-to-date accumulation makes no logical sense for that metric. You want the calculation items to apply only to a defined set of additive measures and return the unmodified base measure for all others, without creating separate calculation groups. Which DAX approach inside each calculation item expression best achieves this?

An analyst builds a measure to count high-value orders (amount greater than 1000). When they place this measure in a matrix sliced by product category and also apply an external filter selecting only the 'Electronics' category, they notice that a standard CALCULATE with a boolean filter on order amount unexpectedly overrides part of the existing category filter behavior in a comparison measure. They want the amount condition applied as an ADDITIONAL constraint that intersects with — rather than replaces — any filters already coming from the same column context. Which DAX function should wrap the filter argument to preserve the existing filter context and intersect the new condition?

You are building a semantic model for a retail company. A report page must display each product's rank by total sales within its own product category, so the top-selling product in each category shows rank 1, regardless of how the visual is currently filtered by category. You create a measure called [Total Sales]. Which DAX measure correctly produces the per-category ranking?

An analyst is building a measure for a Power BI report on a Fabric semantic model. The requirement is: return the total sales contributed only by the top 5 products (by their own total sales) within the current filter context, and the measure must respond correctly when a category or year slicer is applied. Which DAX pattern produces the correct result?

You are building a DAX query in a Fabric semantic model. The 'Budget' table stores a 'RegionName' column but has no physical relationship to the 'Sales' table, which also contains a 'RegionName' column. You need to write a measure that returns the sum of Sales amounts filtered by the RegionName values currently present in the Budget table's filter context, without creating a physical relationship. Which DAX function should you use to propagate the filter?

You are building a semantic model in Fabric with a fact table Sales and a marked Date table. Business users want a measure that compares the current visual's quarter total against the total from three quarters earlier, regardless of how the visual is sorted or which quarters are visible. You want to use the DAX window functions introduced for this purpose rather than classic time-intelligence functions. Which DAX function is the most appropriate core of this measure?

You maintain a large enterprise semantic model in a Fabric Premium workspace. A colleague made structural changes (new calculated columns and measures) directly in a development workspace model using an external tool. You now need to promote ONLY those metadata differences to the production model without overwriting production-only partitions or triggering a full data reload. Which approach best accomplishes this?

Your team uses a three-stage Fabric deployment pipeline (Development, Test, Production). A semantic model in Development connects to a warehouse. When content is deployed from Test to Production, you have configured a data source rule on the Production stage that repoints the connection to the production warehouse. However, you also rely on Fabric's automatic re-binding, which connects deployed items to items already present in the target stage. During a deployment to Production, both the data source rule and auto-binding could apply to the same connection. What determines which connection the deployed semantic model uses in Production?

Your team maintains a Fabric workspace containing a semantic model and several reports. The team wants developers to work in isolated feature branches with pull-request reviews before merging, while release managers separately promote validated content from a Development workspace through Test to a Production workspace without touching source files. Which combination of Fabric lifecycle tools should you configure to meet both requirements?

Your team has three developers who each need to work on separate features of the same Power BI project simultaneously without overwriting each other's changes. The workspace is already connected to a Git repository. During development, each developer needs an isolated environment to test their changes before merging them into the shared workspace. Which approach best supports parallel, isolated development in this scenario?

You maintain a Direct Lake semantic model over a lakehouse that holds a 4-billion-row Sales fact table refreshed hourly. Business users also need to compare against a small, static PriorYearBudget table that is maintained manually in an Excel file and is not stored in the lakehouse. You must keep the large Sales table on Direct Lake for freshness and scale, while still bringing in the budget data without moving it into the lakehouse. Which approach meets these requirements?

You publish a Direct Lake semantic model over a large Delta table in a Fabric lakehouse. During peak usage, users report that some visuals become noticeably slower and analysts observe that certain queries no longer benefit from in-memory VertiPaq column loading. In Performance Analyzer you notice these queries are being executed as DirectQuery against the SQL analytics endpoint. The model's DirectLakeBehavior property is left at its default value. What is the MOST likely cause of this behavior?

You manage a Direct Lake semantic model on a Fabric F64 capacity. Business stakeholders complain that report performance is inconsistent: some visuals return instantly while others are noticeably slower, especially during peak hours. Investigation shows that when the model exceeds the maximum in-memory row guardrail, queries silently fall back to DirectQuery against the SQL analytics endpoint, causing the slowdowns. Leadership decides they would rather have a query fail with a clear error than silently degrade performance, so they can identify and fix the offending report. Which configuration change on the semantic model achieves this?

You maintain a Direct Lake semantic model over a large lakehouse fact table with 8 billion rows. Business users report that certain high-cardinality slicer visuals frequently trigger DirectQuery fallback because column memory guardrails are exceeded, causing slow performance. Your priority is to keep the model on Direct Lake for the bulk of queries while ensuring a small, frequently filtered dimension is always served from memory with no fallback. Which approach best meets this requirement?

You are building a Direct Lake semantic model on an F64 capacity over a lakehouse fact table that contains 4.2 billion rows. During validation you observe that queries against this table consistently fall back to DirectQuery, and performance is worse than expected. You confirm the SQL analytics endpoint is healthy and there is no memory eviction occurring. What is the most likely cause of the DirectQuery fallback?

Your team publishes a Direct Lake semantic model over a lakehouse. Security requirements state that row-level filtering must be enforced consistently whether users query through the semantic model, the SQL analytics endpoint, or Spark. The analytics engineer wants to define the security once at the data layer rather than duplicating logic in DAX RLS roles. Which approach on the newer Direct Lake on OneLake mode best meets this goal?

You are building a Direct Lake semantic model over a Fabric lakehouse. The lakehouse contains several Delta tables written directly by a Spark notebook. Your team wants the semantic model to read table data with the least dependency on additional metadata-syncing layers, and you want to avoid the automatic framing delays that can occur when the SQL analytics endpoint has not yet caught up with newly written Delta files. Which approach should you choose when creating the model?

A retail analyst maintains a Direct Lake semantic model built on a Fabric lakehouse Delta table. An overnight Spark job appends the previous day's transactions to the Delta table, writing new Parquet files and updating the Delta log. The next morning, users report that reports still show yesterday's totals and none of the newly appended rows appear. The model is not configured for scheduled refresh. What is the correct explanation and remedy?

A retail company has a 400 million row sales fact table stored as Delta tables in a Fabric lakehouse. Analysts complain that the first report interaction each morning is noticeably slow, but subsequent queries are fast. The semantic model uses Direct Lake storage mode. Investigation shows no fallback to DirectQuery is occurring, and the model stays well within capacity guardrails. What is the MOST likely cause of the slow first query?

You manage a Direct Lake semantic model on an F64 capacity. Users report that certain visuals are intermittently slow during peak hours, but the same visuals are fast at other times. Direct Lake fallback to DirectQuery is NOT occurring. You suspect memory pressure is causing columns to be paged out. Which behavior of Direct Lake best explains the intermittent slowness, and what should you investigate first?