Aggregations for performance in Power BI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to calculate the total sales amount.

Power BI

Total Sales = SUM([1])

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

ASales[Amount]

BSales[Date]

CCustomers[Name]

DProducts[Category]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-numeric column like dates or names in SUM.

Forgetting to specify the table and column.

The SUM function adds all values in the Sales[Amount] column to calculate total sales.

2fill in blank

medium

Complete the code to calculate the average sales amount.

Power BI

Average Sales = AVERAGE([1])

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

ASales[Quantity]

BSales[Amount]

CProducts[Price]

DCustomers[Age]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-sales column like age or quantity.

Confusing average with sum.

The AVERAGE function calculates the mean of the Sales[Amount] values.

3fill in blank

hard

Fix the error in the code to calculate the maximum sales amount.

Power BI

Max Sales = MAX([1])

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

ASales[Date]

BCustomers[ID]

CSales[Amount]

DProducts[Name]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a date or text column inside MAX.

Not specifying the correct table and column.

The MAX function finds the highest value in the Sales[Amount] column. Using dates or names causes errors.

4fill in blank

hard

Fill the blank to calculate total sales for a specific product category.

Power BI

Category Sales = CALCULATE(SUM(Sales[Amount]), Sales[Category] [1] "Electronics")

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

A=

B==

CIN

D>

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '=' in DAX.

Using '>' which is not correct for category filtering.

Use = to filter sales where the category is 'Electronics'. The correct syntax is Sales[Category] = "Electronics" or using IN for multiple values.

5fill in blank

hard

Fill all three blanks to create a measure that counts customers with sales above 1000.

Power BI

High Value Customers = CALCULATE(DISTINCTCOUNT([1]), FILTER(ALL(Sales), Sales[Amount] [2] [3]))

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

ACustomers[CustomerID]

B>

C1000

DSales[Date]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a date column instead of customer ID for counting.

Using '=' instead of '>' for filtering sales above 1000.

This measure counts unique customers whose sales amount is greater than 1000. Use Customers[CustomerID] for counting, > for comparison, and 1000 as the threshold.

Practice

1.

What is the main benefit of using aggregations in Power BI reports?

easy

A. Speeding up report loading by summarizing detailed data

B. Increasing the size of the data model

C. Making data entry easier for users

D. Automatically fixing data errors

Solution

1. Step 1: Understand the purpose of aggregations

   Aggregations summarize detailed data into smaller, grouped summaries.

2. Step 2: Identify the effect on report performance

   Using these summaries reduces the amount of data Power BI processes, speeding up report loading.

3. Final Answer:

   Speeding up report loading by summarizing detailed data -> Option A

4. Quick Check:

   Aggregations improve speed [OK]

Hint: Aggregations reduce data detail to speed up reports [OK]

Common Mistakes:

• Thinking aggregations increase data size
• Confusing aggregations with data entry
• Assuming aggregations fix data errors

2.

Which of the following is the correct DAX syntax to create a simple aggregation measure that sums the SalesAmount column?

easy

A. Total Sales = AVERAGE(Sales[SalesAmount])

B. Total Sales = COUNT(Sales[SalesAmount])

C. Total Sales = SUM(Sales[SalesAmount])

D. Total Sales = SUMMARIZE(Sales, Sales[SalesAmount])

Solution

1. Step 1: Identify the aggregation function for summing

   The SUM function adds all values in a column.

2. Step 2: Check the syntax for summing SalesAmount

   Total Sales = SUM(Sales[SalesAmount]) correctly sums the column.

3. Final Answer:

   Total Sales = SUM(Sales[SalesAmount]) -> Option C

4. Quick Check:

   SUM function sums values [OK]

Hint: SUM() adds values; COUNT() counts rows [OK]

Common Mistakes:

• Using COUNT instead of SUM for totals
• Using SUMMARIZE incorrectly as aggregation
• Confusing AVERAGE with SUM

3.

Given a summary table SalesSummary with columns Region and TotalSales, what will the following DAX measure return?
Measure = CALCULATE(SUM(SalesSummary[TotalSales]), SalesSummary[Region] = "West")

medium

A. Sum of TotalSales for the West region only

B. Sum of TotalSales for all regions

C. Count of rows where region is West

D. Error due to incorrect filter syntax

Solution

1. Step 1: Understand the CALCULATE filter

   The filter SalesSummary[Region] = "West" limits data to West region.

2. Step 2: Calculate sum with filter applied

   SUM aggregates TotalSales only for rows where Region is West.

3. Final Answer:

   Sum of TotalSales for the West region only -> Option A

4. Quick Check:

   CALCULATE applies filter [OK]

Hint: CALCULATE applies filters to aggregation [OK]

Common Mistakes:

• Ignoring the filter and summing all regions
• Confusing SUM with COUNT
• Assuming syntax error in filter

4.

Identify the error in this DAX measure intended to sum SalesAmount for the East region:
Measure = CALCULATE(SUM(Sales[SalesAmount]), Sales[Region] == "East")

medium

A. SUM cannot be used inside CALCULATE

B. Using double equals (==) instead of single equals (=) in filter

C. Missing ALL() function to remove filters

D. SalesAmount column name is incorrect

Solution

1. Step 1: Check filter syntax inside CALCULATE

   DAX uses single equals (=) for filter conditions, not double equals (==).

2. Step 2: Confirm correct syntax for filter

   Replace Sales[Region] == "East" with Sales[Region] = "East" to fix error.

3. Final Answer:

   Using double equals (==) instead of single equals (=) in filter -> Option B

4. Quick Check:

   Use = for filters in DAX [OK]

Hint: Use single = for filters, not == [OK]

Common Mistakes:

• Using == like in other languages
• Thinking SUM can't be inside CALCULATE
• Adding unnecessary ALL() function

5.

You have a large sales dataset and want to improve report speed by creating an aggregation table that groups sales by Year and ProductCategory. Which approach is best to create this aggregation table in Power BI?

hard

A. Add a slicer for ProductCategory on the report page

B. Use FILTER(Sales, Sales[Year] = 2023) to reduce data

C. Create a calculated column with Sales[SalesAmount] * 2

D. Create a new table using SUMMARIZE(Sales, Sales[Year], Sales[ProductCategory], "TotalSales", SUM(Sales[SalesAmount]))

Solution

1. Step 1: Understand aggregation table creation

   Use SUMMARIZE to group data by Year and ProductCategory and calculate totals.

2. Step 2: Evaluate options for aggregation

   Create a new table using SUMMARIZE(Sales, Sales[Year], Sales[ProductCategory], "TotalSales", SUM(Sales[SalesAmount])) creates a summary table with grouped totals, ideal for aggregation.

3. Final Answer:

   Create a new table using SUMMARIZE(Sales, Sales[Year], Sales[ProductCategory], "TotalSales", SUM(Sales[SalesAmount])) -> Option D

4. Quick Check:

   SUMMARIZE creates aggregation tables [OK]

Hint: Use SUMMARIZE to group and sum for aggregation tables [OK]

Common Mistakes:

• Using FILTER instead of grouping
• Creating calculated columns instead of tables
• Relying on slicers for performance