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.

Practice

1.

What is the main purpose of a statistical summary card in Tableau dashboards?

easy

A. To design interactive maps

B. To display detailed raw data tables

C. To create complex data models

D. To show key numbers clearly and simply

Solution

1. Step 1: Understand the role of summary cards

   Summary cards highlight important numbers like totals or averages for quick insight.

2. Step 2: Compare options with this purpose

   Only To show key numbers clearly and simply matches the purpose of showing key numbers simply and clearly.

3. Final Answer:

   To show key numbers clearly and simply -> Option D

4. Quick Check:

   Summary card = clear key numbers [OK]

Hint: Summary cards highlight main numbers quickly [OK]

Common Mistakes:

• Confusing summary cards with detailed tables
• Thinking summary cards create data models
• Assuming summary cards are for maps

2.

Which of the following is the correct way to create a SUM aggregation for a measure named Sales in Tableau?

easy

A. SUM([Sales])

B. SUM(Sales)

C. SUM{Sales}

D. SUM: Sales

Solution

1. Step 1: Recall Tableau aggregation syntax

   Tableau uses square brackets for field names inside aggregation functions.

2. Step 2: Check each option

   Only SUM([Sales]) uses correct syntax with brackets and parentheses.

3. Final Answer:

   SUM([Sales]) -> Option A

4. Quick Check:

   SUM with brackets = SUM([Sales]) [OK]

Hint: Use square brackets for fields inside functions [OK]

Common Mistakes:

• Omitting square brackets around field names
• Using curly braces instead of parentheses
• Using colon instead of parentheses

3.

Given a dataset with Sales values: 100, 200, 300, what will the AVG([Sales]) aggregation show on a summary card?

medium

A. 600

B. 200

C. 300

D. 100

Solution

1. Step 1: Calculate the average of Sales values

   Sum is 100 + 200 + 300 = 600; count is 3.

2. Step 2: Compute average

   Average = 600 / 3 = 200.

3. Final Answer:

   200 -> Option B

4. Quick Check:

   AVG = sum/count = 200 [OK]

Hint: Average = total sum divided by count [OK]

Common Mistakes:

• Choosing sum instead of average
• Picking a single value instead of average
• Confusing average with maximum

4.

Which of the following formulas will cause an error when used in a Tableau summary card?

IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low' END

medium

A. IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low' END

B. >edoc/edoc<

C. IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low'

D. code>IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low' END

Solution

1. Step 1: Understand Tableau IF statement syntax

   Tableau IF statements must end with END keyword.

2. Step 2: Check each option for missing END

   IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low' is missing END, causing syntax error.

3. Final Answer:

   IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low' -> Option C

4. Quick Check:

   Missing END causes error [OK]

Hint: Always end IF statements with END in Tableau [OK]

Common Mistakes:

• Forgetting END keyword in IF statements
• Using wrong comparison operators
• Misplacing THEN or ELSE keywords

5.

You want to create a summary card showing the COUNT of unique customers who made purchases over $500. Which Tableau calculation should you use?

hard

A. COUNTD(IF [Sales] > 500 THEN [Customer ID] END)

B. COUNT(IF [Sales] > 500 THEN [Customer ID] END)

C. SUM(IF [Sales] > 500 THEN 1 ELSE 0 END)

D. AVG(IF [Sales] > 500 THEN [Customer ID] END)

Solution

1. Step 1: Identify requirement for unique count of customers

   Use COUNTD to count distinct customer IDs.

2. Step 2: Filter customers with sales over $500

   Use IF to include only customers where [Sales] > 500.

3. Step 3: Combine into calculation

   COUNTD(IF [Sales] > 500 THEN [Customer ID] END) counts unique customers meeting condition.

4. Final Answer:

   COUNTD(IF [Sales] > 500 THEN [Customer ID] END) -> Option A

5. Quick Check:

   Unique count with condition = COUNTD(IF...) [OK]

Hint: Use COUNTD with IF for unique conditional counts [OK]

Common Mistakes:

• Using COUNT instead of COUNTD for unique counts
• Using SUM or AVG instead of count functions
• Not filtering with IF condition properly