Microsoft PL-300 Practice Test 36

Question 350

A Customer table includes inactive customers and a KPI must count only Active rows. Which implementation best addresses this scenario?

Use COUNTROWS(DeliveryLines) in the required context.
Use CALCULATE(COUNTROWS(Customer),Customer[Status] = "Active").
Calculate DISTINCTCOUNT(UserActivity[UserID]) for the whole month context.
Use DISTINCTCOUNT(Sales[CustomerID]) under month filter context.

Explanation

Correct Answer

The status filter constrains the rows included in the count, supporting active customer master count.

Incorrect Answers

Row counting preserves multiple lines per shipment as separate events. It would address number of delivery line events, not active customer master count.

Repeated users must be deduplicated across the combined period. It may suit avoid duplicated cross-day distinct users, not active customer master count.

DISTINCTCOUNT counts unique IDs in the active date filter. It is useful for unique monthly buyers, not for active customer master count.

Question 351

A score is computed as a weighted contribution per assessment and needs a final sum. What is the best method for this analysis requirement?

Use SUMX(Sales,Sales[Quantity] * Sales[UnitPrice]).
Use SUMX over the eligible rows with an appropriate positive-variance expression.
Use SUMX(Assessments,Assessments[Weight] * Assessments[Score]).
Replace the product of sums with SUMX at the intended transaction grain.

Explanation

Correct Answer

SUMX evaluates product expressions for each row before aggregating, supporting weighted aggregate assessment score.

Incorrect Answers

Row iteration multiplies values before summing, unlike separate sums. It is useful for revenue from row-level quantity-times-price, not for weighted aggregate assessment score.

Row-by-row filtering and aggregation can keep positive contributions only. Its scope is sum positive line-level variances, not weighted aggregate assessment score.

Product of aggregates is not the same as sum of per-row products. It would address correct line-extended revenue calculation, not weighted aggregate assessment score.

Question 352

A report measure needs Sales filtered by a Product[Category] slicer rather than copied columns. Which implementation best addresses this scenario?

Fix the relationship and unique lookup key rather than applying arbitrary first-row lookup.
Use RELATED(Product[Brand]) in the Sales row context.
Use COUNTROWS(RELATEDTABLE(Orders)) in the customer row context.
Use the model's active Product-to-Sales relationship with a measure.

Explanation

Correct Answer

Model relationships transfer filter context from dimension to fact, supporting category-filtered aggregate without fact column copy.

Incorrect Answers

RELATED assumes a singular related lookup row for the evaluated fact. It would address reliable dimension lookup under key uniqueness, not category-filtered aggregate without fact column copy.

RELATED retrieves an attribute on the relationship's one side. That targets add a related brand to sales line, not category-filtered aggregate without fact column copy.

RELATEDTABLE returns the set of related many-side rows for the current dimension row. It may suit per-customer related order count, not category-filtered aggregate without fact column copy.

Question 353

A label needs to distinguish a context with one Department from multiple departments. What is the best method for this analysis requirement?

Use HASONEVALUE(Department[Name]) to branch label logic.
Use SELECTEDVALUE('Date'[Year],"Multiple") for the indicator.
Use SELECTEDVALUE(Region[Name],"All Regions") in a title measure.
Use SELECTEDVALUE(Currency[Code]) and handle its blank result.

Explanation

Correct Answer

HASONEVALUE tests the distinct value count in the current context; this helps detect single-department filter context.

Incorrect Answers

SELECTEDVALUE defines a clear alternate when context is not singular. Its scope is display selected-year ambiguity safely, not detect single-department filter context.

SELECTEDVALUE returns a scalar only when one distinct value is visible. That is meant for dynamic report title with single-value fallback, not detect single-department filter context.

A missing or multiple currency selection yields blank unless an alternate is specified. It would address unambiguous reporting-currency selection, not detect single-department filter context.

Question 354

A product rank should return BLANK for a category with no eligible revenue instead of a misleading low rank. Which implementation best addresses this scenario?

