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 Put the DAX logic in a semantic model or supported DAX query interface. because model measure expressions are not interchangeable with T-SQL stored procedures.

This action is appropriate when a developer copies a SQL `GROUP BY` query directly into KQL and gets parser errors. Equivalent analytical goals use distinct language operators across engines. However, the question instead requires Put the DAX logic in a semantic model or supported DAX query interface. because model measure expressions are not interchangeable with T-SQL stored procedures.

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 Put the DAX logic in a semantic model or supported DAX query interface. because model measure expressions are not interchangeable with T-SQL stored procedures.

This action is appropriate when a KQL query returns a million rows to the browser when the analyst only wants a top-ten list. Server-side ranking and limiting avoid overwhelming the client with unneeded results. However, the question instead requires Audit join cardinality and validate row counts before interpreting aggregate values. because incorrect relational matching can invalidate sums regardless of runtime speed.

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 Audit join cardinality and validate row counts before interpreting aggregate values. because incorrect relational matching can invalidate sums regardless of runtime speed.

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 Audit join cardinality and validate row counts before interpreting aggregate values. because incorrect relational matching can invalidate sums regardless of runtime speed.

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 Design an approved composite model with supported storage modes. because composite models allow appropriate mixes of model storage behaviors subject to compatibility.

This action is appropriate when a service owner assumes DirectQuery will always be faster than Import on complex high-concurrency dashboards. Remote query latency and source load can dominate interactive performance. However, the question instead requires Design an approved composite model with supported storage modes. because composite models allow appropriate mixes of model storage behaviors subject to compatibility.

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 Design an approved composite model with supported storage modes. because composite models allow appropriate mixes of model storage behaviors subject to compatibility.

This action is appropriate when a finance model has separate local date fields on several facts and needs consistent monthly reporting. A conformed date table makes time slicing consistent across fact tables. However, the question instead requires Prefer stable surrogate or business identifier columns for relationships. because stable keys prevent descriptive edits from breaking joins and filtering.

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 Prefer stable surrogate or business identifier columns for relationships. because stable keys prevent descriptive edits from breaking joins and filtering.

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 Prefer stable surrogate or business identifier columns for relationships. because stable keys prevent descriptive edits from breaking joins and filtering.

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 Verify and create an appropriate model relationship before manipulating DAX context. because missing or invalid relationship paths are a modeling problem, not always a DAX problem.

This action is appropriate when a dimension filters multiple fact tables with circular relationships and visuals return ambiguous results. Ambiguous filter paths can create unpredictable metric interpretation. However, the question instead requires Verify and create an appropriate model relationship before manipulating DAX context. because missing or invalid relationship paths are a modeling problem, not always a DAX problem.

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 Verify and create an appropriate model relationship before manipulating DAX context. because missing or invalid relationship paths are a modeling problem, not always a DAX problem.

This action is appropriate when a model stores the same customer-campaign membership twice in a bridge and calculated participants double. Bridge cardinality must reflect one unique relationship instance per key pair. However, the question instead requires Test scoped bridge relationships and use DAX filtering only where business semantics demand it. because unrestricted bidirectional relationships can yield ambiguous propagation.

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 Test scoped bridge relationships and use DAX filtering only where business semantics demand it. because unrestricted bidirectional relationships can yield ambiguous propagation.

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 Test scoped bridge relationships and use DAX filtering only where business semantics demand it. because unrestricted bidirectional relationships can yield ambiguous propagation.

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 DIVIDE with appropriate alternate-result semantics. because dIVIDE handles denominator-zero scenarios more safely than direct division.

This action is appropriate when a report needs a reusable intermediate set of customers who exceed a threshold for a later calculation. Table-valued variables can make multi-step DAX calculations explicit and testable. However, the question instead requires Use DIVIDE with appropriate alternate-result semantics. because dIVIDE handles denominator-zero scenarios more safely than direct division.

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 DIVIDE with appropriate alternate-result semantics. because dIVIDE handles denominator-zero scenarios more safely than direct division.

This action is appropriate when a DAX model filters product and region but mistakenly removes both when computing percent of total product. Denominator filter scope determines whether percentages match visible business segments. However, the question instead requires Review row context and use an appropriate context transition or row-specific expression. because row context alone does not automatically apply all aggregation filters.

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 Review row context and use an appropriate context transition or row-specific expression. because row context alone does not automatically apply all aggregation filters.

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 Review row context and use an appropriate context transition or row-specific expression. because row context alone does not automatically apply all aggregation filters.

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 Model the approved 4-4-5 fiscal calendar and write period-aware measures. because custom period systems cannot be represented reliably by default calendar-month grouping.

This action is appropriate when a prior-month measure returns blanks because the visual uses a text MonthName column without year context. Period calculations need an unambiguous temporal axis. However, the question instead requires Model the approved 4-4-5 fiscal calendar and write period-aware measures. because custom period systems cannot be represented reliably by default calendar-month grouping.

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 Model the approved 4-4-5 fiscal calendar and write period-aware measures. because custom period systems cannot be represented reliably by default calendar-month grouping.

This action is appropriate when a window function produces unstable results when multiple rows share the same sort value. Stable window results require a defined order within ties. However, the question instead requires Expand the ranking comparison table to the intended eligible products. because rANKX requires the correct peer set, not the current single row.

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 Expand the ranking comparison table to the intended eligible products. because rANKX requires the correct peer set, not the current single row.

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 Expand the ranking comparison table to the intended eligible products. because rANKX requires the correct peer set, not the current single row.

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.