Pass Your Microsoft DP-600 Exam Easy!

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 Use a supported model-editing workflow and verify calculation-group prerequisites. because calculation group authoring depends on model capabilities and supported tools.

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 a supported model-editing workflow and verify calculation-group prerequisites. because calculation group authoring depends on model capabilities and supported tools.

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 Use a supported model-editing workflow and verify calculation-group prerequisites. because calculation group authoring depends on model capabilities and supported tools.

This action is appropriate when the same revenue measure must show euros for one currency selection and dollars for another. Dynamic formatting changes presentation without converting the numeric measure to text. However, the question instead requires Keep measures numeric and use semantic model formatting metadata. because display formatting can vary independently of the stored number.

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 Keep measures numeric and use semantic model formatting metadata. because display formatting can vary independently of the stored number.

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 Keep measures numeric and use semantic model formatting metadata. because display formatting can vary independently of the stored number.

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 Test dependent visuals, slicers and bookmarks when modifying parameter definitions. because field-parameter changes can affect persisted report state references.

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 Test dependent visuals, slicers and bookmarks when modifying parameter definitions. because field-parameter changes can affect persisted report state references.

This action is appropriate when a report consumer wants to switch a chart axis between product, region and channel. Field parameters provide user-controlled selection among model fields. However, the question instead requires Test dependent visuals, slicers and bookmarks when modifying parameter definitions. because field-parameter changes can affect persisted report state references.

This action is appropriate when a semantic model must combine a small imported budget table with a live sales source. Mixed storage models allow different freshness and performance tradeoffs per table. However, the question instead requires Review cross-source relationship behavior and test query semantics for the chosen modes. because composite model query plans and relationship assumptions can affect correctness and performance.

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 Review cross-source relationship behavior and test query semantics for the chosen modes. because composite model query plans and relationship assumptions can affect correctness and performance.

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 Review cross-source relationship behavior and test query semantics for the chosen modes. because composite model query plans and relationship assumptions can affect correctness and performance.

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 Simplify visual interactions and avoid unnecessary duplicated calculations. because reducing redundant query fan-out can improve end-user responsiveness.

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 Simplify visual interactions and avoid unnecessary duplicated calculations. because reducing redundant query fan-out can improve end-user responsiveness.

This action is appropriate when a report contains one visual that loads much more slowly than adjacent visuals. Visual-level timings help isolate the bottleneck before modifying unrelated model components. However, the question instead requires Simplify visual interactions and avoid unnecessary duplicated calculations. because reducing redundant query fan-out can improve end-user responsiveness.

This action is appropriate when a DAX measure iterates a billion-row fact using FILTER even though a simple column predicate would suffice. Simpler native filter expressions can lower Formula Engine work. However, the question instead requires Correct the denominator filter scope using the intended peer set. because dAX performance tuning must preserve filter semantics rather than only minimize execution time.

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 Correct the denominator filter scope using the intended peer set. because dAX performance tuning must preserve filter semantics rather than only minimize execution time.

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 Correct the denominator filter scope using the intended peer set. because dAX performance tuning must preserve filter semantics rather than only minimize execution time.

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 supported Direct Lake query diagnostics such as TABLETRAITS fallback information. because mode diagnostics identify the actual query path instead of relying on model labels.

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 supported Direct Lake query diagnostics such as TABLETRAITS fallback information. because mode diagnostics identify the actual query path instead of relying on model labels.

This action is appropriate when a Direct Lake on SQL model unexpectedly switches slow report queries to SQL for a secured source table. SQL-endpoint row restrictions can force DirectQuery fallback in this Direct Lake variant. However, the question instead requires Inspect supported Direct Lake query diagnostics such as TABLETRAITS fallback information. because mode diagnostics identify the actual query path instead of relying on model labels.

This action is appropriate when a new semantic model needs direct Delta-column access with OneLake security but no SQL endpoint dependency. The OneLake variant uses OneLake APIs and is not coupled with the SQL endpoint. However, the question instead requires Configure and verify OneLake security or semantic-model RLS for that model. because oneLake variant authorization does not consult SQL-endpoint row-level rules.

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 Configure and verify OneLake security or semantic-model RLS for that model. because oneLake variant authorization does not consult SQL-endpoint row-level rules.

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 Configure and verify OneLake security or semantic-model RLS for that model. because oneLake variant authorization does not consult SQL-endpoint row-level rules.

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 Refresh affected models and revalidate effective security as required by the integration. because security and table metadata changes can require recalculation of the model's effective access state.

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 Refresh affected models and revalidate effective security as required by the integration. because security and table metadata changes can require recalculation of the model's effective access state.

This action is appropriate when a Direct Lake report still shows prior values after upstream Delta rows changed. Model framing determines which Delta table state the semantic model can query. However, the question instead requires Refresh affected models and revalidate effective security as required by the integration. because security and table metadata changes can require recalculation of the model's effective access state.

This action is appropriate when a ten-year Import semantic model takes hours to reload even though only the most recent month changes. Incremental processing reduces refresh work to changed time ranges. However, the question instead requires Verify service-side policy application and scheduled incremental refresh execution. because model policy configuration alone does not guarantee routine refresh operations.

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 Verify service-side policy application and scheduled incremental refresh execution. because model policy configuration alone does not guarantee routine refresh operations.

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 Verify service-side policy application and scheduled incremental refresh execution. because model policy configuration alone does not guarantee routine refresh operations.

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 Profile model tables, cardinality and capacity usage before sizing or redesigning. because data model memory pressure cannot be fixed by a cosmetic change to report layout.

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 Profile model tables, cardinality and capacity usage before sizing or redesigning. because data model memory pressure cannot be fixed by a cosmetic change to report layout.

This action is appropriate when a semantic model stores transaction GUIDs in multiple high-cardinality string columns that reports never use. Wide high-cardinality data can consume memory without adding analytical value. However, the question instead requires Profile model tables, cardinality and capacity usage before sizing or redesigning. because data model memory pressure cannot be fixed by a cosmetic change to report layout.