Use an ALL-based comparison Store set in RANKX where that business definition is intended.
Wrap the RANKX result in a blank-measure guard.
Use a measure-based rank or Top N visual filter with the correct comparison set.
Use RANKX over an appropriate ALLSELECTED Store set with [Revenue].

Explanation

Correct Answer

Explicit blank handling avoids ranking missing observations as actual low performers, supporting omit ranks for missing business values.

Incorrect Answers

An ALL comparison universe removes specified filters rather than using only selected peers. It would address global branch rank independent of branch slicer, not omit ranks for missing business values.

Dynamic ranking updates when date or geographic filters change. It may suit selection-responsive top-ten products, not omit ranks for missing business values.

RANKX compares values across an explicitly defined comparison table. It is useful for store revenue ranking among selected peers, not for omit ranks for missing business values.

Question 355

A measure combines a current Customer segment slicer with a second allowed segment predicate and should intersect them. What is the best method for this analysis requirement?

Use CALCULATE([Sales],REMOVEFILTERS(Product[Brand])).
Use CALCULATE(COUNTROWS(Cases),Cases[Status]="Closed").
Use KEEPFILTERS for the added Customer segment condition.
Use CALCULATE([Sales],USERELATIONSHIP('Date'[Date],Sales[DeliveryDate])).

Explanation

Correct Answer

KEEPFILTERS narrows existing context instead of replacing compatible selected values, supporting additive filter intersection rather than overwrite.

Incorrect Answers

Removing a targeted column filter leaves unrelated Country context intact. It is useful for brand-independent totals within selected country, not for additive filter intersection rather than overwrite.

CALCULATE evaluates the expression under an added status condition. Its scope is filtered closed-case count, not additive filter intersection rather than overwrite.

USERELATIONSHIP changes the active path only for the calculation scope. It would address calculate revenue by alternate delivery date, not additive filter intersection rather than overwrite.

Question 356

A model adds a calculation group and existing measure formats display incorrectly for percentage and currency metrics. Which implementation best addresses this scenario?

Use a calculation group where dynamic measure transformation is the requirement.
Create a time-intelligence calculation group with a YTD calculation item.
Use separate calculation items referencing SELECTEDMEASURE and context shifts.
Configure an appropriate dynamic format string expression for calculation items.

Explanation

Correct Answer

Dynamic formats preserve expected unit and percent presentation across transformed measures; this helps correct formatting of transformed measures.

Incorrect Answers

Calculation groups operate on measures rather than materializing repeated per-row columns. It would address avoid duplicating columns for dynamic period calculations, not correct formatting of transformed measures.

Calculation items can transform SELECTEDMEASURE across eligible base measures. That targets reuse YTD behavior across many measures, not correct formatting of transformed measures.

Calculation items centralize recurring measure transformations. It may suit central reusable period comparisons, not correct formatting of transformed measures.

Question 357

A complex nonstandard fiscal time calculation cannot be expressed accurately by an available quick template. What is the best method for this analysis requirement?

Author and validate an explicit DAX measure for the custom fiscal rule.
Examine the generated DAX and check the new filter context rather than trusting the template.
Use a supported Quick measure running-total template, then inspect its DAX.
Use the supported Quick measure percentage-of-total operation.

Explanation

Correct Answer

Direct DAX is required when a business definition exceeds supplied templates, supporting precise custom fiscal-period calculation.

Incorrect Answers

Generated formulas depend on model relationships and business grain. Its scope is debug Quick measure filter-context assumptions, not precise custom fiscal-period calculation.

Quick measures generate standard patterns that still require business validation. That is meant for bootstrap a standard cumulative calculation, not precise custom fiscal-period calculation.

Quick measures assemble common denominator and context expressions. It would address generate an initial share-of-total pattern, not precise custom fiscal-period calculation.

Question 358

An analyst needs standard deviation of a sample of observed delivery durations. Which implementation best addresses this scenario?

Use a supported PERCENTILEX or PERCENTILE function with correct interpolation.
Use STDEV.S or an appropriate sample-standard-deviation DAX pattern.
Use AVERAGE over the fact's numeric amount column.
Use MEDIAN or MEDIANX over eligible transaction values.

