ExamworthyExamworthy
Open the appStart free

DP-600 - Implement and Manage Semantic Models - Section 3.3

Write DAX calculations using variables and functions, and implement calculation groups, dynamic format strings, and field parameters.

Write DAX measures using variables, iterator functions, and windowing functions to express complex business logic clearly and efficiently. Implement calculation groups, dynamic format strings, and field parameters to reduce measure proliferation and enable user-driven analysis in reports.

DAX measurescalculation groupsiterators and windowingdynamic format stringsfield parametersDAX variables

Practice question for this objective

Free sampleImplement and Manage Semantic Modelshard

An analytics engineer must let report consumers swap the axis of one shared chart between Product, Region, and Channel through a slicer, and separately must make a single revenue measure render as currency below one million and as a thousands abbreviation above it, with the format chosen at evaluation time. The engineer wants the governed, model-defined feature for each requirement. Which TWO feature-to-requirement pairings are correct? Select TWO.

  • AA calculated column on the date dimension delivers the per-value revenue format, because the column stores the chosen currency or thousands text for each row ready for the visual.
  • BA calculation group with one item per dimension delivers the axis switching, because selecting an item on a slicer rebinds the chart axis to Product, Region, or Channel.
  • CA field parameter listing Product, Region, and Channel delivers the axis switching, because a slicer over the parameter rebinds the single chart's axis to the chosen dimension at view time. Correct
  • DA dynamic format string on the measure delivers the per-value format, because its DAX expression tests the result against the threshold and returns currency or thousands per evaluation. Correct
Field parameters provide governed view-time dimension or measure switching, and dynamic format strings let a measure return its display format per evaluated value. A field parameter creates a model-defined table whose rows reference fields, so a slicer over it rebinds a visual axis to the selected dimension, while a dynamic format string attaches a DAX expression that returns the format string per evaluation so it can branch on the value; a calculation group cannot supply an axis field and a calculated text column cannot vary a numeric measure's format per value.

Why A is wrong: This is tempting because columns can hold formatted text, but a calculated text column stops aggregating as a number and is fixed at refresh, so it cannot vary the numeric format per evaluated value as the threshold rule requires.

Why B is wrong: This is tempting because calculation groups respond to slicers, but they modify how a measure is calculated and cannot place an arbitrary dimension on a chart axis, so they do not perform the grouping-field swap described.

Why C is correct: A field parameter is a model-defined table of fields that a slicer selects from, so choosing one dimension rebinds the shared chart axis to it, which is the governed mechanism for view-time dimension switching.

Why D is correct: A dynamic format string is a DAX expression evaluated alongside the measure value, so it can branch on the magnitude and return the appropriate format per result, travelling with the measure into any visual without extra columns.

See more DP-600 practice questions, answers explained.

More in this domain

Back to all Implement and Manage Semantic Models objectives, or the DP-600 cert hub.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.