Microsoft PL-300 Practice Test 25
Question 240
The original scenario was: A shipping KPI must calculate Sales Amount by ShipDate although the active Calendar link uses OrderDate. The initial solution is already in place. Now this new requirement arises: A new interactive page needs two distinct date slicers at once. Which ADDITIONAL action BEST meets the changed condition?
- Use CALCULATE with USERELATIONSHIP for the ShipDate measure
- Add role-playing Order and Ship date dimension tables
- The shipping measure responds to the calendar through Sales ShipDate without changing regular revenue
- Disable the OrderDate model relationship permanently for every sales measure
Explanation
Correct Answer
B:The changed requirement is 'A new interactive page needs two distinct date slicers at once'. The additional response is 'Add role-playing Order and Ship date dimension tables'.
Incorrect Answers
A:This is the already implemented original solution: Use CALCULATE with USERELATIONSHIP for the ShipDate measure. USERELATIONSHIP activates an existing inactive relationship during a calculation. It does not itself solve the new requirement.
C:This observes the original approach but is not an additional action: The shipping measure responds to the calendar through Sales ShipDate without changing regular revenue.
D:This remains unsuitable for the original situation: Changing the global active relationship breaks ordinary order-date analyses. It also does not meet the changed need.
Question 241
Time-intelligence DAX fails because the date field contains gaps and duplicate timestamps. Which approach BEST meets the stated Microsoft Power BI requirement?
- Create a proper contiguous date table and mark it as the Date table
- Mark a fact's duplicate transaction timestamp column as the Date table
- Add fiscal attributes and use fiscal-aware calendar logic
- Define a measure for SUM of the Sales amount
Explanation
Correct Answer
A:A marked date table needs appropriate unique contiguous date values for standard calendar calculations. For the stated case, Create a proper contiguous date table and mark it as the Date table.
Incorrect Answers
B:Duplicated granular timestamps do not meet date-dimension requirements. The proposed shortcut 'Mark a fact's duplicate transaction timestamp column as the Date table' fails the documented need.
C:This might be appropriate after a different requirement arises: Fiscal-year reporting starts in July instead of January. It is not the best initial response to the stated case.
D:This addresses a separate source situation: An enterprise wants Sales amount to aggregate over selected filters while the stored row-level SaleValue remains a table column. It does not directly satisfy this case's priority.
Question 242
Time-intelligence DAX fails because the date field contains gaps and duplicate timestamps. A colleague proposes: Mark a fact's duplicate transaction timestamp column as the Date table. Which explanation BEST identifies the defect in that proposal?
- The suggested approach is safe merely because its product name is familiar.
- A repeated static total does not behave as a filtered measure
- Duplicated granular timestamps do not meet date-dimension requirements
- A marked date table needs appropriate unique contiguous date values for standard calendar calculations
Explanation
Correct Answer
C:Duplicated granular timestamps do not meet date-dimension requirements. This directly explains why the proposal 'Mark a fact's duplicate transaction timestamp column as the Date table' should not be used.
Incorrect Answers
A:Product familiarity is not evidence of suitability. The actual defect in this proposal is: Duplicated granular timestamps do not meet date-dimension requirements.
B:This addresses a different case: An enterprise wants Sales amount to aggregate over selected filters while the stored row-level SaleValue remains a table column. It is not the specific defect in 'Mark a fact's duplicate transaction timestamp column as the Date table'.
D:This is reasoning supporting the preferred solution 'Create a proper contiguous date table and mark it as the Date table', but it does not directly name the defect in the proposed shortcut.
Question 243
Time-intelligence DAX fails because the date field contains gaps and duplicate timestamps. After implementing Create a proper contiguous date table and mark it as the Date table, which observation BEST demonstrates that the intended result is actually working?
- The marked Calendar has one row per date and time calculations evaluate correctly
- The measure changes when customers or months are selected
- The report owner approves Create a proper contiguous date table and mark it as the Date table without testing the resulting behavior.
- The team schedules a future check of whether The marked Calendar has one row per date and time calculations evaluate correctly, but has not observed a result.
Explanation
Correct Answer
A:The observation 'The marked Calendar has one row per date and time calculations evaluate correctly' directly tests the intended result. A marked date table needs appropriate unique contiguous date values for standard calendar calculations.
Incorrect Answers
B:This belongs to a different case: An enterprise wants Sales amount to aggregate over selected filters while the stored row-level SaleValue remains a table column. It does not validate the current change.
C:Approval of a proposed design is not evidence of working behavior. The required observation is: The marked Calendar has one row per date and time calculations evaluate correctly.
D:A future test is not yet observed operational evidence. The verification must establish: The marked Calendar has one row per date and time calculations evaluate correctly.
Question 244
The original scenario was: Time-intelligence DAX fails because the date field contains gaps and duplicate timestamps. The initial solution is already in place. Now this new requirement arises: Fiscal-year reporting starts in July instead of January. Which ADDITIONAL action BEST meets the changed condition?
- Add fiscal attributes and use fiscal-aware calendar logic
- Create a proper contiguous date table and mark it as the Date table
- The marked Calendar has one row per date and time calculations evaluate correctly
- Mark a fact's duplicate transaction timestamp column as the Date table
Explanation
Correct Answer
A:The changed requirement is 'Fiscal-year reporting starts in July instead of January'. The additional response is 'Add fiscal attributes and use fiscal-aware calendar logic'.
Incorrect Answers
B:This is the already implemented original solution: Create a proper contiguous date table and mark it as the Date table. A marked date table needs appropriate unique contiguous date values for standard calendar calculations. It does not itself solve the new requirement.
C:This observes the original approach but is not an additional action: The marked Calendar has one row per date and time calculations evaluate correctly.
D:This remains unsuitable for the original situation: Duplicated granular timestamps do not meet date-dimension requirements. It also does not meet the changed need.
Question 245
Users select MonthName and see April before February because names sort alphabetically. Which approach BEST meets the stated Microsoft Power BI requirement?
- Fix or replace the Products table with a unique ProductID dimension
- Set MonthName to Sort by Column using a numeric MonthNumber
- Provide a fiscal month index and assign that as the sort key
- Rename the months with leading letters to force the order
Explanation
Correct Answer
B:Sort by Column lets readable labels follow a numeric calendar order. For the stated case, Set MonthName to Sort by Column using a numeric MonthNumber.
Incorrect Answers
A:This addresses a separate source situation: A company's sales model has a product table with repeated ProductIDs and cannot establish a one-to-many relationship. It does not directly satisfy this case's priority.
C:This might be appropriate after a different requirement arises: The business needs month ordering across several fiscal calendars. It is not the best initial response to the stated case.
D:Arbitrary text naming is not robust numeric calendar sorting. The proposed shortcut 'Rename the months with leading letters to force the order' fails the documented need.
Question 246
Users select MonthName and see April before February because names sort alphabetically. A colleague proposes: Rename the months with leading letters to force the order. Which explanation BEST identifies the defect in that proposal?
- Arbitrary text naming is not robust numeric calendar sorting
- Many-to-many may conceal a data-quality problem and create ambiguous totals
- The suggested approach is safe merely because its product name is familiar.
- Sort by Column lets readable labels follow a numeric calendar order
Explanation
Correct Answer
A:Arbitrary text naming is not robust numeric calendar sorting. This directly explains why the proposal 'Rename the months with leading letters to force the order' should not be used.
Incorrect Answers
B:This addresses a different case: A company's sales model has a product table with repeated ProductIDs and cannot establish a one-to-many relationship. It is not the specific defect in 'Rename the months with leading letters to force the order'.
C:Product familiarity is not evidence of suitability. The actual defect in this proposal is: Arbitrary text naming is not robust numeric calendar sorting.
D:This is reasoning supporting the preferred solution 'Set MonthName to Sort by Column using a numeric MonthNumber', but it does not directly name the defect in the proposed shortcut.
Question 247
Users select MonthName and see April before February because names sort alphabetically. After implementing Set MonthName to Sort by Column using a numeric MonthNumber, which observation BEST demonstrates that the intended result is actually working?
- The team schedules a future check of whether A month slicer follows January through December rather than alphabetic names, but has not observed a result.
- A month slicer follows January through December rather than alphabetic names
- The report owner approves Set MonthName to Sort by Column using a numeric MonthNumber without testing the resulting behavior.
- ProductIDs become unique and an ordinary one-to-many relationship validates
Explanation
Correct Answer
B:The observation 'A month slicer follows January through December rather than alphabetic names' directly tests the intended result. Sort by Column lets readable labels follow a numeric calendar order.
Incorrect Answers
A:A future test is not yet observed operational evidence. The verification must establish: A month slicer follows January through December rather than alphabetic names.
C:Approval of a proposed design is not evidence of working behavior. The required observation is: A month slicer follows January through December rather than alphabetic names.
D:This belongs to a different case: A company's sales model has a product table with repeated ProductIDs and cannot establish a one-to-many relationship. It does not validate the current change.
Question 248
The original scenario was: Users select MonthName and see April before February because names sort alphabetically. The initial solution is already in place. Now this new requirement arises: The business needs month ordering across several fiscal calendars. Which ADDITIONAL action BEST meets the changed condition?
- Rename the months with leading letters to force the order
- Provide a fiscal month index and assign that as the sort key
- A month slicer follows January through December rather than alphabetic names
- Set MonthName to Sort by Column using a numeric MonthNumber
Explanation
Correct Answer
B:The changed requirement is 'The business needs month ordering across several fiscal calendars'. The additional response is 'Provide a fiscal month index and assign that as the sort key'.
Incorrect Answers
A:This remains unsuitable for the original situation: Arbitrary text naming is not robust numeric calendar sorting. It also does not meet the changed need.
C:This observes the original approach but is not an additional action: A month slicer follows January through December rather than alphabetic names.
D:This is the already implemented original solution: Set MonthName to Sort by Column using a numeric MonthNumber. Sort by Column lets readable labels follow a numeric calendar order. It does not itself solve the new requirement.
Question 249
An enterprise wants Sales amount to aggregate over selected filters while the stored row-level SaleValue remains a table column. Which approach BEST meets the stated Microsoft Power BI requirement?
- Use a calculated column where persistent per-row classification is appropriate
- Create a calculated text column that repeats the entire report's grand total on each row
- Define a measure for SUM of the Sales amount
- Create a one-to-many relationship from Products to Sales
Explanation
Correct Answer
C:Measures evaluate in the current filter context and suit dynamic aggregations. For the stated case, Define a measure for SUM of the Sales amount.
Incorrect Answers
A:This might be appropriate after a different requirement arises: Pricing must be stored as a fixed row-level classification for every product. It is not the best initial response to the stated case.
B:A repeated static total does not behave as a filtered measure. The proposed shortcut 'Create a calculated text column that repeats the entire report's grand total on each row' fails the documented need.
D:This addresses a separate source situation: The Sales table has many transactions per ProductKey and Products has one row per ProductKey. It does not directly satisfy this case's priority.
Question 250
An enterprise wants Sales amount to aggregate over selected filters while the stored row-level SaleValue remains a table column. A colleague proposes: Create a calculated text column that repeats the entire report's grand total on each row. Which explanation BEST identifies the defect in that proposal?
- Incorrect cardinality contradicts the key uniqueness required on the One side
- The suggested approach is safe merely because its product name is familiar.
- A repeated static total does not behave as a filtered measure
- Measures evaluate in the current filter context and suit dynamic aggregations
Explanation
Correct Answer
C:A repeated static total does not behave as a filtered measure. This directly explains why the proposal 'Create a calculated text column that repeats the entire report's grand total on each row' should not be used.
Incorrect Answers
A:This addresses a different case: The Sales table has many transactions per ProductKey and Products has one row per ProductKey. It is not the specific defect in 'Create a calculated text column that repeats the entire report's grand total on each row'.
B:Product familiarity is not evidence of suitability. The actual defect in this proposal is: A repeated static total does not behave as a filtered measure.
D:This is reasoning supporting the preferred solution 'Define a measure for SUM of the Sales amount', but it does not directly name the defect in the proposed shortcut.