Pass Your Microsoft DP-600 Exam Easy!

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.

This action is appropriate when a measure uses DAX FORMAT to display currency and downstream charts stop treating its result as numeric. FORMAT returns text and can break numeric aggregation and sorting. However, the question instead requires Define a supported dynamic format-string expression for the measure. because dynamic formatting changes presentation without converting the numeric measure to text.

This action is appropriate when a KPI should display a percentage with one decimal without changing its underlying ratio. Formatting expresses numeric semantics while preserving the value. However, the question instead requires Define a supported dynamic format-string expression for the measure. because dynamic formatting changes presentation without converting the numeric measure to text.

This action is appropriate when an organization wants calculation items to show percent growth and currency totals with distinct formats. Calculation groups may require format propagation tailored to the item. However, the question instead requires Define a supported dynamic format-string expression for the measure. because dynamic formatting changes presentation without converting the numeric measure to text.

This action is appropriate when a field parameter references an unapproved sensitive dimension and users can expose it in a visual. Dynamic selection should not introduce new access to confidential attributes. However, the question instead requires Create a supported field parameter that includes the approved dimension fields. because field parameters provide user-controlled selection among model fields.

This action is appropriate when an analyst expects a field parameter to rewrite the underlying data warehouse table. Visual field flexibility is not an ETL operation. However, the question instead requires Create a supported field parameter that includes the approved dimension fields. because field parameters provide user-controlled selection among model fields.

This action is appropriate when a user needs to toggle between revenue, profit and quantity in one visual. Measure parameters can switch the metric without duplicating whole report pages. However, the question instead requires Create a supported field parameter that includes the approved dimension fields. because field parameters provide user-controlled selection among model fields.

This action is appropriate when a model grows beyond standard storage assumptions and needs enterprise-scale capacity features. Large storage configurations can support eligible enterprise-scale models when properly provisioned. However, the question instead requires Build an eligible composite model with supported Import and DirectQuery storage modes. because mixed storage models allow different freshness and performance tradeoffs per table.

This action is appropriate when a team enables large model format and assumes it automatically fixes inefficient DAX. Storage capacity does not replace query and model optimization. However, the question instead requires Build an eligible composite model with supported Import and DirectQuery storage modes. because mixed storage models allow different freshness and performance tradeoffs per table.

This action is appropriate when an architect mixes Direct Lake on SQL tables with unsupported additional storage modes in one model. Direct Lake on SQL analytics endpoint mode has restrictions not shared by every composite variant. However, the question instead requires Build an eligible composite model with supported Import and DirectQuery storage modes. because mixed storage models allow different freshness and performance tradeoffs per table.

This action is appropriate when a report loads quickly in Desktop but is slow under production capacity concurrency. Production concurrency can expose limits not seen in isolated development testing. However, the question instead requires Use Power BI Performance Analyzer to inspect the slow visual's query timing. because visual-level timings help isolate the bottleneck before modifying unrelated model components.

This action is appropriate when an analyst adds a complex custom visual and total page render time rises despite unchanged measures. Slow pages can be caused by client rendering rather than semantic query execution alone. However, the question instead requires Use Power BI Performance Analyzer to inspect the slow visual's query timing. because visual-level timings help isolate the bottleneck before modifying unrelated model components.

This action is appropriate when a dashboard becomes slow only when a specific slicer produces many high-cardinality groups. Visual cardinality can multiply both rendering and model-query work. However, the question instead requires Use Power BI Performance Analyzer to inspect the slow visual's query timing. because visual-level timings help isolate the bottleneck before modifying unrelated model components.

This action is appropriate when a margin KPI calculates row-wise ratio then sums it, causing numerical inconsistency and high query work. Correct aggregate semantics can also eliminate excessive per-row iteration. However, the question instead requires Rewrite CALCULATE filters to use efficient column predicates where semantics permit. because simpler native filter expressions can lower Formula Engine work.

This action is appropriate when a DAX formula recomputes the same large table expression several times. Variables can reduce repeated evaluation and make performance investigation easier. However, the question instead requires Rewrite CALCULATE filters to use efficient column predicates where semantics permit. because simpler native filter expressions can lower Formula Engine work.

This action is appropriate when a report uses `FORMAT` on every numeric measure and sorting and charts behave as text. Text conversion compromises numeric sorting and may increase model processing overhead. However, the question instead requires Rewrite CALCULATE filters to use efficient column predicates where semantics permit. because simpler native filter expressions can lower Formula Engine work.

