PL-300 - Model the Data (35% of the exam) - Section 2.2

Create model calculations using DAX including measures, calculated columns, and time intelligence.

Write DAX measures and calculated columns, and use CALCULATE to modify filter context for comparisons such as year-over-year growth via time intelligence functions. Distinguish row context from filter context to predict how an expression evaluates inside a table versus a visual.

DAX measurescalculated columnsCALCULATE functiontime intelligence functionsrow context vs filter context

Practice question for this objective

Free sampleModel the Dataeasy

You are writing a measure that should sum Sales[Sales Amount] but only for rows where Product[Color] equals Blue, regardless of any color filter the visual applies. Which DAX function evaluates an expression in a modified filter context?

AWrap the SUM in CALCULATE and pass Product[Color] = "Blue" as the filter argument. Correct
BWrap the SUM in SUMX and pass Product[Color] = "Blue" as the filter argument.
CWrap the SUM in SUMMARIZE and pass Product[Color] = "Blue" as the filter argument.
DWrap the SUM in RELATED and pass Product[Color] = "Blue" as the filter argument.

CALCULATE is the DAX function that evaluates an expression in a modified filter context. CALCULATE evaluates an expression in a modified filter context. Passing Product[Color] = "Blue" as a Boolean filter argument adds a filter to the Product[Color] column or overwrites any existing filter on that column, producing a Blue-only sum.

Why A is correct: Correct. CALCULATE evaluates an expression in a modified filter context.

Why B is wrong: SUMX iterates a table and evaluates an expression per row; it does not accept a Boolean filter argument that modifies filter context.

Why C is wrong: SUMMARIZE groups a table by columns and returns a table; it is not the filter-context modifier for a scalar expression.

Why D is wrong: RELATED follows a relationship from a row context to fetch a single value; it does not modify filter context for an aggregation.

See more PL-300 practice questions, answers explained.

Exam traps in Model the Data

Answers that look right on this material and are not. Each one is a distractor from a different question in the PL-300 bank for this domain.

No
Why it is wrong: Claiming the author must wrap every measure reference in CALCULATE conflates the model-measure rule with the inline-aggregation rule; only the latter needs an explicit CALCULATE.
CALCULATE is required to make SUM see the entire Sales table because aggregations cannot run in calculated columns otherwise.
Why it is wrong: Aggregations run in calculated columns, but without CALCULATE they would scan the whole Sales table because the row context on Customer does not propagate to Sales as a filter.
Yes
Why it is wrong: Saying Yes would imply zero size impact and would invite uncontrolled calculated-column growth on large fact tables.

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