DA0-002 Visualization and Reporting Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  SAMEPERIODLASTYEAR

  Why it's wrong here

  SAMEPERIODLASTYEAR shifts the date context back exactly one year, returning prior-year figures rather than a year-to-date accumulation ending at the latest data date. It is tempting because it is a time-intelligence function for year-over-year comparisons, and would be correct when the requirement is comparing current sales against the equivalent prior-year period.

• ✗

  CALCULATE

  Why it's wrong here

  CALCULATE modifies filter context but performs no date truncation or accumulation, so it cannot itself produce a year-to-date total ending at the latest date. It is tempting because it is the core context-transition function used to wrap time-intelligence expressions, and would be correct as the outer function around a YTD measure.

• ✗

  SUMX

  Why it's wrong here

  SUMX is an iterator that evaluates an expression row by row over a table, returning a sum but applying no date filtering, so it cannot restrict sales to the current year to date. It tempts because it aggregates sales values, and would be correct when a row-context expression must be evaluated per row before summing.

• ✓

  TOTALYTD

  Why this is correct

  TOTALYTD aggregates a measure from the start of the year to the latest date present in the data, matching the stem's requirement for year-to-date sales. Unlike DATESYTD, which returns a date table, TOTALYTD evaluates the expression directly, producing the cumulative sales figure the analyst needs.