Given a Sales table with columns Product and SalesAmount, what is the result of this DAX measure?
Filtered Sales = CALCULATE(SUM(Sales[SalesAmount]), FILTER(Sales, Sales[Product] = "Bike"))
Assuming the Sales table has these rows:
- Bike, 100
- Car, 200
- Bike, 150
- Boat, 300
What is the value of Filtered Sales?
Filtered Sales = CALCULATE(SUM(Sales[SalesAmount]), FILTER(Sales, Sales[Product] = "Bike"))Only sum the SalesAmount where Product is exactly "Bike".
The FILTER function limits rows to those where Product is "Bike". The SUM then adds 100 + 150 = 250.
You want to create a report page where users can filter sales data by a date range interactively. Which visualization component is best suited for this purpose?
Think about which visual lets users pick a range of dates easily.
A slicer with a date range slider allows users to select start and end dates to filter the report dynamically.
You have two tables: Orders and Customers. Orders has a CustomerID column related to Customers. You want to create a measure that sums Order Amount only for customers in the "Premium" segment. Which DAX expression correctly filters Orders based on Customers segment?
Use RELATED to access columns from the related Customers table inside FILTER on Orders.
Option C filters Orders rows where the related Customer's Segment is "Premium", then sums OrderAmount. Other options have syntax errors or incorrect filter context.
What error will this DAX expression cause?
Filtered Sales = CALCULATE(SUM(Sales[SalesAmount]), FILTER(Sales, Sales[Product] == "Bike"))
Check the comparison operator used in DAX.
DAX uses a single '=' for equality, not '=='. Using '==' causes a syntax error.
In a Power BI report with Row-Level Security (RLS) applied to the Sales table, what happens when you apply an additional filter on Sales[Region] = "West" in a visual?
Think about how RLS and report filters combine.
RLS filters data first, then report filters apply. So the visual shows data allowed by RLS and further filtered by Region = "West".