Why choosing the right visual matters in Power BI - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a bar chart visual in Power BI.

Power BI

BarChart = [1](SalesData, 'Product', 'SalesAmount')

Drag options to blanks, or click blank then click option'

ABarChart

BBarChartVisual

Cbar_chart

DBarChartVisualize

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect visual names like 'bar_chart' or 'BarChartVisualize'.

In Power BI, the bar chart visual is created using the BarChart function or visual name.

2fill in blank

medium

Complete the DAX measure to calculate total sales for the visual.

Power BI

TotalSales = SUM([1][SalesAmount])

Drag options to blanks, or click blank then click option'

ASalesAmount

BSales

CSalesTable

DSalesData

Attempts:

3 left

💡 Hint

Common Mistakes

Using the column name instead of the table name inside SUM.

The SUM function sums the SalesAmount column from the SalesData table.

3fill in blank

hard

Fix the error in the DAX formula to calculate average sales per product.

Power BI

AvgSales = AVERAGE([1][SalesAmount])

Drag options to blanks, or click blank then click option'

ASalesData

BSales

CSalesTable

DSalesAmount

Attempts:

3 left

💡 Hint

Common Mistakes

Using the column name alone without the table name.

Using incorrect table names.

The AVERAGE function requires the table name before the column name. SalesData is the correct table.

4fill in blank

hard

Fill both blanks to filter sales data for the year 2023 and calculate total sales.

Power BI

TotalSales2023 = CALCULATE(SUM(SalesData[SalesAmount]), SalesData[Year] [1] [2] 2023)

Drag options to blanks, or click blank then click option'

A=

B>

C==

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '=' for equality.

Using wrong comparison operators like '<' or '>'.

The correct syntax uses a single equals sign = for comparison and the CALCULATE function filters sales where the year equals 2023.

5fill in blank

hard

Fill all three blanks to create a measure that calculates total sales for products with sales greater than 1000.

Power BI

HighSales = CALCULATE(SUM([1][SalesAmount]), FILTER([2], [3][SalesAmount] > 1000))

Drag options to blanks, or click blank then click option'

ASalesData

BSales

Attempts:

3 left

💡 Hint

Common Mistakes

Using different table names in the same formula.

Forgetting to use FILTER for row context.

All blanks refer to the SalesData table. The FILTER function filters rows where sales are greater than 1000.

Practice

1. Why is it important to choose the right visual when creating a Power BI report?

easy

A. Because the right visual makes data easier to understand and interpret.

B. Because visuals always look better with more colors and effects.

C. Because the right visual increases the file size of the report.

D. Because the right visual hides data from the audience.

Solution

1. Step 1: Understand the purpose of visuals in reports

   Visuals help communicate data clearly and make it easier for viewers to understand the story behind the data.

2. Step 2: Identify the effect of choosing the right visual

   The right visual simplifies complex data and highlights key insights, improving comprehension.

3. Final Answer:

   Because the right visual makes data easier to understand and interpret. -> Option A

4. Quick Check:

   Right visual = easier understanding [OK]

Hint: Right visuals simplify data for clear understanding [OK]

Common Mistakes:

• Thinking more colors always improve visuals
• Believing visuals increase file size significantly
• Assuming visuals hide data intentionally

2. Which of the following is the correct way to add a bar chart visual in Power BI?

easy

A. Select the bar chart icon from the Visualizations pane and drag the desired fields to Axis and Values.

B. Write a DAX formula to create a bar chart.

C. Use the Query Editor to draw a bar chart.

D. Insert a bar chart by typing <bar_chart> in the report canvas.

Solution

1. Step 1: Identify how visuals are added in Power BI

   Visuals are added by selecting icons in the Visualizations pane, not by code or markup.

2. Step 2: Confirm the correct method for bar charts

   Drag fields to Axis and Values after selecting the bar chart icon to create the visual.

3. Final Answer:

   Select the bar chart icon from the Visualizations pane and drag the desired fields to Axis and Values. -> Option A

4. Quick Check:

   Visual pane + drag fields = correct bar chart [OK]

Hint: Use Visualizations pane icons to add charts [OK]

Common Mistakes:

• Trying to create visuals using DAX formulas
• Using Query Editor for visual creation
• Typing HTML-like tags on the canvas

3. Given a dataset with sales over time, which visual best shows trends clearly?

medium

A. Pie chart showing sales by product category.

B. Stacked bar chart showing sales by region.

C. Line chart showing sales amount over months.

D. Table listing sales transactions.

Solution

1. Step 1: Understand the data and goal

   The dataset has sales over time, so the goal is to show trends clearly.

2. Step 2: Match visual type to goal

   Line charts are best for showing trends over time because they connect data points sequentially.

3. Final Answer:

   Line chart showing sales amount over months. -> Option C

4. Quick Check:

   Trend over time = line chart [OK]

Hint: Use line charts to show trends over time [OK]

Common Mistakes:

• Using pie charts for time trends
• Choosing tables instead of visuals
• Stacked bars confuse time sequence

4. You created a pie chart to show sales by region, but the chart looks cluttered and hard to read. What should you do to fix this?

medium

A. Add more slices to the pie chart to show detailed data.

B. Replace the pie chart with a bar chart to better compare regions.

C. Increase the number of colors used in the pie chart.

D. Remove the legend to save space.

Solution

1. Step 1: Identify the problem with the pie chart

   Pie charts with many slices become cluttered and hard to interpret.

2. Step 2: Choose a better visual for comparison

   Bar charts display categories side by side, making it easier to compare values clearly.

3. Final Answer:

   Replace the pie chart with a bar chart to better compare regions. -> Option B

4. Quick Check:

   Cluttered pie chart = use bar chart [OK]

Hint: Use bar charts for many categories, not pie charts [OK]

Common Mistakes:

• Adding more slices increases clutter
• More colors confuse viewers
• Removing legend hides important info

5. You want to create a dashboard showing monthly sales, product category distribution, and customer satisfaction ratings. Which combination of visuals best supports clear communication?

hard

A. Scatter plot for monthly sales, pie chart for customer satisfaction, and table for product categories.

B. Table for monthly sales, stacked bar chart for product categories, and scatter plot for customer satisfaction.

C. Pie chart for monthly sales, line chart for product categories, and bar chart for customer satisfaction.

D. Line chart for monthly sales, pie chart for product categories, and gauge for customer satisfaction.

Solution

1. Step 1: Match each data type to the best visual

   Monthly sales over time is best shown with a line chart to show trends. Product category distribution suits a pie chart to show parts of a whole. Customer satisfaction ratings are often shown with a gauge to indicate performance level.

2. Step 2: Evaluate each option's visual choices

   Line chart for monthly sales, pie chart for product categories, and gauge for customer satisfaction correctly pairs each data type with an appropriate visual. Other options mismatch visuals and data types, reducing clarity.

3. Final Answer:

   Line chart for monthly sales, pie chart for product categories, and gauge for customer satisfaction. -> Option D

4. Quick Check:

   Right visual for each data type = Line chart for monthly sales, pie chart for product categories, and gauge for customer satisfaction. [OK]

Hint: Match data story to best visual type [OK]

Common Mistakes:

• Using pie charts for time series data
• Using tables instead of visuals for summaries
• Mixing unrelated visuals for data types