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.

• ✗

  Table calculation

  Why it's wrong here

  Table calculations operate on the aggregated values already present in the view, so the average shifts as dimensions change the level of detail. It is tempting because table calculations are the usual tool for percent-of-total and ranking, but a constant per-customer average needs a fixed level-of-detail expression.

• ✓

  Level of Detail expression

  Why this is correct

  A Level of Detail expression fixes the aggregation at a declared granularity, such as customer, independently of the dimensions in the view. This satisfies the requirement that the average sales per customer stays constant regardless of the view's level of detail.

• ✗

  Parameter

  Why it's wrong here

  Parameters supply user-controlled input values; they do not fix the aggregation grain of a calculated field, so the average still varies with the view's dimensions. It is tempting because parameters drive dynamic calculations, but a constant per-customer average requires a fixed level-of-detail expression.

• ✗

  Filter

  Why it's wrong here

  Filters remove or restrict rows before aggregation, so the average still recalculates at whatever level of detail remains in the view. It is tempting because filters shape which customers contribute, but fixing a value across all dimensions requires a fixed level-of-detail expression instead.