100% Latest & Updated Microsoft PL-300 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 270
A sales model needs revenue from multiplying each line's quantity by price. The selected approach is: Use SUMX for a row-wise expression before aggregating. Which implementation step puts it into practice?
- Define SUMX(Sales, Sales[Quantity] * Sales[UnitPrice]).
- Wrap the CALCULATE filter argument with KEEPFILTERS.
- Use CALCULATE([Revenue], REMOVEFILTERS(Product)) for the denominator.
- Create a calculated column = RELATED(Product[Category]) with the relationship present.
Explanation
Correct Answer
A:Per-row multiplication occurs before aggregation; multiplying column sums would differ.
Incorrect Answers
B:The measure should narrow rather than overwrite an existing selection. It does not implement the needed solution: use sumx for a row-wise expression before aggregating.
C:The Product selection is ignored for the total while other filters remain. It does not implement the needed solution: use sumx for a row-wise expression before aggregating.
D:Row context plus relationship allows lookup of dimension values. It does not implement the needed solution: use sumx for a row-wise expression before aggregating.
Question 271
A fact table stores Quantity and UnitPrice but not a precomputed line amount. The chosen solution is: Use SUMX for a row-wise expression before aggregating. Which verification best demonstrates that it meets the requirement?
- Compare query results and execution characteristics consistently.
- Test the derived attribute against sample source rows.
- Measure model size and refresh duration after pruning.
- Compare to invoice line extensions under multiple filters.
Explanation
Correct Answer
D:Correct totals reflect line-level arithmetic.
Incorrect Answers
A:Speed improvements cannot change correct business values. That check does not verify the result required here: compare to invoice line extensions under multiple filters.
B:Row-level classification should be reproducible. That check does not verify the result required here: compare to invoice line extensions under multiple filters.
C:Smaller data should not change required report values. That check does not verify the result required here: compare to invoice line extensions under multiple filters.
Question 272
A fact table stores Quantity and UnitPrice but not a precomputed line amount. A specific ongoing problem has appeared: An expensive iterator over unnecessary granularity can slow visuals. Which safeguard most directly addresses it?
- Review filter paths before enabling bidirectional relationships.
- Review relationship diagrams whenever the model changes.
- Refresh and validate the date table range for the reporting horizon.
- Optimize row grain and avoid repeated costly iterator work.
Explanation
Correct Answer
D:Iterators may be more expensive than simple storage-engine aggregations.
Incorrect Answers
A:Both directions can introduce unexpected ambiguity and performance costs; iterators may be more expensive than simple storage-engine aggregations.
B:Model structure is central to DAX correctness. Iterators may be more expensive than simple storage-engine aggregations.
C:Coverage must include all required periods; iterators may be more expensive than simple storage-engine aggregations.
Question 273
A dashboard needs the same period sales one month before the currently selected calendar dates. Which Power BI approach most directly satisfies this requirement?
- Use SUMX for a row-wise expression before aggregating.
- Use VAR and RETURN to name reusable intermediate values.
- Use DATEADD for a shifted date-filter context.
- Use a semi-additive last-observation measure over dates.
Explanation
Correct Answer
C:DATEADD shifts a valid date selection for time comparison.
Incorrect Answers
A:SUMX iterates visible rows and sums an expression evaluated for each row. DATEADD shifts a valid date selection for time comparison.
B:Variables make measures easier to read and can avoid repeated computation; DATEADD shifts a valid date selection for time comparison.
D:Snapshot values may aggregate across entities but not across time; DATEADD shifts a valid date selection for time comparison.
Question 274
A finance team compares the selected month to its previous month on a proper continuous date table. The selected approach is: Use DATEADD for a shifted date-filter context. Which implementation step puts it into practice?
- Define CALCULATE([Sales], DATEADD('Date'[Date], -1, MONTH)).
- Assign meaningful variables before the RETURN expression.
- Create a calculated column = RELATED(Product[Category]) with the relationship present.
- Create appropriate calculation items using SELECTEDMEASURE and time filters.
Explanation
Correct Answer
A:The date table and relationship must be suitable for the intended periods.
Incorrect Answers
B:The final result can reuse scalar or table values consistently. It does not implement the needed solution: use dateadd for a shifted date-filter context.
C:Row context plus relationship allows lookup of dimension values. It does not implement the needed solution: use dateadd for a shifted date-filter context.
D:Reusable items can apply to many base measures when configured correctly. It does not implement the needed solution: use dateadd for a shifted date-filter context.
Question 275
A dashboard needs the same period sales one month before the currently selected calendar dates. The chosen solution is: Use DATEADD for a shifted date-filter context. Which TWO actions together implement this approach and provide evidence that it works? Choose TWO.
- Define CALCULATE([Sales], DATEADD('Date'[Date], -1, MONTH)).
- Compare the measure with known prior-month totals.
- Verify each fact row maps to the expected calendar day.
- Assign meaningful variables before the RETURN expression.
- Filter one product and reconcile fact rows and sums.
Explanation
Correct Answers
A:The date table and relationship must be suitable for the intended periods.
B:It should align period filters with the shifted interval.
Incorrect Answers
C:Date joins must preserve correct day boundaries. That check does not verify the result required here: compare the measure with known prior-month totals.
D:The final result can reuse scalar or table values consistently. It does not implement the needed solution: use dateadd for a shifted date-filter context.
E:The relationship should propagate the intended product filter to sales. That check does not verify the result required here: compare the measure with known prior-month totals.
Question 276
A dashboard needs the same period sales one month before the currently selected calendar dates. A specific ongoing problem has appeared: Gaps or incorrect calendars may misalign shifted dates. Which safeguard most directly addresses it?
- Review filter paths before enabling bidirectional relationships.
- Keep a governed detailed source separately if deeper drilldown is required.
- Maintain a continuous marked date table and calendar assumptions.
- Validate measure equivalence as well as execution performance.
Explanation
Correct Answer
C:Time intelligence needs reliable date semantics.
Incorrect Answers
A:Both directions can introduce unexpected ambiguity and performance costs; time intelligence needs reliable date semantics.
B:Granularity reduction trades detail for performance. Time intelligence needs reliable date semantics.
D:Performance improvements must preserve semantics. Time intelligence needs reliable date semantics.
Question 277
A CFO needs revenue accumulated from January 1 through the selected reporting date. Which Power BI approach most directly satisfies this requirement?
- Use DISTINCTCOUNT on the intended business identifier.
- Use COUNTROWS to count table records.
- Use TOTALYTD or an equivalent DAX time-intelligence expression.
- Use VAR and RETURN to name reusable intermediate values.
Explanation
Correct Answer
C:Year-to-date accumulation must honor reporting dates and year-end rules.
Incorrect Answers
A:DISTINCTCOUNT avoids treating multiple line rows as separate business entities. Year-to-date accumulation must honor reporting dates and year-end rules.
B:COUNTROWS counts rows in the visible table regardless of a particular column's blank values; year-to-date accumulation must honor reporting dates and year-end rules.
D:Variables make measures easier to read and can avoid repeated computation; year-to-date accumulation must honor reporting dates and year-end rules.
Question 278
An operations manager wants a year-to-date cost measure resetting at the proper year boundary. The selected approach is: Use TOTALYTD or an equivalent DAX time-intelligence expression. Which implementation step puts it into practice?
- Define TOTALYTD([Sales], 'Date'[Date]) for a calendar year.
- Wrap the CALCULATE filter argument with KEEPFILTERS.
- Create appropriate calculation items using SELECTEDMEASURE and time filters.
- Create a calculated column = RELATED(Product[Category]) with the relationship present.
Explanation
Correct Answer
A:The function accumulates from year start through current date context.
Incorrect Answers
B:The measure should narrow rather than overwrite an existing selection. It does not implement the needed solution: use totalytd or an equivalent dax time-intelligence expression.
C:Reusable items can apply to many base measures when configured correctly. It does not implement the needed solution: use totalytd or an equivalent dax time-intelligence expression.
D:Row context plus relationship allows lookup of dimension values. It does not implement the needed solution: use totalytd or an equivalent dax time-intelligence expression.
Question 279
A CFO needs revenue accumulated from January 1 through the selected reporting date. The chosen solution is: Use TOTALYTD or an equivalent DAX time-intelligence expression. Which verification best demonstrates that it meets the requirement?
- Inspect query folding and compare refresh time after the change.
- Compare results when filtering order date versus ship date.
- Test counts across students, courses and unique memberships.
- Check January reset and December accumulated totals.
Explanation
Correct Answer
D:A YTD measure should reset at the correct boundary.
Incorrect Answers
A:Folded filters should improve refresh efficiency. That check does not verify the result required here: check january reset and december accumulated totals.
B:A correct model returns role-specific totals. That check does not verify the result required here: check january reset and december accumulated totals.
C:Relationships must not multiply memberships when filtering. That check does not verify the result required here: check january reset and december accumulated totals.
Question 280
A CFO needs revenue accumulated from January 1 through the selected reporting date. A specific ongoing problem has appeared: A fiscal-year company could use a different year-end date. Which safeguard most directly addresses it?
- Retain necessary iterators for true row-level arithmetic.
- Keep grains and filter paths documented and unambiguous.
- Specify the correct fiscal year end in time calculations.
- Maintain a documented required-column contract for reports.
Explanation
Correct Answer
C:Wrong year-end definitions misstate YTD figures.
Incorrect Answers
A:Do not sacrifice correctness for superficial expression simplicity; wrong year-end definitions misstate YTD figures.
B:Conformed dimensions enable reliable comparisons. Wrong year-end definitions misstate YTD figures.
D:Model optimization should not remove necessary business attributes. Wrong year-end definitions misstate YTD figures.
Microsoft Power BI Data Analyst (PL-300) Practice Tests