Pass Your Microsoft DP-600 Exam Easy!

This action is appropriate when an incident team needs subsecond exploratory filtering over timestamped Eventhouse telemetry. KQL is optimized for event-stream and time-series analysis patterns. However, the question instead requires Translate the aggregation to KQL `summarize` syntax for Eventhouse. because equivalent analytical goals use distinct language operators across engines.

This action is appropriate when a Power BI analyst wants a KPI evaluated under report slicers and semantic model relationships. DAX understands model filter context and report interactions. However, the question instead requires Translate the aggregation to KQL `summarize` syntax for Eventhouse. because equivalent analytical goals use distinct language operators across engines.

This action is appropriate when an engineer needs transactional SQL joins and view definitions in a Fabric warehouse. T-SQL matches SQL warehouse object and relational operations. However, the question instead requires Translate the aggregation to KQL `summarize` syntax for Eventhouse. because equivalent analytical goals use distinct language operators across engines.

This action is appropriate when a SQL query joins three large tables and times out despite needing only last-day records. Early reduction and plan inspection can avoid unnecessary joins over historical data. However, the question instead requires Add a correct `top` or aggregation limit to the query. because server-side ranking and limiting avoid overwhelming the client with unneeded results.

This action is appropriate when a KQL query scans months of events but the incident occurred only during a one-hour window. Time filtering limits event scans to the relevant investigation scope. However, the question instead requires Add a correct `top` or aggregation limit to the query. because server-side ranking and limiting avoid overwhelming the client with unneeded results.

This action is appropriate when a DAX report visual is slow and its measure repeatedly iterates the full fact table for each cell. Reducing unnecessary repeated iterators can improve model query execution. However, the question instead requires Add a correct `top` or aggregation limit to the query. because server-side ranking and limiting avoid overwhelming the client with unneeded results.

This action is appropriate when a regulated report must query an eligible live operational source without keeping a large imported snapshot. DirectQuery delegates data queries to the source rather than maintaining a full imported copy. However, the question instead requires Benchmark query patterns and source capacity before choosing DirectQuery over Import. because remote query latency and source load can dominate interactive performance.

This action is appropriate when a Fabric analytics model targets compatible OneLake Delta tables and requires low latency without ordinary Import processing. Direct Lake loads Delta-backed columns into memory on demand rather than using conventional Import refresh. However, the question instead requires Benchmark query patterns and source capacity before choosing DirectQuery over Import. because remote query latency and source load can dominate interactive performance.

This action is appropriate when a small published dataset needs fastest interactive model queries and can tolerate scheduled refresh latency. Import stores compressed model data for efficient in-memory querying. However, the question instead requires Benchmark query patterns and source capacity before choosing DirectQuery over Import. because remote query latency and source load can dominate interactive performance.

This action is appropriate when a product sales semantic model must support date, customer and product slicing over transactions. Dimensional star design supports consistent filters and analytic measures. However, the question instead requires Introduce a shared well-formed date dimension with appropriate relationships. because a conformed date table makes time slicing consistent across fact tables.

This action is appropriate when a dimension contains repeated product IDs and its one-to-many relationship cannot be validated. The one-side column must have suitable uniqueness for a one-to-many relationship. However, the question instead requires Introduce a shared well-formed date dimension with appropriate relationships. because a conformed date table makes time slicing consistent across fact tables.

This action is appropriate when a model mixes one-row-per-order and one-row-per-line totals in one fact table. Mixed grains cause repeated subtotals and confusing model relationships. However, the question instead requires Introduce a shared well-formed date dimension with appropriate relationships. because a conformed date table makes time slicing consistent across fact tables.

This action is appropriate when an orders model has both order date and ship date columns but only one Date relationship can be active along that path. Multiple role-playing dates need explicit relationship handling. However, the question instead requires Simplify relationship paths using a star schema or explicit bridge design. because ambiguous filter paths can create unpredictable metric interpretation.

This action is appropriate when a revenue measure should use the inactive shipment-date relationship for one report page. Explicit activation changes the relationship path only for the intended calculation. However, the question instead requires Simplify relationship paths using a star schema or explicit bridge design. because ambiguous filter paths can create unpredictable metric interpretation.

