Pass Your Microsoft DP-600 Exam Easy!

This action is appropriate when a team tries to run a DAX `CALCULATE` expression as if it were a Fabric warehouse stored procedure. Model measure expressions are not interchangeable with T-SQL stored procedures. However, the question instead requires Define the metric as a DAX measure in the semantic model. because dAX understands model filter context and report interactions.

This action is appropriate when a developer copies a SQL `GROUP BY` query directly into KQL and gets parser errors. Equivalent analytical goals use distinct language operators across engines. However, the question instead requires Define the metric as a DAX measure in the semantic model. because dAX understands model filter context and report interactions.

This action is appropriate when an engineer needs transactional SQL joins and view definitions in a Fabric warehouse. T-SQL matches SQL warehouse object and relational operations. However, the question instead requires Define the metric as a DAX measure in the semantic model. because dAX understands model filter context and report interactions.

This action is appropriate when a KQL query returns a million rows to the browser when the analyst only wants a top-ten list. Server-side ranking and limiting avoid overwhelming the client with unneeded results. However, the question instead requires Use DAX performance analysis to evaluate a simpler measure and aggregation strategy. because reducing unnecessary repeated iterators can improve model query execution.

This action is appropriate when a SQL query joins three large tables and times out despite needing only last-day records. Early reduction and plan inspection can avoid unnecessary joins over historical data. However, the question instead requires Use DAX performance analysis to evaluate a simpler measure and aggregation strategy. because reducing unnecessary repeated iterators can improve model query execution.

This action is appropriate when a SQL query returns unexpectedly high revenue after joining promotions to orders. Incorrect relational matching can invalidate sums regardless of runtime speed. However, the question instead requires Use DAX performance analysis to evaluate a simpler measure and aggregation strategy. because reducing unnecessary repeated iterators can improve model query execution.

This action is appropriate when a mixed enterprise solution combines imported reference data with an eligible live source. Composite models allow appropriate mixes of model storage behaviors subject to compatibility. However, the question instead requires Evaluate Direct Lake storage mode and its capacity prerequisites. because direct Lake loads Delta-backed columns into memory on demand rather than using conventional Import refresh.

This action is appropriate when a service owner assumes DirectQuery will always be faster than Import on complex high-concurrency dashboards. Remote query latency and source load can dominate interactive performance. However, the question instead requires Evaluate Direct Lake storage mode and its capacity prerequisites. because direct Lake loads Delta-backed columns into memory on demand rather than using conventional Import refresh.

This action is appropriate when a small published dataset needs fastest interactive model queries and can tolerate scheduled refresh latency. Import stores compressed model data for efficient in-memory querying. However, the question instead requires Evaluate Direct Lake storage mode and its capacity prerequisites. because direct Lake loads Delta-backed columns into memory on demand rather than using conventional Import refresh.

This action is appropriate when a finance model has separate local date fields on several facts and needs consistent monthly reporting. A conformed date table makes time slicing consistent across fact tables. However, the question instead requires Document and enforce the fact grain before creating measures. because mixed grains cause repeated subtotals and confusing model relationships.

This action is appropriate when a product sales semantic model must support date, customer and product slicing over transactions. Dimensional star design supports consistent filters and analytic measures. However, the question instead requires Document and enforce the fact grain before creating measures. because mixed grains cause repeated subtotals and confusing model relationships.

This action is appropriate when a model uses human-readable product descriptions as relationship keys that change frequently. Stable keys prevent descriptive edits from breaking joins and filtering. However, the question instead requires Document and enforce the fact grain before creating measures. because mixed grains cause repeated subtotals and confusing model relationships.

This action is appropriate when a slicer on an unrelated lookup table does not affect sales and an analyst adds a broad cross-filter override. Missing or invalid relationship paths are a modeling problem, not always a DAX problem. However, the question instead requires Activate the shipping relationship in the measure with USERELATIONSHIP where supported. because explicit activation changes the relationship path only for the intended calculation.

This action is appropriate when a dimension filters multiple fact tables with circular relationships and visuals return ambiguous results. Ambiguous filter paths can create unpredictable metric interpretation. However, the question instead requires Activate the shipping relationship in the measure with USERELATIONSHIP where supported. because explicit activation changes the relationship path only for the intended calculation.

This action is appropriate when a customer dimension should filter its sales fact but the model uses ambiguous bidirectional relationships everywhere. Controlled filter direction reduces ambiguity and unexpected propagation. However, the question instead requires Activate the shipping relationship in the measure with USERELATIONSHIP where supported. because explicit activation changes the relationship path only for the intended calculation.

This action is appropriate when a model stores the same customer-campaign membership twice in a bridge and calculated participants double. Bridge cardinality must reflect one unique relationship instance per key pair. However, the question instead requires Create conformed dimensions or a suitable bridge between the facts. because fact-to-fact many-to-many joins often duplicate values and complicate filtering.

