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 the supported T-SQL environment for warehouse relational querying. because t-SQL matches SQL warehouse object and relational operations.

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 the supported T-SQL environment for warehouse relational querying. because t-SQL matches SQL warehouse object and relational operations.

This action is appropriate when an incident team needs subsecond exploratory filtering over timestamped Eventhouse telemetry. KQL is optimized for event-stream and time-series analysis patterns. However, the question instead requires Choose the supported T-SQL environment for warehouse relational querying. because t-SQL matches SQL warehouse object and relational operations.

This action is appropriate when a KQL query scans months of events but the incident occurred only during a one-hour window. Time filtering limits event scans to the relevant investigation scope. However, the question instead requires Push selective date filters earlier and inspect the query plan. because early reduction and plan inspection can avoid unnecessary joins over historical data.

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 Push selective date filters earlier and inspect the query plan. because early reduction and plan inspection can avoid unnecessary joins over historical data.

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 Push selective date filters earlier and inspect the query plan. because early reduction and plan inspection can avoid unnecessary joins over historical data.

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 Choose Import storage mode with a defined refresh schedule. because import stores compressed model data for efficient in-memory querying.

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 Choose Import storage mode with a defined refresh schedule. because import stores compressed model data for efficient in-memory querying.

This action is appropriate when a regulated report must query an eligible live operational source without keeping a large imported snapshot. DirectQuery delegates data queries to the source rather than maintaining a full imported copy. However, the question instead requires Choose Import storage mode with a defined refresh schedule. because import stores compressed model data for efficient in-memory querying.

This action is appropriate when a dimension contains repeated product IDs and its one-to-many relationship cannot be validated. The one-side column must have suitable uniqueness for a one-to-many relationship. However, the question instead requires Build a fact table linked to separate conformed dimension tables. because dimensional star design supports consistent filters and analytic measures.

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 Build a fact table linked to separate conformed dimension tables. because dimensional star design supports consistent filters and analytic measures.

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 Build a fact table linked to separate conformed dimension tables. because dimensional star design supports consistent filters and analytic measures.

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 Prefer well-defined one-direction relationships from dimensions to facts where possible. because controlled filter direction reduces ambiguity and unexpected propagation.

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 Prefer well-defined one-direction relationships from dimensions to facts where possible. because controlled filter direction reduces ambiguity and unexpected propagation.

This action is appropriate when an orders model has both order date and ship date columns but only one Date relationship can be active along that path. Multiple role-playing dates need explicit relationship handling. However, the question instead requires Prefer well-defined one-direction relationships from dimensions to facts where possible. because controlled filter direction reduces ambiguity and unexpected propagation.

This action is appropriate when a revenue report double-counts customers because the fact table was joined directly to a many-to-many campaign mapping. Multi-membership makes naive revenue summation unsafe. However, the question instead requires Introduce a customer-segment bridge table with explicit unique keys. because bridge tables represent valid many-to-many membership without duplicating facts.

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 Introduce a customer-segment bridge table with explicit unique keys. because bridge tables represent valid many-to-many membership without duplicating facts.

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 Introduce a customer-segment bridge table with explicit unique keys. because bridge tables represent valid many-to-many membership without duplicating facts.

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 a DAX VAR to compute the intermediate once and reference it. because variables improve readability and can avoid redundant evaluation.

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 a DAX VAR to compute the intermediate once and reference it. because variables improve readability and can avoid redundant evaluation.

This action is appropriate when a measure must sum unit price times quantity for each visible invoice line. Iterators evaluate an expression per row before aggregation. However, the question instead requires Use a DAX VAR to compute the intermediate once and reference it. because variables improve readability and can avoid redundant evaluation.

This action is appropriate when a measure ignores a category slicer and returns the grand total for every chart bar. Removing filters on a grouping dimension can flatten per-category results. However, the question instead requires Use CALCULATE with a targeted customer filter that preserves required date context. because cALCULATE can modify selected filter dimensions without erasing unrelated slicers.

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 Use CALCULATE with a targeted customer filter that preserves required date context. because cALCULATE can modify selected filter dimensions without erasing unrelated slicers.

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 Use CALCULATE with a targeted customer filter that preserves required date context. because cALCULATE can modify selected filter dimensions without erasing unrelated slicers.

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 Use a marked calendar and a suitable DAX time-intelligence pattern for the fiscal year. because accurate YTD measures depend on an appropriate date dimension and fiscal boundary.

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 Use a marked calendar and a suitable DAX time-intelligence pattern for the fiscal year. because accurate YTD measures depend on an appropriate date dimension and fiscal boundary.

This action is appropriate when a report compares current sales with the same period in the preceding year. Time shifting uses the date context to align comparable periods. However, the question instead requires Use a marked calendar and a suitable DAX time-intelligence pattern for the fiscal year. because accurate YTD measures depend on an appropriate date dimension and fiscal boundary.

This action is appropriate when a report must show each product's revenue alongside the previous product after sorting by sales rank. Window calculations require a deterministic ordering and partition context. However, the question instead requires Use RANKX or supported DAX window ranking with correctly scoped filters. because ranking should be calculated over the appropriate comparison set.

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 RANKX or supported DAX window ranking with correctly scoped filters. because ranking should be calculated over the appropriate comparison set.

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 RANKX or supported DAX window ranking with correctly scoped filters. because ranking should be calculated over the appropriate comparison set.

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 Create a supported calculation group with reusable time-intelligence calculation items. because calculation groups reduce repeated measure patterns by transforming selected 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 Create a supported calculation group with reusable time-intelligence calculation items. because calculation groups reduce repeated measure patterns by transforming selected measures.

This action is appropriate when a calculation item should operate on the currently selected base measure rather than a hard-coded revenue measure. SELECTEDMEASURE makes a calculation reusable across eligible measures. However, the question instead requires Create a supported calculation group with reusable time-intelligence calculation items. because calculation groups reduce repeated measure patterns by transforming selected measures.