DP-600 · Question #122
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might h
The correct answer is B. No. This solution does NOT meet the goal. The expression NOT ( CALCULATE ( COUNTROWS ( 'Order Item' ) ) < 0 ) is a double negation - logically equivalent to COUNTROWS >= 0, which is always true and semantically different from a useful filter. More critically, wrapping CALCULATE insid
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a Fabric tenant that contains a semantic model named Model1. You discover that the following query performs slowly against Model1. You need to reduce the execution time of the query. Solution: You replace line 4 by using the following code:
NOT ( CALCULATE ( COUNTROWS ( 'Order Item' ) ) < 0) Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(49 responses)- A16% (8)
- B84% (41)
Explanation
This solution does NOT meet the goal. The expression NOT ( CALCULATE ( COUNTROWS ( 'Order Item' ) ) < 0 ) is a double negation - logically equivalent to COUNTROWS >= 0, which is always true and semantically different from a useful filter. More critically, wrapping CALCULATE inside NOT forces the DAX engine to use the slower Formula Engine (FE) rather than the optimized Storage Engine (SE). The Storage Engine handles simple comparisons like > 0 efficiently, but double-negation patterns bypass that optimization path. To improve query performance, you should use a direct positive comparison (e.g., COUNTROWS('Order Item') > 0) which allows the Storage Engine to process the predicate natively. The replacement in this solution would likely worsen performance, not improve it.
Topics
Community Discussion
No community discussion yet for this question.