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 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.

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 Replace text conversion with dynamic format strings when suitable. because fORMAT returns text and can break numeric aggregation and sorting.

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 Replace text conversion with dynamic format strings when suitable. because fORMAT returns text and can break numeric aggregation and sorting.

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 Replace text conversion with dynamic format strings when suitable. because fORMAT returns text and can break numeric aggregation and sorting.

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 Use a field parameter containing the intended measures. because measure parameters can switch the metric without duplicating whole report pages.

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 Use a field parameter containing the intended measures. because measure parameters can switch the metric without duplicating whole report pages.

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 Use a field parameter containing the intended measures. because measure parameters can switch the metric without duplicating whole report pages.

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 Evaluate large semantic model storage format and capacity prerequisites. because large storage configurations can support eligible enterprise-scale models when properly provisioned.

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 Evaluate large semantic model storage format and capacity prerequisites. because large storage configurations can support eligible enterprise-scale models when properly provisioned.

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 Evaluate large semantic model storage format and capacity prerequisites. because large storage configurations can support eligible enterprise-scale models when properly provisioned.

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 Reduce unnecessary visual detail and inspect the query produced under that filter. because visual cardinality can multiply both rendering and model-query work.

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 Reduce unnecessary visual detail and inspect the query produced under that filter. because visual cardinality can multiply both rendering and model-query work.

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 Reduce unnecessary visual detail and inspect the query produced under that filter. because visual cardinality can multiply both rendering and model-query work.

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 Replace the design with ratio of appropriately aggregated numerator and denominator. because correct aggregate semantics can also eliminate excessive per-row iteration.

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 Replace the design with ratio of appropriately aggregated numerator and denominator. because correct aggregate semantics can also eliminate excessive per-row iteration.

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 Replace the design with ratio of appropriately aggregated numerator and denominator. because correct aggregate semantics can also eliminate excessive per-row iteration.

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 Evaluate materializing the view as a Delta table or accepting DirectQuery fallback. because views in Direct Lake on SQL can require query fallback instead of reading Delta columns directly.

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 Evaluate materializing the view as a Delta table or accepting DirectQuery fallback. because views in Direct Lake on SQL can require query fallback instead of reading Delta columns directly.

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 Evaluate materializing the view as a Delta table or accepting DirectQuery fallback. because views in Direct Lake on SQL can require query fallback instead of reading Delta columns directly.

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 Evaluate Direct Lake on SQL analytics endpoints with documented fallback behavior. because this variant checks SQL-endpoint metadata and may execute DirectQuery for restricted paths.

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 Evaluate Direct Lake on SQL analytics endpoints with documented fallback behavior. because this variant checks SQL-endpoint metadata and may execute DirectQuery for restricted paths.

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 Evaluate Direct Lake on SQL analytics endpoints with documented fallback behavior. because this variant checks SQL-endpoint metadata and may execute DirectQuery for restricted paths.

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 Explain that Direct Lake refresh typically updates framing metadata rather than importing all source rows. because framing tracks eligible Delta table snapshots while columns are read on demand.

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 Explain that Direct Lake refresh typically updates framing metadata rather than importing all source rows. because framing tracks eligible Delta table snapshots while columns are read on demand.

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 Explain that Direct Lake refresh typically updates framing metadata rather than importing all source rows. because framing tracks eligible Delta table snapshots while columns are read on demand.

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 Use a consistent inclusive lower and exclusive upper bound on partition filters. because nonoverlapping partition predicates prevent duplicate boundary rows.

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 Use a consistent inclusive lower and exclusive upper bound on partition filters. because nonoverlapping partition predicates prevent duplicate boundary rows.

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 Use a consistent inclusive lower and exclusive upper bound on partition filters. because nonoverlapping partition predicates prevent duplicate boundary rows.

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 Move stable descriptions to an appropriate dimension when relationships support it. because dimensional normalization can reduce repeated text and improve compression.

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 Move stable descriptions to an appropriate dimension when relationships support it. because dimensional normalization can reduce repeated text and improve compression.

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 Move stable descriptions to an appropriate dimension when relationships support it. because dimensional normalization can reduce repeated text and improve compression.