This action is appropriate when a customer can belong to several marketing segments and each segment contains many customers. Bridge tables represent valid many-to-many membership without duplicating facts. However, the question instead requires Create conformed dimensions or a suitable bridge between the facts. because fact-to-fact many-to-many joins often duplicate values and complicate filtering.

This action is appropriate when a student has multiple classes and a model author sets both relationship directions broadly to make every visual filter everything. Unrestricted bidirectional relationships can yield ambiguous propagation. However, the question instead requires Create conformed dimensions or a suitable bridge between the facts. because fact-to-fact many-to-many joins often duplicate values and complicate filtering.

This action is appropriate when a DAX calculation can divide by zero when a slicer leaves no eligible transactions. DIVIDE handles denominator-zero scenarios more safely than direct division. However, the question instead requires Divide aggregate margin by aggregate revenue using DIVIDE. because ratio of totals is usually different from sum of per-row ratios.

This action is appropriate when a report needs a reusable intermediate set of customers who exceed a threshold for a later calculation. Table-valued variables can make multi-step DAX calculations explicit and testable. However, the question instead requires Divide aggregate margin by aggregate revenue using DIVIDE. because ratio of totals is usually different from sum of per-row ratios.

This action is appropriate when a measure recalculates an expensive intermediate total three times in one DAX expression. Variables improve readability and can avoid redundant evaluation. However, the question instead requires Divide aggregate margin by aggregate revenue using DIVIDE. because ratio of totals is usually different from sum of per-row ratios.

This action is appropriate when a DAX model filters product and region but mistakenly removes both when computing percent of total product. Denominator filter scope determines whether percentages match visible business segments. However, the question instead requires Build a filtered customer table and evaluate revenue in that filter context. because table filters support set-based eligibility before aggregate evaluation.

This action is appropriate when a KPI must return sales for premium customers while respecting a separate date slicer. CALCULATE can modify selected filter dimensions without erasing unrelated slicers. However, the question instead requires Build a filtered customer table and evaluate revenue in that filter context. because table filters support set-based eligibility before aggregate evaluation.

This action is appropriate when a calculated column uses a naked aggregation and returns the same total for every row. Row context alone does not automatically apply all aggregation filters. However, the question instead requires Build a filtered customer table and evaluate revenue in that filter context. because table filters support set-based eligibility before aggregate evaluation.

This action is appropriate when a business defines months using a custom 4-4-5 calendar but a report uses Gregorian month numbers. Custom period systems cannot be represented reliably by default calendar-month grouping. However, the question instead requires Build a contiguous date table spanning the required reporting range. because time-intelligence calculations expect a complete and appropriately typed calendar.

This action is appropriate when a prior-month measure returns blanks because the visual uses a text MonthName column without year context. Period calculations need an unambiguous temporal axis. However, the question instead requires Build a contiguous date table spanning the required reporting range. because time-intelligence calculations expect a complete and appropriately typed calendar.

This action is appropriate when executives need year-to-date sales respecting the official fiscal calendar. Accurate YTD measures depend on an appropriate date dimension and fiscal boundary. However, the question instead requires Build a contiguous date table spanning the required reporting range. because time-intelligence calculations expect a complete and appropriately typed calendar.

This action is appropriate when a window function produces unstable results when multiple rows share the same sort value. Stable window results require a defined order within ties. However, the question instead requires Define the window frame using the visible date ordering and selected filter scope. because running totals must respect intended report selection boundaries.

This action is appropriate when a sales leader wants to rank stores by revenue within the currently selected region. Ranking should be calculated over the appropriate comparison set. However, the question instead requires Define the window frame using the visible date ordering and selected filter scope. because running totals must respect intended report selection boundaries.

This action is appropriate when a ranking measure assigns unexpected equal positions to all products because the iterator set contains one row. RANKX requires the correct peer set, not the current single row. However, the question instead requires Define the window frame using the visible date ordering and selected filter scope. because running totals must respect intended report selection boundaries.

This action is appropriate when a calculation group changes a decimal KPI to a whole number in every report. Reusable calculations must preserve the meaning and display of their results. However, the question instead requires Review calculation group precedence and test combined selections. because precedence controls how multiple calculation-item expressions are composed.

This action is appropriate when a team tries to create calculation groups without checking the model editing tool and compatibility. Calculation group authoring depends on model capabilities and supported tools. However, the question instead requires Review calculation group precedence and test combined selections. because precedence controls how multiple calculation-item expressions are composed.

This action is appropriate when a large model repeats year-to-date, prior-year and growth calculations for dozens of base measures. Calculation groups reduce repeated measure patterns by transforming selected measures. However, the question instead requires Review calculation group precedence and test combined selections. because precedence controls how multiple calculation-item expressions are composed.