You have a table named Sales with columns Quantity and UnitPrice. You want to create a measure that calculates the total sales amount by multiplying quantity by unit price and summing over all rows.
Which DAX expression correctly calculates this total sales amount?
Think about multiplying quantity and price for each row, then adding all results.
Option A uses SUMX to multiply Quantity and UnitPrice row by row, then sums the results. Option A multiplies total quantities by total prices, which is incorrect. Options C and D add quantities and prices, not multiply.
You have calculated a measure Sales Growth % that shows the percentage increase in sales compared to the previous year. You want to display this on a dashboard for easy comparison across years.
Which visualization type is best suited to clearly show the sales growth percentage over multiple years?
Think about how to best show trends over time.
A line chart is best for showing trends like percentage growth over time. Stacked bar charts and pie charts are better for absolute values or parts of a whole. Tables show numbers but are less visual for trends.
You have a Sales table with columns Revenue and Cost. You want to add a calculated column that shows the profit margin percentage for each sale.
Which DAX formula correctly creates this calculated column?
Use a function that safely handles division by zero.
Option C uses DIVIDE which safely divides and handles division by zero. Option C is missing DIVIDE and may cause errors if revenue is zero. Option C uses aggregation functions which are not valid in calculated columns. Option C has incorrect operator precedence causing wrong calculation.
Consider this DAX measure intended to calculate the average unit price:
Average Price = SUM(Sales[UnitPrice]) / COUNT(Sales[UnitPrice])
What is the main problem with this measure?
Think about built-in functions for averages.
While the formula mathematically calculates average, using AVERAGE(Sales[UnitPrice]) is simpler, more readable, and optimized. The given formula works but is not best practice. There is no syntax error.
You create a measure Total Profit = SUM(Sales[Revenue]) - SUM(Sales[Cost]). When you place this measure in a table visual grouped by Region, the profit is calculated per region. But when you use it in a card visual, it shows the total profit for all regions.
Why does the same measure show different results in these visuals?
Think about how filters and grouping affect calculations.
The evaluation context in DAX changes depending on the visual. In a table grouped by region, the measure calculates profit per region. In a card visual with no grouping, it calculates total profit. This is normal behavior due to context.