Exam PL-300 topic 3 question 74 discussion

Tested and correct answer is: D. one row per year that contains the same value repeated for each year

A. one row per year that contains blank values for every year except 2023. The `2023 Population` measure filters the `Total Population` to only show values for the year 2023. For all other years, the measure returns blank. Thus, the table visual will display one row per year with blank values except for the year 2023, which will show the population value for 2023.

I was doubting but A is the correct answer. does not respect the row context of the Date[Year] column in the visual. Instead, it overrides it with a fixed filter: 'Date'[Year] = 2023. So what happens? Power BI evaluates the measure once, using only the filter 'Date'[Year] = 2023. Then it repeats that same result for every row in the visual — regardless of the year shown in each row. This behavior is expected when you hardcode a filter inside CALCULATE.

Option A, checked with Chatgpt and Gemini.(both selected A with similar explanation)

2023 Population is a constant value across all years as calculation is encapsulated in a CALCULATE function setting the year to be '2023' despite any other context therefore, even when the table is reporting all years in the period, this is not going to change that result

My Opinion: D When I add Date[Year] as a column, the row context would typically calculate the population sum for each distinct year. However, the measure forces a new row context to evaluate only for the year 2023, resulting in the same population value (for 2023) being displayed for every year in the table.

Well first of all; the Date measure is completely wrong: It should be ; 2023 Population = CALCULATE([Total Population], YEAR('Date'[Date])=2023) As a date table (created by calendar or calendar auto) will return a date you will have to format in short date anyway. Secondly, the population table contains dates as 01/01/YYYY meaning, one record per year. When you apply the one to many relationship, you will have all records from population matching the date of 01/01/yyyy in the Date table And as your Measure is calculating with a filter applied on the YEAR portion of the date = 2023, well, you will get one row only. In SQL you would have something like "select population from PopulationTable where Year(PopulationTable.Date)=2023 And when you have the measure being right it will show you the population number according to the selected year. It will return 1 record for 2023 with the corresponding population amount

C in my opinion

Tested and D is the correct answer.

C - i tested it. When you specify Date(Year) in the visual - it is implied that you are using that part of the Date hierarchy table. That automatically means that only the year selected by the filter of the expression is returned

Tested C

D is the right answer.

D is the correct answer

tested

D is correct

C is correct, if you use a table visual and select year only you will receive a list with the distinct years. Once you add the 2023 Population measure, there is only 1 row for 2023 and the Total Population (in 2023) left.

Tested and correct answer is D. Ref: https://learn.microsoft.com/en-us/dax/calculate-function-dax This is a property of CALCULATE function. "When the filter expression is not wrapped in the KEEPFILTERS function: If the columns (or tables) aren't in the filter context, then new filters will be added to the filter context to evaluate the expression. If the columns (or tables) are already in the filter context, the existing filters will be overwritten by the new filters to evaluate the CALCULATE expression". This question refers to the "overwritten case.