You have a sales table with a column SalesAmount and a date column OrderDate. You want to create a measure that calculates the total sales for the current year only.
Which DAX measure will correctly calculate this?
Use CALCULATE with FILTER to apply a row context filter on the date column.
Option B uses CALCULATE with FILTER to correctly filter rows where the year of OrderDate matches the current year. Option B tries to use a boolean expression directly inside CALCULATE, which is invalid. Option B uses SUMX with FILTER, which works but is less efficient. Option B sums all sales without filtering.
You want to create a KPI visual in Power BI that shows sales growth. Which color usage follows best practices for accessibility and clarity?
Think about common color meanings and accessibility.
Green usually means good or positive, red means bad or negative. Ensuring color contrast helps users with visual impairments. Option D follows these best practices. Option D reverses common meanings. Option D lacks differentiation. Option D can confuse users and reduce clarity.
You have sales data and a separate date table. You want to create a KPI visual that shows sales for the current month and compares it to the previous month. What is the best data modeling approach?
Think about how Power BI uses relationships and date tables for time intelligence.
Option A is best practice: a single date table linked to sales allows use of built-in time intelligence functions like SAMEPERIODLASTMONTH. Option A is inefficient and error-prone. Option A can cause data duplication and performance issues. Option A complicates the model unnecessarily.
Given this DAX measure for a KPI visual:
Sales Growth % = DIVIDE(SUM(Sales[SalesAmount]) - SUM(Sales[SalesAmount]), SUM(Sales[SalesAmount]), 0)
What is the main issue causing incorrect KPI output?
Look carefully at the subtraction in the numerator.
The numerator subtracts SUM(Sales[SalesAmount]) from itself, so it always equals zero, making the growth always zero. Option A is incorrect because DIVIDE has a third argument (0) as alternate result. Option A is wrong because SUM does not accept two arguments, but here the second argument is inside DIVIDE, so syntax is valid. Option A is a modeling suggestion but not the main error.
You need to create a KPI visual that shows sales growth for multiple product categories side by side. The data model has a sales table and a product category table. How should you design the KPI visual and measures to best support this?
Think about dynamic filtering and scalability for multiple categories.
Option C allows dynamic calculation of sales growth per category and displays them side by side in a matrix, which is scalable and user-friendly. Option C is inefficient and hard to maintain. Option C uses calculated columns which are static and not recommended for dynamic KPIs. Option C limits user to one category at a time, reducing insight.