Free Microsoft Power BI PL-300 Actual Exam Questions - Question 7 Discussion

Option A doesn't make much sense because summing sales_id values isn’t meaningful—they’re just identifiers, not numbers you’d total. Calculated columns (B and D) are static and won’t react to filters or slicers, which is usually important for reports. So, a measure that counts rows dynamically (C) seems like the only practical choice here to reflect the current filtered data accurately.

It’s C; calculated columns won’t change with slicers or filters anyway.

It’s C, because measures adjust with filters unlike calculated columns.

Probably C. Counting rows with a measure makes sense because sales_id is likely just an identifier, so summing it (like in A or D) wouldn't add up logically. Also, calculated columns like in B and D won't react well to report filters, which is a big downside for dynamic sales reports. Measures with COUNTROWS handle filtering properly and give you the total number of sales records easily.

B/C? B counts non-blank sales IDs, which is good if you just want to know how many sales entries exist, but it’s a calculated column, so it won’t aggregate well in reports. C uses COUNTROWS as a measure, which updates dynamically and counts all rows, matching typical reporting needs. Using a measure over a column usually makes more sense for totals like this since it recalculates across filters. A and D don’t really add up because summing sales_id isn’t meaningful. So between B and C, I’d go with C because it’s a measure and fits better for reporting.

Probably B. COUNTA on sales_id counts non-blank entries, which could be useful if you want to know how many sales records exist without summing values. Measures aren’t always necessary if it’s a simple count.

Maybe C makes the most sense since COUNTROWS will give you the total number of sales entries, which is often what’s needed for sales reports. A measure works better than a calculated column because you want it to update dynamically with filters. Options A and D don't seem right because summing IDs isn’t meaningful, and B’s calculated column with COUNTA might not be as flexible or accurate for reporting totals. So C fits better if we’re just counting how many sales records there are.

It’s A because summing sales_id directly doesn’t make sense, but summing sales amounts would.

It’s C, counting rows fits best for sales reporting here.