This action is appropriate when a Fabric capacity has Direct Lake table sizes above guardrail thresholds and fallback occurs. Excessive file counts or row groups can make in-memory Direct Lake queries ineligible. However, the question instead requires Inspect SQL endpoint RLS and DirectQuery fallback behavior for the affected table. because sQL-endpoint row restrictions can force DirectQuery fallback in this Direct Lake variant.

This action is appropriate when a team disables fallback while keeping SQL security constraints that need it, and visuals fail. Disabling the SQL mode's fallback converts a slow fallback path into query errors. However, the question instead requires Inspect SQL endpoint RLS and DirectQuery fallback behavior for the affected table. because sQL-endpoint row restrictions can force DirectQuery fallback in this Direct Lake variant.

This action is appropriate when a semantic model references a nonmaterialized SQL view and reports are slower than Delta-table queries. Views in Direct Lake on SQL can require query fallback instead of reading Delta columns directly. However, the question instead requires Inspect SQL endpoint RLS and DirectQuery fallback behavior for the affected table. because sQL-endpoint row restrictions can force DirectQuery fallback in this Direct Lake variant.

This action is appropriate when a model requires SQL analytics endpoint security semantics and may accept slower queries when restricted. This variant checks SQL-endpoint metadata and may execute DirectQuery for restricted paths. However, the question instead requires Select Direct Lake on OneLake where the source and capacity meet requirements. because the OneLake variant uses OneLake APIs and is not coupled with the SQL endpoint.

This action is appropriate when a team expects Direct Lake on OneLake to fall back to DirectQuery when its guardrails are exceeded. Unsupported direct lake execution fails rather than silently switching to SQL in the OneLake variant. However, the question instead requires Select Direct Lake on OneLake where the source and capacity meet requirements. because the OneLake variant uses OneLake APIs and is not coupled with the SQL endpoint.

This action is appropriate when a designer wants a single Direct Lake model to span eligible Delta sources rather than only one SQL endpoint. OneLake-based Direct Lake can use eligible Delta tables from multiple Fabric sources. However, the question instead requires Select Direct Lake on OneLake where the source and capacity meet requirements. because the OneLake variant uses OneLake APIs and is not coupled with the SQL endpoint.

This action is appropriate when a Direct Lake model has automatic updates disabled but business users expect newly committed Delta data immediately. Source commits alone do not override a disabled model framing policy. However, the question instead requires Check model framing or automatic updates and trigger a supported refresh when needed. because model framing determines which Delta table state the semantic model can query.

This action is appropriate when a model adds a table through XMLA metadata and its report returns an unframed-table error. New Direct Lake tables need a valid framing state before queries. However, the question instead requires Check model framing or automatic updates and trigger a supported refresh when needed. because model framing determines which Delta table state the semantic model can query.

This action is appropriate when a team confuses Direct Lake semantic refresh with a full copy of all tables into Import storage. Framing tracks eligible Delta table snapshots while columns are read on demand. However, the question instead requires Check model framing or automatic updates and trigger a supported refresh when needed. because model framing determines which Delta table state the semantic model can query.

This action is appropriate when an incremental refresh policy produces duplicate data because partitions overlap at the time boundary. Nonoverlapping partition predicates prevent duplicate boundary rows. However, the question instead requires Configure supported incremental refresh with RangeStart and RangeEnd partitions. because incremental processing reduces refresh work to changed time ranges.

This action is appropriate when a model defines incremental refresh but the source query does not fold the date predicate. Without effective folding, every partition may rescan full source data. However, the question instead requires Configure supported incremental refresh with RangeStart and RangeEnd partitions. because incremental processing reduces refresh work to changed time ranges.

This action is appropriate when late-arriving corrections change older partitions beyond the refresh window. An incremental window only captures changes in the ranges it processes. However, the question instead requires Configure supported incremental refresh with RangeStart and RangeEnd partitions. because incremental processing reduces refresh work to changed time ranges.

This action is appropriate when a model creates hundreds of calculated columns for values that can be computed in source SQL. Model size and refresh work may fall when unnecessary calculated columns are removed. However, the question instead requires Remove unneeded high-cardinality columns from the model. because wide high-cardinality data can consume memory without adding analytical value.

This action is appropriate when a model uses bidirectional filters on every relationship and reports contain ambiguous results. Relationship design affects both query work and analytical correctness. However, the question instead requires Remove unneeded high-cardinality columns from the model. because wide high-cardinality data can consume memory without adding analytical value.

This action is appropriate when a fact table includes a verbose description repeated across millions of rows. Dimensional normalization can reduce repeated text and improve compression. However, the question instead requires Remove unneeded high-cardinality columns from the model. because wide high-cardinality data can consume memory without adding analytical value.