Pass Your Microsoft DP-600 Exam Easy!

This action is appropriate when a Power BI analyst wants a KPI evaluated under report slicers and semantic model relationships. DAX understands model filter context and report interactions. However, the question instead requires Choose KQL queries against the KQL database. because kQL is optimized for event-stream and time-series analysis patterns.

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 Choose KQL queries against the KQL database. because kQL is optimized for event-stream and time-series analysis patterns.

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 Choose KQL queries against the KQL database. because kQL is optimized for event-stream and time-series analysis patterns.

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 Apply a narrow timestamp predicate before expensive parsing or summarization. because time filtering limits event scans to the relevant investigation scope.

This action is appropriate when a DAX report visual is slow and its measure repeatedly iterates the full fact table for each cell. Reducing unnecessary repeated iterators can improve model query execution. However, the question instead requires Apply a narrow timestamp predicate before expensive parsing or summarization. because time filtering limits event scans to the relevant investigation scope.

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 Apply a narrow timestamp predicate before expensive parsing or summarization. because time filtering limits event scans to the relevant investigation scope.

This action is appropriate when a Fabric analytics model targets compatible OneLake Delta tables and requires low latency without ordinary Import processing. Direct Lake loads Delta-backed columns into memory on demand rather than using conventional Import refresh. However, the question instead requires Evaluate DirectQuery with the source's performance and permission requirements. because directQuery delegates data queries to the source rather than maintaining a full imported copy.

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 DirectQuery with the source's performance and permission requirements. because directQuery delegates data queries to the source rather than maintaining a full imported copy.

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 DirectQuery with the source's performance and permission requirements. because directQuery delegates data queries to the source rather than maintaining a full imported copy.

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 Deduplicate or repair the dimension's key column before defining the relationship. because the one-side column must have suitable uniqueness for a one-to-many relationship.

This action is appropriate when a model mixes one-row-per-order and one-row-per-line totals in one fact table. Mixed grains cause repeated subtotals and confusing model relationships. However, the question instead requires Deduplicate or repair the dimension's key column before defining the relationship. because the one-side column must have suitable uniqueness for a one-to-many relationship.

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 Deduplicate or repair the dimension's key column before defining the relationship. because the one-side column must have suitable uniqueness for a one-to-many relationship.

This action is appropriate when a revenue measure should use the inactive shipment-date relationship for one report page. Explicit activation changes the relationship path only for the intended calculation. However, the question instead requires Keep the principal date relationship active and use an inactive relationship for alternate analysis. because multiple role-playing dates need explicit relationship handling.

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 Keep the principal date relationship active and use an inactive relationship for alternate analysis. because multiple role-playing dates need explicit relationship handling.

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 Keep the principal date relationship active and use an inactive relationship for alternate analysis. because multiple role-playing dates need explicit relationship handling.

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 Model campaign membership with a bridge and define allocation or distinct-count semantics. because multi-membership makes naive revenue summation unsafe.

This action is appropriate when two facts at different grains share a many-to-many identifier and a direct relationship causes ambiguous paths. Fact-to-fact many-to-many joins often duplicate values and complicate filtering. However, the question instead requires Model campaign membership with a bridge and define allocation or distinct-count semantics. because multi-membership makes naive revenue summation unsafe.

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 Model campaign membership with a bridge and define allocation or distinct-count semantics. because multi-membership makes naive revenue summation unsafe.

This action is appropriate when a margin percentage is computed as `SUM(Margin / Revenue)` and overstates results for differently sized transactions. Ratio of totals is usually different from sum of per-row ratios. However, the question instead requires Use SUMX over eligible invoice rows for the row-level expression. because iterators evaluate an expression per row before aggregation.

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 Use SUMX over eligible invoice rows for the row-level expression. because iterators evaluate an expression per row before aggregation.

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 Use SUMX over eligible invoice rows for the row-level expression. because iterators evaluate an expression per row before aggregation.

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 Inspect ALL and REMOVEFILTERS calls for unintended category filter removal. because removing filters on a grouping dimension can flatten per-category results.

This action is appropriate when an analyst needs sales only for customers with lifetime orders above a chosen threshold. Table filters support set-based eligibility before aggregate evaluation. However, the question instead requires Inspect ALL and REMOVEFILTERS calls for unintended category filter removal. because removing filters on a grouping dimension can flatten per-category results.

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 Inspect ALL and REMOVEFILTERS calls for unintended category filter removal. because removing filters on a grouping dimension can flatten per-category results.

This action is appropriate when a model's date dimension omits holidays and dates with no transactions, breaking calculations. Time-intelligence calculations expect a complete and appropriately typed calendar. However, the question instead requires Calculate a prior-year measure with an eligible time shift such as SAMEPERIODLASTYEAR. because time shifting uses the date context to align comparable periods.

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 Calculate a prior-year measure with an eligible time shift such as SAMEPERIODLASTYEAR. because time shifting uses the date context to align comparable periods.

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 Calculate a prior-year measure with an eligible time shift such as SAMEPERIODLASTYEAR. because time shifting uses the date context to align comparable periods.

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 Use an eligible DAX window function with an explicit order definition. because window calculations require a deterministic ordering and partition context.

This action is appropriate when an analyst wants a running total across selected months without including hidden years. Running totals must respect intended report selection boundaries. However, the question instead requires Use an eligible DAX window function with an explicit order definition. because window calculations require a deterministic ordering and partition context.

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 Use an eligible DAX window function with an explicit order definition. because window calculations require a deterministic ordering and partition context.

This action is appropriate when a model has multiple calculation groups whose ordering creates unexpected results. Precedence controls how multiple calculation-item expressions are composed. However, the question instead requires Use SELECTEDMEASURE in the calculation item expression. because sELECTEDMEASURE makes a calculation reusable across eligible measures.

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 Use SELECTEDMEASURE in the calculation item expression. because sELECTEDMEASURE makes a calculation reusable across eligible measures.

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 Use SELECTEDMEASURE in the calculation item expression. because sELECTEDMEASURE makes a calculation reusable across eligible measures.