Microsoft PL-300 Practice Test 35
Question 340
The original scenario was: A bar chart must show each product's rank by Sales Amount within selected business scope. The initial solution is already in place. Now this new requirement arises: The business wants rank only among selected products. Which ADDITIONAL action BEST meets the changed condition?
- Products sort by measured sales rank, with ties handled by the chosen policy
- Sort ProductName alphabetically and label that order as sales rank
- Create a RANKX measure over the intended product population
- Change the rank table to an ALLSELECTED scope
Explanation
Correct Answer
D:The changed requirement is 'The business wants rank only among selected products'. The additional response is 'Change the rank table to an ALLSELECTED scope'.
Incorrect Answers
A:This observes the original approach but is not an additional action: Products sort by measured sales rank, with ties handled by the chosen policy.
B:This remains unsuitable for the original situation: Alphabetical order is not a revenue-based rank. It also does not meet the changed need.
C:This is the already implemented original solution: Create a RANKX measure over the intended product population. RANKX evaluates relative rankings for values in a defined table. It does not itself solve the new requirement.
Question 341
A measure needs Sales Amount for the same period in the previous year. Which approach BEST meets the stated Microsoft Power BI requirement?
- Subtract 365 from each day and assume leap years never matter
- Use SWITCH(TRUE(), ...) with ordered thresholds and a default
- Validate fiscal calendar mapping rather than assuming Gregorian period shifts
- Use a time-intelligence expression such as SAMEPERIODLASTYEAR on the marked Date table
Explanation
Correct Answer
D:Time intelligence shifts a valid date context to the corresponding prior-year period. For the stated case, Use a time-intelligence expression such as SAMEPERIODLASTYEAR on the marked Date table.
Incorrect Answers
A:Fixed day arithmetic does not reliably represent calendar-year comparisons. The proposed shortcut 'Subtract 365 from each day and assume leap years never matter' fails the documented need.
B:This addresses a separate source situation: A finance measure maps an integer risk score into Low, Medium, and High bands. It does not directly satisfy this case's priority.
C:This might be appropriate after a different requirement arises: Fiscal calendars use an unusual period pattern. It is not the best initial response to the stated case.
Question 342
A measure needs Sales Amount for the same period in the previous year. A colleague proposes: Subtract 365 from each day and assume leap years never matter. Which explanation BEST identifies the defect in that proposal?
- Time intelligence shifts a valid date context to the corresponding prior-year period
- Ambiguous thresholds can return incorrect risk categories
- Fixed day arithmetic does not reliably represent calendar-year comparisons
- The suggested approach is safe merely because its product name is familiar.
Explanation
Correct Answer
C:Fixed day arithmetic does not reliably represent calendar-year comparisons. This directly explains why the proposal 'Subtract 365 from each day and assume leap years never matter' should not be used.
Incorrect Answers
A:This is reasoning supporting the preferred solution 'Use a time-intelligence expression such as SAMEPERIODLASTYEAR on the marked Date table', but it does not directly name the defect in the proposed shortcut.
B:This addresses a different case: A finance measure maps an integer risk score into Low, Medium, and High bands. It is not the specific defect in 'Subtract 365 from each day and assume leap years never matter'.
D:Product familiarity is not evidence of suitability. The actual defect in this proposal is: Fixed day arithmetic does not reliably represent calendar-year comparisons.
Question 343
A measure needs Sales Amount for the same period in the previous year. After implementing Use a time-intelligence expression such as SAMEPERIODLASTYEAR on the marked Date table, which observation BEST demonstrates that the intended result is actually working?
- Boundary scores map to the approved band in explicit tests
- A monthly visual compares current-period and valid prior-year amounts
- The report owner approves Use a time-intelligence expression such as SAMEPERIODLASTYEAR on the marked Date table without testing the resulting behavior.
- The team schedules a future check of whether A monthly visual compares current-period and valid prior-year amounts, but has not observed a result.
Explanation
Correct Answer
B:The observation 'A monthly visual compares current-period and valid prior-year amounts' directly tests the intended result. Time intelligence shifts a valid date context to the corresponding prior-year period.
Incorrect Answers
A:This belongs to a different case: A finance measure maps an integer risk score into Low, Medium, and High bands. It does not validate the current change.
C:Approval of a proposed design is not evidence of working behavior. The required observation is: A monthly visual compares current-period and valid prior-year amounts.
D:A future test is not yet observed operational evidence. The verification must establish: A monthly visual compares current-period and valid prior-year amounts.
Question 344
The original scenario was: A measure needs Sales Amount for the same period in the previous year. The initial solution is already in place. Now this new requirement arises: Fiscal calendars use an unusual period pattern. Which ADDITIONAL action BEST meets the changed condition?
- A monthly visual compares current-period and valid prior-year amounts
- Validate fiscal calendar mapping rather than assuming Gregorian period shifts
- Subtract 365 from each day and assume leap years never matter
- Use a time-intelligence expression such as SAMEPERIODLASTYEAR on the marked Date table
Explanation
Correct Answer
B:The changed requirement is 'Fiscal calendars use an unusual period pattern'. The additional response is 'Validate fiscal calendar mapping rather than assuming Gregorian period shifts'.
Incorrect Answers
A:This observes the original approach but is not an additional action: A monthly visual compares current-period and valid prior-year amounts.
C:This remains unsuitable for the original situation: Fixed day arithmetic does not reliably represent calendar-year comparisons. It also does not meet the changed need.
D:This is the already implemented original solution: Use a time-intelligence expression such as SAMEPERIODLASTYEAR on the marked Date table. Time intelligence shifts a valid date context to the corresponding prior-year period. It does not itself solve the new requirement.
Question 345
An executive wants cumulative revenue from January 1 through each selected day. Which approach BEST meets the stated Microsoft Power BI requirement?
- Set a supported fiscal year end or fiscal date logic
- Add only the last seven days and call it year-to-date
- Use DISTINCTCOUNT(Sales[CustomerID]) for the filtered transaction set
- Use a year-to-date measure with DATESYTD or an equivalent time-intelligence pattern
Explanation
Correct Answer
D:YTD accumulates the current calendar year's values up to the selected date. For the stated case, Use a year-to-date measure with DATESYTD or an equivalent time-intelligence pattern.
Incorrect Answers
A:This might be appropriate after a different requirement arises: The company's year ends June 30. It is not the best initial response to the stated case.
B:A rolling week is not the year's cumulative total. The proposed shortcut 'Add only the last seven days and call it year-to-date' fails the documented need.
C:This addresses a separate source situation: A report must count distinct customers who purchased during the selected period. It does not directly satisfy this case's priority.
Question 346
An executive wants cumulative revenue from January 1 through each selected day. A colleague proposes: Add only the last seven days and call it year-to-date. Which explanation BEST identifies the defect in that proposal?
- YTD accumulates the current calendar year's values up to the selected date
- A rolling week is not the year's cumulative total
- Repeated transaction lines overcount customers
- The suggested approach is safe merely because its product name is familiar.
Explanation
Correct Answer
B:A rolling week is not the year's cumulative total. This directly explains why the proposal 'Add only the last seven days and call it year-to-date' should not be used.
Incorrect Answers
A:This is reasoning supporting the preferred solution 'Use a year-to-date measure with DATESYTD or an equivalent time-intelligence pattern', but it does not directly name the defect in the proposed shortcut.
C:This addresses a different case: A report must count distinct customers who purchased during the selected period. It is not the specific defect in 'Add only the last seven days and call it year-to-date'.
D:Product familiarity is not evidence of suitability. The actual defect in this proposal is: A rolling week is not the year's cumulative total.
Question 347
An executive wants cumulative revenue from January 1 through each selected day. After implementing Use a year-to-date measure with DATESYTD or an equivalent time-intelligence pattern, which observation BEST demonstrates that the intended result is actually working?
- The team schedules a future check of whether The measure resets at the start of each calendar year, but has not observed a result.
- The report owner approves Use a year-to-date measure with DATESYTD or an equivalent time-intelligence pattern without testing the resulting behavior.
- The count matches the list of unique CustomerIDs after slicer filters
- The measure resets at the start of each calendar year
Explanation
Correct Answer
D:The observation 'The measure resets at the start of each calendar year' directly tests the intended result. YTD accumulates the current calendar year's values up to the selected date.
Incorrect Answers
A:A future test is not yet observed operational evidence. The verification must establish: The measure resets at the start of each calendar year.
B:Approval of a proposed design is not evidence of working behavior. The required observation is: The measure resets at the start of each calendar year.
C:This belongs to a different case: A report must count distinct customers who purchased during the selected period. It does not validate the current change.
Question 348
The original scenario was: An executive wants cumulative revenue from January 1 through each selected day. The initial solution is already in place. Now this new requirement arises: The company's year ends June 30. Which ADDITIONAL action BEST meets the changed condition?
- Set a supported fiscal year end or fiscal date logic
- Use a year-to-date measure with DATESYTD or an equivalent time-intelligence pattern
- The measure resets at the start of each calendar year
- Add only the last seven days and call it year-to-date
Explanation
Correct Answer
A:The changed requirement is 'The company's year ends June 30'. The additional response is 'Set a supported fiscal year end or fiscal date logic'.
Incorrect Answers
B:This is the already implemented original solution: Use a year-to-date measure with DATESYTD or an equivalent time-intelligence pattern. YTD accumulates the current calendar year's values up to the selected date. It does not itself solve the new requirement.
C:This observes the original approach but is not an additional action: The measure resets at the start of each calendar year.
D:This remains unsuitable for the original situation: A rolling week is not the year's cumulative total. It also does not meet the changed need.
Question 349
A finance report needs previous-month sales for each month on an axis. Which TWO entries together identify the most appropriate initial action and direct observed evidence of its success? (Select TWO.)
- Filter Sales by its row number instead of shifting calendar dates
- February's comparison returns the valid January sales period
- Use DATEADD on the marked date table with a one-month backward interval
- Use a semi-additive closing balance measure based on the last relevant date
- Use a rolling date window with AVERAGEX or a suitable average measure
Explanation
Correct Answers
B:Correct direct operational evidence. February's comparison returns the valid January sales period. This is a check of the original requirement, not an unperformed plan.
C:DATEADD shifts the date context for a period comparison. For the stated case, Use DATEADD on the marked date table with a one-month backward interval.
Incorrect Answers
A:Row position does not represent the previous calendar month. The proposed shortcut 'Filter Sales by its row number instead of shifting calendar dates' fails the documented need.
D:This addresses a separate source situation: A bank reports month-end account balances and must calculate annual balances without summing every day's snapshot. It does not directly satisfy this case's priority.
E:This might be appropriate after a different requirement arises: The business instead requests a moving three-month average. It is not the best initial response to the stated case.
Question 350
A finance report needs previous-month sales for each month on an axis. A colleague proposes: Filter Sales by its row number instead of shifting calendar dates. Which explanation BEST identifies the defect in that proposal?
- Adding snapshots over time overstates closing financial balances
- Row position does not represent the previous calendar month
- The suggested approach is safe merely because its product name is familiar.
- DATEADD shifts the date context for a period comparison
Explanation
Correct Answer
B:Row position does not represent the previous calendar month. This directly explains why the proposal 'Filter Sales by its row number instead of shifting calendar dates' should not be used.
Incorrect Answers
A:This addresses a different case: A bank reports month-end account balances and must calculate annual balances without summing every day's snapshot. It is not the specific defect in 'Filter Sales by its row number instead of shifting calendar dates'.
C:Product familiarity is not evidence of suitability. The actual defect in this proposal is: Row position does not represent the previous calendar month.
D:This is reasoning supporting the preferred solution 'Use DATEADD on the marked date table with a one-month backward interval', but it does not directly name the defect in the proposed shortcut.