Pass Your Microsoft DP-600 Exam Easy!

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 Review calculation group precedence and test combined selections. because precedence controls how multiple calculation-item expressions are composed.

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 Review calculation group precedence and test combined selections. because precedence controls how multiple calculation-item expressions are composed.

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 Review calculation group precedence and test combined selections. because precedence controls how multiple calculation-item expressions are composed.

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 Apply the correct percentage measure format rather than multiplying stored values arbitrarily. because formatting expresses numeric semantics while preserving the value.

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 Apply the correct percentage measure format rather than multiplying stored values arbitrarily. because formatting expresses numeric semantics while preserving the value.

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 Apply the correct percentage measure format rather than multiplying stored values arbitrarily. because formatting expresses numeric semantics while preserving the value.

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 Restrict the field parameter to fields authorized for the target audience. because dynamic selection should not introduce new access to confidential attributes.

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 Restrict the field parameter to fields authorized for the target audience. because dynamic selection should not introduce new access to confidential attributes.

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 Restrict the field parameter to fields authorized for the target audience. because dynamic selection should not introduce new access to confidential attributes.

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 Profile measures and relationships independently of model storage settings. because storage capacity does not replace query and model optimization.

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 Profile measures and relationships independently of model storage settings. because storage capacity does not replace query and model optimization.

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 Profile measures and relationships independently of model storage settings. because storage capacity does not replace query and model optimization.

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 Compare capacity utilization and simultaneous model-query load during the slowdown. because production concurrency can expose limits not seen in isolated development testing.

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 Compare capacity utilization and simultaneous model-query load during the slowdown. because production concurrency can expose limits not seen in isolated development testing.

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 Compare capacity utilization and simultaneous model-query load during the slowdown. because production concurrency can expose limits not seen in isolated development testing.

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 Cache an intermediate expression with VAR and inspect the resulting execution plan. because variables can reduce repeated evaluation and make performance investigation easier.

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 Cache an intermediate expression with VAR and inspect the resulting execution plan. because variables can reduce repeated evaluation and make performance investigation easier.

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 Cache an intermediate expression with VAR and inspect the resulting execution plan. because variables can reduce repeated evaluation and make performance investigation easier.

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 Review capacity guardrails and optimize Delta files or scale capacity as warranted. because excessive file counts or row groups can make in-memory Direct Lake queries ineligible.

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 Review capacity guardrails and optimize Delta files or scale capacity as warranted. because excessive file counts or row groups can make in-memory Direct Lake queries ineligible.

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 Review capacity guardrails and optimize Delta files or scale capacity as warranted. because excessive file counts or row groups can make in-memory Direct Lake queries ineligible.

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 Explain that Direct Lake on OneLake does not support DirectQuery fallback. because unsupported direct lake execution fails rather than silently switching to SQL in the OneLake variant.

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 Explain that Direct Lake on OneLake does not support DirectQuery fallback. because unsupported direct lake execution fails rather than silently switching to SQL in the OneLake variant.

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 Explain that Direct Lake on OneLake does not support DirectQuery fallback. because unsupported direct lake execution fails rather than silently switching to SQL in the OneLake variant.

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 Configure approved automatic updates or a refresh trigger aligned with the freshness SLA. because source commits alone do not override a disabled model framing policy.

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 Configure approved automatic updates or a refresh trigger aligned with the freshness SLA. because source commits alone do not override a disabled model framing policy.

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 Configure approved automatic updates or a refresh trigger aligned with the freshness SLA. because source commits alone do not override a disabled model framing policy.

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 Inspect query folding and push eligible date filters to the source. because without effective folding, every partition may rescan full source data.

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 Inspect query folding and push eligible date filters to the source. because without effective folding, every partition may rescan full source data.

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 Inspect query folding and push eligible date filters to the source. because without effective folding, every partition may rescan full source data.

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 Consider source-side materialization or reusable measures based on intended semantics. because model size and refresh work may fall when unnecessary calculated columns are removed.

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 Consider source-side materialization or reusable measures based on intended semantics. because model size and refresh work may fall when unnecessary calculated columns are removed.

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 Consider source-side materialization or reusable measures based on intended semantics. because model size and refresh work may fall when unnecessary calculated columns are removed.