Tableau-Desktop-Found Understanding Tableau Concepts 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.

• ✗

  A calculated field using SUM(Sales) / TOTAL(SUM(Sales))

  Why it's wrong here

  TOTAL returns the aggregate across the whole table, but this expression is evaluated as a table calculation context only when the addressing and partitioning are correct. Without configuring the calculation to compute across all regions, it can return unexpected values, and it also requires manual table calculation setup rather than the purpose-built quick calculation for percent of total.

• ✗

  Changing the mark type to Pie and using Angle as the size

  Why it's wrong here

  Switching to a pie mark changes the visual encoding but does not transform the underlying measure into percentages. The analyst specifically wants a bar chart whose values sum to one hundred percent, so altering the mark type addresses appearance rather than the proportional calculation needed to express each region as a share of the whole.

• ✗

  A dual axis combining SUM(Sales) and a reference line at the average

  Why it's wrong here

  A dual axis overlays two measures on shared or synchronized axes, and a reference line marks a statistical value such as the mean. Neither operation converts each region's sales into a share of the total, so the resulting bars would still show absolute currency values rather than percentages that sum to one hundred.

• ✓

  Quick Table Calculation of Percent of Total on SUM(Sales)

  Why this is correct

  A Percent of Total quick table calculation divides each mark's value by the total of the values in the view, producing proportions that sum to one hundred percent. Applied to SUM(Sales) by Region, it gives each region's share of overall sales and keeps the chart as a bar chart, exactly matching the requirement.