This action is appropriate when a customer dimension should filter its sales fact but the model uses ambiguous bidirectional relationships everywhere. Controlled filter direction reduces ambiguity and unexpected propagation. However, the question instead requires Simplify relationship paths using a star schema or explicit bridge design. because ambiguous filter paths can create unpredictable metric interpretation.

This action is appropriate when a customer can belong to several marketing segments and each segment contains many customers. Bridge tables represent valid many-to-many membership without duplicating facts. However, the question instead requires Enforce unique membership pairs and validate bridge grain. because bridge cardinality must reflect one unique relationship instance per key pair.

This action is appropriate when a revenue report double-counts customers because the fact table was joined directly to a many-to-many campaign mapping. Multi-membership makes naive revenue summation unsafe. However, the question instead requires Enforce unique membership pairs and validate bridge grain. because bridge cardinality must reflect one unique relationship instance per key pair.

This action is appropriate when two facts at different grains share a many-to-many identifier and a direct relationship causes ambiguous paths. Fact-to-fact many-to-many joins often duplicate values and complicate filtering. However, the question instead requires Enforce unique membership pairs and validate bridge grain. because bridge cardinality must reflect one unique relationship instance per key pair.

This action is appropriate when a measure must sum unit price times quantity for each visible invoice line. Iterators evaluate an expression per row before aggregation. However, the question instead requires Use a DAX VAR holding an appropriate filtered table expression. because table-valued variables can make multi-step DAX calculations explicit and testable.

This action is appropriate when a margin percentage is computed as `SUM(Margin / Revenue)` and overstates results for differently sized transactions. Ratio of totals is usually different from sum of per-row ratios. However, the question instead requires Use a DAX VAR holding an appropriate filtered table expression. because table-valued variables can make multi-step DAX calculations explicit and testable.

This action is appropriate when a measure recalculates an expensive intermediate total three times in one DAX expression. Variables improve readability and can avoid redundant evaluation. However, the question instead requires Use a DAX VAR holding an appropriate filtered table expression. because table-valued variables can make multi-step DAX calculations explicit and testable.

This action is appropriate when a KPI must return sales for premium customers while respecting a separate date slicer. CALCULATE can modify selected filter dimensions without erasing unrelated slicers. However, the question instead requires Remove only the intended product filter while retaining region context. because denominator filter scope determines whether percentages match visible business segments.

This action is appropriate when a measure ignores a category slicer and returns the grand total for every chart bar. Removing filters on a grouping dimension can flatten per-category results. However, the question instead requires Remove only the intended product filter while retaining region context. because denominator filter scope determines whether percentages match visible business segments.

This action is appropriate when an analyst needs sales only for customers with lifetime orders above a chosen threshold. Table filters support set-based eligibility before aggregate evaluation. However, the question instead requires Remove only the intended product filter while retaining region context. because denominator filter scope determines whether percentages match visible business segments.

This action is appropriate when a report compares current sales with the same period in the preceding year. Time shifting uses the date context to align comparable periods. However, the question instead requires Use an actual date column and complete year-month context for time shifting. because period calculations need an unambiguous temporal axis.

This action is appropriate when a model's date dimension omits holidays and dates with no transactions, breaking calculations. Time-intelligence calculations expect a complete and appropriately typed calendar. However, the question instead requires Use an actual date column and complete year-month context for time shifting. because period calculations need an unambiguous temporal axis.

This action is appropriate when executives need year-to-date sales respecting the official fiscal calendar. Accurate YTD measures depend on an appropriate date dimension and fiscal boundary. However, the question instead requires Use an actual date column and complete year-month context for time shifting. because period calculations need an unambiguous temporal axis.

This action is appropriate when a sales leader wants to rank stores by revenue within the currently selected region. Ranking should be calculated over the appropriate comparison set. However, the question instead requires Add a deterministic tie-breaker or explicit match-by columns. because stable window results require a defined order within ties.

This action is appropriate when a report must show each product's revenue alongside the previous product after sorting by sales rank. Window calculations require a deterministic ordering and partition context. However, the question instead requires Add a deterministic tie-breaker or explicit match-by columns. because stable window results require a defined order within ties.

This action is appropriate when an analyst wants a running total across selected months without including hidden years. Running totals must respect intended report selection boundaries. However, the question instead requires Add a deterministic tie-breaker or explicit match-by columns. because stable window results require a defined order within ties.

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.