Expecting one Date table to serve two roles at once
The wrong answers try to make a single Date table filter OrderDate and ShipDate together: a second active relationship, a bidirectional cross-filter, or USERELATIONSHIP. Only one relationship between two tables can be active, and cross-filter direction controls propagation, not which role applies. USERELATIONSHIP switches the role inside one measure at a time. To filter both roles in one visual, duplicate the Date dimension so each role has its own active relationship to Sales.
See it in a sample questionExpecting CALCULATE filters to intersect by default
The wrong answers assume a CALCULATE filter argument combines with a filter already on the same column, or that KEEPFILTERS discards the argument or clears filters. By default the new filter overwrites the existing one, so Blue Revenue inside a visual filtered to Red returns Blue sales only. KEEPFILTERS is what intersects the new filter with the existing one. Clearing filters is the job of REMOVEFILTERS or ALL.
See it in a sample questionUsing FILTER and Boolean arguments the wrong way round
The wrong answers misjudge when a CALCULATE filter needs FILTER. A Boolean filter argument cannot reference a measure, so a test on [Profit] needs FILTER over VALUES, and neither KEEPFILTERS nor ALL lifts that restriction. Where a Boolean expression is enough, as for Red product sales in an Import model, passing a table expression is the pattern the documentation says to avoid: FILTER over Product iterates row by row, with or without ALL, and CALCULATETABLE also produces a table expression.
See it in a sample questionPicking a date-set function where an aggregator is needed
The wrong answers choose a time-intelligence function that returns the wrong kind of result or the wrong period. DATESYTD and DATESMTD return a table of dates and do not aggregate an expression, while TOTALYTD and TOTALQTD evaluate one. TOTALMTD sums across the month-to-date range instead of returning the closing-day value that CLOSINGBALANCEMONTH gives, and OPENINGBALANCEMONTH reads the first date rather than the last.
See it in a sample questionTreating calculated columns as free of storage cost
The wrong answers give calculated columns the behaviour of measures: no stored result, evaluation on demand, or no effect on size. A calculated column is evaluated at data refresh and its result is stored in the model, so it increases model size on a large fact table. Calculated columns compress less efficiently than Power Query computed columns and lengthen refresh, so the guidance prefers a custom column in Power Query.
See it in a sample question