Explanation

Correct Answer

Sample standard deviation estimates variability from sampled observations, supporting sample delivery-time dispersion.

Incorrect Answers

Percentile expressions summarize a specified point in the numeric distribution. It would address selected-context high latency percentile, not sample delivery-time dispersion.

AVERAGE computes the arithmetic mean of nonblank values in context. It may suit mean transaction amount, not sample delivery-time dispersion.

Median computes the middle observation and reduces sensitivity to extremes. It is useful for median transaction amount, not for sample delivery-time dispersion.

Question 359

A report title should show '(none)' if its dynamic category selection is blank. What is the best method for this analysis requirement?

Use COALESCE([Sales],0) in a display measure.
Use DIVIDE([Numerator],[Denominator],BLANK()).
Use COALESCE(SELECTEDVALUE(Category[Name]),"(none)").
Preserve BLANK and annotate missing-data state instead of unconditional COALESCE.

Explanation

Correct Answer

COALESCE can supply a fallback for blank selected values, supporting display fallback for missing selected category.

Incorrect Answers

COALESCE returns the first nonblank expression, making zero substitution deliberate. It is useful for controlled zero display when no revenue, not for display fallback for missing selected category.

DIVIDE handles zero and blank denominators safely. Its scope is safe undefined ratio behavior, not display fallback for missing selected category.

Blanket zero substitution can hide missing-source data quality issues. It would address preserve missingness semantics in KPI, not display fallback for missing selected category.

Question 360

A measure must activate an existing inactive date path rather than simulate it with arbitrary text comparisons. Which implementation best addresses this scenario?

Use a carefully scoped TREATAS virtual filter with matching key types.
Use TREATAS(VALUES(ProductSelection[ProductID]),Product[ProductID]) in CALCULATE.
Use a disconnected parameter table and read its selected value in a measure.
Use USERELATIONSHIP within CALCULATE for the validated inactive path.

Explanation

Correct Answer

USERELATIONSHIP leverages the existing relationship with known date keys, supporting efficient alternate physical relationship.

Incorrect Answers

Virtual relationships transfer intended filter values without changing the physical model. It would address calculation-specific disconnected mapping, not efficient alternate physical relationship.

TREATAS applies selected values as filters to a different model column. That targets disconnected slicer virtual relationship, not efficient alternate physical relationship.

Disconnected what-if tables provide parameters without physically filtering facts. It may suit user-controlled scalar threshold, not efficient alternate physical relationship.

Microsoft Power BI Data Analyst (PL-300) Practice Tests

Microsoft PL-300 Practice Test 34 - 10 Questions (Last Reviewed 11-Oct-2026)
Microsoft PL-300 Practice Test 35 - 10 Questions (Last Reviewed 10-Oct-2026)
Microsoft PL-300 Practice Test 36 - 10 Questions (Last Reviewed 09-Oct-2026)
Microsoft PL-300 Practice Test 37 - 10 Questions (Last Reviewed 08-Oct-2026)
Microsoft PL-300 Practice Test 38 - 10 Questions (Last Reviewed 07-Oct-2026)

Pass Your Microsoft PL-300 Exam Easy!

Question 350

Explanation

Correct Answer

Incorrect Answers

Question 351

Explanation

Correct Answer

Incorrect Answers

Question 352

Explanation

Correct Answer

Incorrect Answers

Question 353

Explanation

Correct Answer

Incorrect Answers

Question 354

Explanation

Correct Answer

Incorrect Answers

Question 355

Explanation

Correct Answer

Incorrect Answers

Question 356

Explanation

Correct Answer

Incorrect Answers

Question 357

Explanation

Correct Answer

Incorrect Answers

Question 358

Explanation

Correct Answer

Incorrect Answers

Question 359

Explanation

Correct Answer

Incorrect Answers

Question 360

Explanation

Correct Answer

Incorrect Answers

Microsoft Power BI Data Analyst (PL-300) Practice Tests