Microsoft Power BI Data Analyst PL-300 Practice Test 20
Question 190
A legacy model contains Sales related bidirectionally to both Geography and Customer, plus another path between Geography and Customer, producing ambiguous filter results. A design reviewer proposes this alternative: Create multiple active alternate paths between the same tables. Which objection BEST explains why it would not satisfy the stated requirement?
- Competing active paths do not automatically resolve ambiguity or produce intended results
- Inactive paths break normal dimension filters rather than resolving the model design
- A clean star filter flow reduces ambiguous propagation paths and makes slicer behavior predictable
- Additional both-direction paths can increase ambiguity and affect performance
Explanation
Correct Answer
A:Competing active paths do not automatically resolve ambiguity or produce intended results This specifically addresses the deployed or proposed alternative: Create multiple active alternate paths between the same tables.
Incorrect Answers
B:Inactive paths break normal dimension filters rather than resolving the model design That limitation describes Turn every relationship inactive, not the specified approach.
C:A clean star filter flow reduces ambiguous propagation paths and makes slicer behavior predictable This supports the recommended design but does not diagnose why the specified alternative fails.
D:Additional both-direction paths can increase ambiguity and affect performance That limitation applies to a different alternative (Set every relationship to Both because more propagation always helps), not the one here.
Question 191
A DAX measure recalculates the same expensive filtered expression three times inside nested IF branches. Which Power BI or Power Query action BEST meets the stated requirement?
- Increase maximum visual interactions as a performance fix
- Store the repeated expression in a DAX VAR and reuse it within RETURN
- Copy the identical expensive expression into every IF branch
- Convert all calculated measures to imported text columns
Explanation
Correct Answer
B:Variables can avoid redundant evaluation and make measure logic easier to maintain This addresses the specific requirement: a DAX measure recalculates the same expensive filtered expression three times inside nested IF branches.
Incorrect Answers
A:More interactions do not remove redundant DAX expression logic This alternative therefore fails an explicit scenario constraint.
C:Duplicate expression text keeps the maintenance and possible evaluation cost This alternative therefore fails an explicit scenario constraint.
D:Text columns cannot replace context-sensitive numeric measure calculations This alternative therefore fails an explicit scenario constraint.
Question 192
A semantic model imported many unused high-cardinality transaction text columns and file size is excessive. A design reviewer proposes this alternative: Add another calculated copy of the unused columns. Which objection BEST explains why it would not satisfy the stated requirement?
- Additional calculated columns increase rather than reduce model memory
- A theme cannot reduce the semantic model's stored data volume
- Summarization settings do not remove cached high-cardinality data
- Fewer unnecessary distinct strings reduce storage and encoding overhead in Import models
Explanation
Correct Answer
A:Additional calculated columns increase rather than reduce model memory This specifically addresses the deployed or proposed alternative: Add another calculated copy of the unused columns.
Incorrect Answers
B:A theme cannot reduce the semantic model's stored data volume That limitation describes Change the report theme without altering the imported schema, not the specified approach.
C:Summarization settings do not remove cached high-cardinality data That limitation applies to a different alternative (Set every text column to Don't summarize), not the one here.
D:Fewer unnecessary distinct strings reduce storage and encoding overhead in Import models This supports the recommended design but does not diagnose why the specified alternative fails.
Question 193
A report must calculate actual average item price across mixed sales quantities, weighted by units sold rather than average invoice price. After the correct solution is implemented, which result provides the MOST DIRECT evidence that the requirement actually works?
- The field uses the expected numeric format, but no zero-denominator or date-boundary case was tested
- A manually calculated small sample with unequal quantities matches the weighted average measure
- The DAX expression parses and returns a number for one unfiltered report page
- The measure changes after a slicer click, but the result has not been compared against known test rows
Explanation
Correct Answer
B:A manually calculated small sample with unequal quantities matches the weighted average measure This exercises the requested business outcome and the necessary positive or negative boundary.
Incorrect Answers
A:Formatting and a normal case do not validate the edge condition the calculation is supposed to handle.
C:A valid DAX expression may still evaluate the wrong period, denominator or context under filters.
D:Reacting to a slicer does not establish the correct math or intended filter semantics.
Question 194
Sales has OrderDate and ShipDate columns but business users need two independent date slicers, one for order month and one for ship month. A pilot instead implemented the following proposed change: Use one Date dimension linked actively to both fact date columns. The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- Multiple active ambiguous paths between the same tables cannot normally be created
- Independent date roles let two slicers filter their corresponding fact dates simultaneously
- Product membership does not supply separate order and shipment calendar roles
- One active relationship follows one date role, not the independent second role
Explanation
Correct Answer
A:Multiple active ambiguous paths between the same tables cannot normally be created This specifically addresses the deployed or proposed alternative: Use one Date dimension linked actively to both fact date columns.
Incorrect Answers
B:Independent date roles let two slicers filter their corresponding fact dates simultaneously This supports the recommended design but does not diagnose why the specified alternative fails.
C:Product membership does not supply separate order and shipment calendar roles That limitation describes Use a Product dimension with duplicated calendar dates, not the specified approach.
D:One active relationship follows one date role, not the independent second role That limitation applies to a different alternative (Use one active date relationship and expect it to filter both date columns), not the one here.
Question 195
A monthly table displays a numerical total but the analyst wants a simple percentage-of-grand-total measure without manually building complex DAX. After the correct solution is implemented, which result provides the MOST DIRECT evidence that the requirement actually works?
- The measure changes after a slicer click, but the result has not been compared against known test rows
- The generated measure produces row shares that sum to the intended displayed total under supported filter context
- The field uses the expected numeric format, but no zero-denominator or date-boundary case was tested
- The DAX expression parses and returns a number for one unfiltered report page
Explanation
Correct Answer
B:The generated measure produces row shares that sum to the intended displayed total under supported filter context This exercises the requested business outcome and the necessary positive or negative boundary.
Incorrect Answers
A:Reacting to a slicer does not establish the correct math or intended filter semantics.
C:Formatting and a normal case do not validate the edge condition the calculation is supposed to handle.
D:A valid DAX expression may still evaluate the wrong period, denominator or context under filters.
Question 196
A product table is used to calculate a row-level category key at refresh rather than a slicer-dependent aggregate; it must participate in a relationship. Which Power BI or Power Query action BEST meets the stated requirement?
- Create only a DAX measure returning the category for each row
- Create a calculated column or Power Query column containing the row-level category key
- Place category text in a report subtitle
- Build an unrelated what-if parameter to store category
Explanation
Correct Answer
B:A persisted per-row attribute can participate as a relationship key after materialization This addresses the specific requirement: a product table is used to calculate a row-level category key at refresh rather than a slicer-dependent aggregate; it must participate in a relationship.
Incorrect Answers
A:A measure produces a context-dependent scalar and cannot be a normal relationship key column This alternative therefore fails an explicit scenario constraint.
C:A subtitle is a visual label rather than a data model column This alternative therefore fails an explicit scenario constraint.
D:A parameter is not a row-by-row category assignment for relationship matching This alternative therefore fails an explicit scenario constraint.
Question 197
A Category dimension contains duplicate CategoryKey values due to source errors, and Power BI refuses to create the intended one-to-many relationship to Sales. After the correct solution is implemented, which result provides the MOST DIRECT evidence that the requirement actually works?
- The model saves successfully, but source keys and report totals have not been reconciled
- The relationship diagram displays a line between tables, but no matching-key uniqueness test has run
- CategoryKey is unique in the dimension and the relationship creates with valid one-to-many cardinality
- One aggregate value is nonblank, but filtering has not been tested from each intended dimension
Explanation
Correct Answer
C:CategoryKey is unique in the dimension and the relationship creates with valid one-to-many cardinality This exercises the requested business outcome and the necessary positive or negative boundary.
Incorrect Answers
A:Saving a model does not rule out duplicate dimension rows, ambiguous paths or fact multiplication.
B:A visible relationship is not proof that the dimension key and relationship cardinality are valid.
D:An unfiltered total cannot establish that the model's date roles and cross-filter paths behave as specified.
Question 198
A DAX measure recalculates the same expensive filtered expression three times inside nested IF branches. A pilot instead implemented the following proposed change: Copy the identical expensive expression into every IF branch. The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- More interactions do not remove redundant DAX expression logic
- Variables can avoid redundant evaluation and make measure logic easier to maintain
- Duplicate expression text keeps the maintenance and possible evaluation cost
- Text columns cannot replace context-sensitive numeric measure calculations
Explanation
Correct Answer
C:Duplicate expression text keeps the maintenance and possible evaluation cost This specifically addresses the deployed or proposed alternative: Copy the identical expensive expression into every IF branch.
Incorrect Answers
A:More interactions do not remove redundant DAX expression logic That limitation describes Increase maximum visual interactions as a performance fix, not the specified approach.
B:Variables can avoid redundant evaluation and make measure logic easier to maintain This supports the recommended design but does not diagnose why the specified alternative fails.
D:Text columns cannot replace context-sensitive numeric measure calculations That limitation applies to a different alternative (Convert all calculated measures to imported text columns), not the one here.
Question 199
A DirectQuery report becomes slow because Power Query transformations cause large source tables to be processed locally before filtering. A pilot instead implemented the following proposed change: Buffer the whole source immediately and filter afterward. The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- Formatting does not reduce data movement caused by nonfoldable source transformations
- Nonfoldable steps can prevent efficient server-side query execution
- Maintaining folding can let the source execute selective predicates before transferring large data
- Early materialization can defeat source-side predicate pushdown
Explanation
Correct Answer
D:Early materialization can defeat source-side predicate pushdown This specifically addresses the deployed or proposed alternative: Buffer the whole source immediately and filter afterward.
Incorrect Answers
A:Formatting does not reduce data movement caused by nonfoldable source transformations That limitation describes Use a measure that only changes result formatting, not the specified approach.
B:Nonfoldable steps can prevent efficient server-side query execution That limitation applies to a different alternative (Add unnecessary custom per-row transformations before source filters), not the one here.
C:Maintaining folding can let the source execute selective predicates before transferring large data This supports the recommended design but does not diagnose why the specified alternative fails.
Question 200
A product manager wants the same quarter last year compared with the selected quarter this year using a contiguous marked date table. A pilot instead implemented the following proposed change: Use TOTALYTD([Total Revenue], Date[Date]). The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- Year-to-date accumulation is not the comparable prior-year quarter
- The first date is not a revenue amount for last year's quarter
- The prior-year date-shift table evaluates revenue for corresponding dates one year earlier
- Removing all date filters does not shift to the preceding year
Explanation
Correct Answer
A:Year-to-date accumulation is not the comparable prior-year quarter This specifically addresses the deployed or proposed alternative: Use TOTALYTD([Total Revenue], Date[Date]).
Incorrect Answers
B:The first date is not a revenue amount for last year's quarter That limitation applies to a different alternative (Use FIRSTDATE(Date[Date]) as the measure result), not the one here.
C:The prior-year date-shift table evaluates revenue for corresponding dates one year earlier This supports the recommended design but does not diagnose why the specified alternative fails.
D:Removing all date filters does not shift to the preceding year That limitation describes Use ALL(Date) to erase current date filters, not the specified approach.