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 Define an appropriate format-string expression for the calculation item. because reusable calculations must preserve the meaning and display of their results.

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 Define an appropriate format-string expression for the calculation item. because reusable calculations must preserve the meaning and display of their results.

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 Define an appropriate format-string expression for the calculation item. because reusable calculations must preserve the meaning and display of their results.

This action is appropriate when a report's currency format changes but exported numeric values must remain suitable for calculations. Display formatting can vary independently of the stored number. However, the question instead requires Configure calculation-item format strings based on the metric semantics. because calculation groups may require format propagation tailored to the item.

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 Configure calculation-item format strings based on the metric semantics. because calculation groups may require format propagation tailored to the item.

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 Configure calculation-item format strings based on the metric semantics. because calculation groups may require format propagation tailored to the item.

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 Explain that field parameters modify semantic or visual field selection, not source data. because visual field flexibility is not an ETL operation.

This action is appropriate when a field parameter is renamed and bookmarked report states no longer restore correctly. Field-parameter changes can affect persisted report state references. However, the question instead requires Explain that field parameters modify semantic or visual field selection, not source data. because visual field flexibility is not an ETL operation.

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 Explain that field parameters modify semantic or visual field selection, not source data. because visual field flexibility is not an ETL operation.

This action is appropriate when a composite model builds a relationship across Import and DirectQuery sources and totals unexpectedly change. Composite model query plans and relationship assumptions can affect correctness and performance. However, the question instead requires Validate storage-mode compatibility before designing the composite structure. because direct Lake on SQL analytics endpoint mode has restrictions not shared by every composite variant.

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 Validate storage-mode compatibility before designing the composite structure. because direct Lake on SQL analytics endpoint mode has restrictions not shared by every composite variant.

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 Validate storage-mode compatibility before designing the composite structure. because direct Lake on SQL analytics endpoint mode has restrictions not shared by every composite variant.

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 Benchmark the visual rendering cost separately from DAX query time. because slow pages can be caused by client rendering rather than semantic query execution alone.

This action is appropriate when a page has dozens of visuals issuing redundant queries every time a slicer changes. Reducing redundant query fan-out can improve end-user responsiveness. However, the question instead requires Benchmark the visual rendering cost separately from DAX query time. because slow pages can be caused by client rendering rather than semantic query execution alone.

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 Benchmark the visual rendering cost separately from DAX query time. because slow pages can be caused by client rendering rather than semantic query execution alone.

This action is appropriate when a visual displays every store's percentage as 100% and a measure has an overbroad ALL call. DAX performance tuning must preserve filter semantics rather than only minimize execution time. However, the question instead requires Use native numeric measures with dynamic format strings or model formats. because text conversion compromises numeric sorting and may increase model processing overhead.

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 Use native numeric measures with dynamic format strings or model formats. because text conversion compromises numeric sorting and may increase model processing overhead.

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 Use native numeric measures with dynamic format strings or model formats. because text conversion compromises numeric sorting and may increase model processing overhead.

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 Reevaluate DirectLakeBehavior settings and remove the incompatible dependency or reenable supported fallback. because disabling the SQL mode's fallback converts a slow fallback path into query errors.

This action is appropriate when a report owner cannot explain whether Direct Lake used in-memory columns or SQL fallback. Mode diagnostics identify the actual query path instead of relying on model labels. However, the question instead requires Reevaluate DirectLakeBehavior settings and remove the incompatible dependency or reenable supported fallback. because disabling the SQL mode's fallback converts a slow fallback path into query errors.

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 Reevaluate DirectLakeBehavior settings and remove the incompatible dependency or reenable supported fallback. because disabling the SQL mode's fallback converts a slow fallback path into query errors.

This action is appropriate when an analyst assumes SQL endpoint row security automatically protects a Direct Lake on OneLake model. OneLake variant authorization does not consult SQL-endpoint row-level rules. However, the question instead requires Check Direct Lake on OneLake source integration and permission requirements. because oneLake-based Direct Lake can use eligible Delta tables from multiple Fabric sources.

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 Check Direct Lake on OneLake source integration and permission requirements. because oneLake-based Direct Lake can use eligible Delta tables from multiple Fabric sources.

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 Check Direct Lake on OneLake source integration and permission requirements. because oneLake-based Direct Lake can use eligible Delta tables from multiple Fabric sources.

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 Perform an appropriate model refresh after adding the table definition. because new Direct Lake tables need a valid framing state before queries.

This action is appropriate when a data steward modifies OneLake security roles and a Direct Lake model still evaluates old access assumptions. Security and table metadata changes can require recalculation of the model's effective access state. However, the question instead requires Perform an appropriate model refresh after adding the table definition. because new Direct Lake tables need a valid framing state before queries.

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 Perform an appropriate model refresh after adding the table definition. because new Direct Lake tables need a valid framing state before queries.

This action is appropriate when a published model's refresh policy is configured but only historical partitions are being processed manually. Model policy configuration alone does not guarantee routine refresh operations. However, the question instead requires Extend the refresh policy or schedule a controlled historical reprocessing operation. because an incremental window only captures changes in the ranges it processes.

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 Extend the refresh policy or schedule a controlled historical reprocessing operation. because an incremental window only captures changes in the ranges it processes.

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 Extend the refresh policy or schedule a controlled historical reprocessing operation. because an incremental window only captures changes in the ranges it processes.

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 Simplify to a clear star schema with controlled filter directions. because relationship design affects both query work and analytical correctness.

This action is appropriate when a model consumes high memory during refresh and the team assumes adding a second report page will solve it. Data model memory pressure cannot be fixed by a cosmetic change to report layout. However, the question instead requires Simplify to a clear star schema with controlled filter directions. because relationship design affects both query work and analytical correctness.

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 Simplify to a clear star schema with controlled filter directions. because relationship design affects both query work and analytical correctness.