Statistical summary card in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ visualization

intermediate

Create a Statistical Summary Card Showing Average Sales

You want to create a summary card in Tableau that shows the average sales amount for the current year. Which of the following calculated fields will correctly compute the average sales?

A TOTAL(AVG([Sales]))

B SUM([Sales]) / COUNTD([Order ID])

C AVG([Sales])

D WINDOW_SUM([Sales]) / WINDOW_COUNT([Order ID])

💡 Hint

Think about the simplest way to calculate average sales using built-in aggregation functions.

The AVG() function directly calculates the average of the Sales field. Option C divides total sales by distinct orders which may not be accurate if orders have multiple sales entries. Options A and D use table calculations which are unnecessary for a simple average.

❓ dax_lod_result

intermediate

DAX Measure for Median Sales in a Summary Card

In Power BI, you want to create a statistical summary card that shows the median sales amount. Which DAX measure will correctly calculate the median sales?

A Median Sales = CALCULATE(MEDIAN('Sales'[SalesAmount]), ALL('Sales'))

B Median Sales = AVERAGE('Sales'[SalesAmount])

C Median Sales = SUM('Sales'[SalesAmount]) / COUNT('Sales'[SalesAmount])

D Median Sales = MEDIAN('Sales'[SalesAmount])

💡 Hint

Use the DAX function that directly calculates the median of a column.

MEDIAN() returns the median value of the column. Option D returns average, C returns mean by manual calculation, and D tries to calculate median ignoring filters which is not always desired for a summary card.

🧠 Conceptual

advanced

Best Practice for Displaying Statistical Summary Cards

Which of the following is the best practice when designing a statistical summary card for business users?

A Use clear labels, simple statistics like average and median, and highlight key trends visually.

B Include multiple complex statistics like skewness and kurtosis to provide deep insights.

C Display raw data tables alongside the summary card for full transparency.

D Use bright colors and animations to attract attention regardless of data clarity.

💡 Hint

Think about what helps users quickly understand key information.

Summary cards should be simple and clear, focusing on key statistics and visual cues. Complex stats can confuse users, raw tables clutter the view, and flashy visuals can distract from the message.

🔧 Formula Fix

advanced

Identify the Error in Tableau Calculation for Summary Card

A Tableau user wrote this calculated field to show the percentage of total sales:
SUM([Sales]) / SUM(TOTAL([Sales]))
Why does this calculation produce an error or incorrect result?

Tableau

SUM([Sales]) / SUM(TOTAL([Sales]))

A TOTAL() returns a number, so wrapping it in SUM() causes a type error.

B The calculation is correct and will produce the percentage of total sales.

C The calculation divides by a running total instead of total sales, causing wrong output.

D TOTAL() cannot be nested inside SUM(), causing a syntax error.

💡 Hint

Check how TOTAL() works and what data type it returns.

TOTAL() returns an aggregated number, not a column or set, so wrapping it inside SUM() is invalid and causes a type error.

🎯 Scenario

expert

Designing a Dynamic Statistical Summary Card with Filters

You need to create a summary card in Power BI that dynamically updates to show the average sales for the selected region and year. Which DAX measure will correctly achieve this behavior?

A Avg Sales Dynamic = AVERAGE('Sales'[SalesAmount])

B Avg Sales Dynamic = CALCULATE(AVERAGE('Sales'[SalesAmount]))

C Avg Sales Dynamic = CALCULATE(AVERAGE('Sales'[SalesAmount]), REMOVEFILTERS('Sales'[Region], 'Sales'[Year]))

D Avg Sales Dynamic = CALCULATE(AVERAGE('Sales'[SalesAmount]), ALL('Sales'))

💡 Hint

Consider how CALCULATE works with filters and what happens if you remove or keep them.

Option B calculates average sales respecting current filters (region and year). Option B removes all filters, ignoring selections. Option B calculates average but may not respond to slicers if context is complex. Option B removes filters, so it ignores user selections.