100% Latest & Updated Microsoft PL-300 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 170
An enterprise semantic model must report order-line revenue by product, region and date without repeating descriptions on every transaction. The selected approach is: Create a star schema with fact and dimension tables. Which implementation step puts it into practice?
- Apply currency or percentage format to the correct model measure.
- Configure relationship filter direction to follow the star schema.
- Keep sales line events in a fact table and join dimensions through keys.
- Document a unique row key and use grain-consistent measures.
Explanation
Correct Answer
C:The fact grain and dimension identities should support one-to-many filter relationships.
Incorrect Answers
A:Formatting should not alter the measure's numeric data type. It does not implement the needed solution: create a star schema with fact and dimension tables.
B:An unnecessary bidirectional filter can create ambiguous paths. It does not implement the needed solution: create a star schema with fact and dimension tables.
D:Measures such as order count may require DISTINCTCOUNT of an order identifier. It does not implement the needed solution: create a star schema with fact and dimension tables.
Question 171
A retail sales model has transaction amounts and descriptive product/customer attributes in separate sources. The chosen solution is: Create a star schema with fact and dimension tables. Which verification best demonstrates that it meets the requirement?
- Change slicers and verify ranks recalculate among the intended stores.
- Compare seasonal periods across two years with known values.
- Measure model size and refresh duration after pruning.
- Verify revenue totals match source transactions under dimension filters.
Explanation
Correct Answer
D:Changing product or date slicers should restrict the correct sales rows.
Incorrect Answers
A:Rank 1 should match the highest measure within scope. That check does not verify the result required here: verify revenue totals match source transactions under dimension filters.
B:Matching months should align correctly across years. That check does not verify the result required here: verify revenue totals match source transactions under dimension filters.
C:Smaller data should not change required report values. That check does not verify the result required here: verify revenue totals match source transactions under dimension filters.
Question 172
A retail sales model has transaction amounts and descriptive product/customer attributes in separate sources. A specific ongoing problem has appeared: Duplicated dimension keys could multiply transactions in queries. Which safeguard most directly addresses it?
- Document measure filter replacement versus intersection behavior.
- Validate dimension-side key uniqueness and relationship cardinality.
- Test folding after substantive query edits.
- Maintain a continuous marked date table and calendar assumptions.
Explanation
Correct Answer
B:Duplicate lookup keys undermine expected one-to-many semantics.
Incorrect Answers
A:Choice of filter semantics affects user trust; duplicate lookup keys undermine expected one-to-many semantics.
C:The physical execution plan can change with transformations; duplicate lookup keys undermine expected one-to-many semantics.
D:Time intelligence needs reliable date semantics. Duplicate lookup keys undermine expected one-to-many semantics.
Question 173
An order dataset has multiple lines per invoice while management needs both line-level and order-level metrics. Which Power BI approach most directly satisfies this requirement?
- Define fact-table grain before building measures and relationships.
- Activate an alternate relationship inside a specific DAX measure.
- Set measure format strings rather than converting numerical values to text.
- Use a calculated column when a stored row attribute is needed.
Explanation
Correct Answer
A:Knowing whether one row means a line, package, or order prevents incorrect aggregation.
Incorrect Answers
B:USERELATIONSHIP can select an inactive relationship within a CALCULATE expression; knowing whether one row means a line, package, or order prevents incorrect aggregation.
C:A formatted numeric measure remains usable in sorting and arithmetic. Knowing whether one row means a line, package, or order prevents incorrect aggregation.
D:Calculated columns materialize per-row results in the model, unlike measures evaluated on demand; knowing whether one row means a line, package, or order prevents incorrect aggregation.
Question 174
A shipping fact table has one row per package, but the business asks for shipment-level totals. The selected approach is: Define fact-table grain before building measures and relationships. Which implementation step puts it into practice?
- Keep sales line events in a fact table and join dimensions through keys.
- Set ProductKey as the one-side key and validate cardinality.
- Document a unique row key and use grain-consistent measures.
- Use a surrogate version key or apply an explicit current-record rule.
Explanation
Correct Answer
C:Measures such as order count may require DISTINCTCOUNT of an order identifier.
Incorrect Answers
A:The fact grain and dimension identities should support one-to-many filter relationships. It does not implement the needed solution: define fact-table grain before building measures and relationships.
B:The dimension side must have unique nonblank keys under the model design. It does not implement the needed solution: define fact-table grain before building measures and relationships.
D:Relationships must not use nonunique versioned IDs as the one-side key. It does not implement the needed solution: define fact-table grain before building measures and relationships.
Question 175
An order dataset has multiple lines per invoice while management needs both line-level and order-level metrics. The chosen solution is: Define fact-table grain before building measures and relationships. Which verification best demonstrates that it meets the requirement?
- Test zero-revenue and normal-revenue filters.
- Compare seasonal periods across two years with known values.
- Compare line counts, distinct orders and totals with audited source facts.
- Change slicers and verify ranks recalculate among the intended stores.
Explanation
Correct Answer
C:Validation should not equate line rows with unique orders.
Incorrect Answers
A:A robust ratio should not emit misleading divide-by-zero errors. That check does not verify the result required here: compare line counts, distinct orders and totals with audited source facts.
B:Matching months should align correctly across years. That check does not verify the result required here: compare line counts, distinct orders and totals with audited source facts.
D:Rank 1 should match the highest measure within scope. That check does not verify the result required here: compare line counts, distinct orders and totals with audited source facts.
Question 176
An order dataset has multiple lines per invoice while management needs both line-level and order-level metrics. A specific ongoing problem has appeared: Stakeholders may assume every row represents one order. Which safeguard most directly addresses it?
- Scope filter-removal expressions to the intended dimension.
- Record grain and use explicit distinct-order measures.
- Document how unavailable ratios are displayed.
- Define a clear fallback for ambiguous selections.
Explanation
Correct Answer
B:Clear semantics prevent double-counting higher-level entities.
Incorrect Answers
A:Broad ALL-table removal can change more context than required; clear semantics prevent double-counting higher-level entities.
C:Blank and zero carry different business meanings; clear semantics prevent double-counting higher-level entities.
D:An explicit alternate prevents blank or confusing labels. Clear semantics prevent double-counting higher-level entities.
Question 177
A Sales fact table contains many transactions for each Product key, while Products has one row per product. Which Power BI approach most directly satisfies this requirement?
- Use a many-to-one relationship from fact to unique dimension.
- Use a calculated table when a materialized model table is justified.
- Hide technical columns and provide clear measure/field properties.
- Use a calculated column when a stored row attribute is needed.
Explanation
Correct Answer
A:Many fact records typically match one unique dimension record.
Incorrect Answers
B:Calculated tables are computed during processing and then stored; many fact records typically match one unique dimension record.
C:Metadata design helps authors use intended business fields. Many fact records typically match one unique dimension record.
D:Calculated columns materialize per-row results in the model, unlike measures evaluated on demand; many fact records typically match one unique dimension record.
Question 178
A financial model has many invoice lines pointing to one customer dimension record. The selected approach is: Use a many-to-one relationship from fact to unique dimension. Which implementation step puts it into practice?
- Disable or refactor conflicting paths and use explicit measure context where needed.
- Document a unique row key and use grain-consistent measures.
- Hide surrogate keys and set appropriate categories, names and formatting.
- Set ProductKey as the one-side key and validate cardinality.
Explanation
Correct Answer
D:The dimension side must have unique nonblank keys under the model design.
Incorrect Answers
A:Each measure should have an intended unambiguous filter route. It does not implement the needed solution: use a many-to-one relationship from fact to unique dimension.
B:Measures such as order count may require DISTINCTCOUNT of an order identifier. It does not implement the needed solution: use a many-to-one relationship from fact to unique dimension.
C:The fields pane should emphasize business-friendly measures. It does not implement the needed solution: use a many-to-one relationship from fact to unique dimension.
Question 179
A Sales fact table contains many transactions for each Product key, while Products has one row per product. The chosen solution is: Use a many-to-one relationship from fact to unique dimension. Which TWO actions together implement this approach and provide evidence that it works? Choose TWO.
- Compare the measure with a filtered source total.
- Filter one product and reconcile fact rows and sums.
- Hide surrogate keys and set appropriate categories, names and formatting.
- Set ProductKey as the one-side key and validate cardinality.
- Test zero-revenue and normal-revenue filters.
Explanation
Correct Answers
B:The relationship should propagate the intended product filter to sales.
D:The dimension side must have unique nonblank keys under the model design.
Incorrect Answers
A:Totals should reconcile to the currently selected population. That check does not verify the result required here: filter one product and reconcile fact rows and sums.
C:The fields pane should emphasize business-friendly measures. It does not implement the needed solution: use a many-to-one relationship from fact to unique dimension.
E:A robust ratio should not emit misleading divide-by-zero errors. That check does not verify the result required here: filter one product and reconcile fact rows and sums.
Question 180
A Sales fact table contains many transactions for each Product key, while Products has one row per product. A specific ongoing problem has appeared: An unexpected many-to-many relation may yield ambiguous totals. Which safeguard most directly addresses it?
- Check unique dimension keys before enabling the relationship.
- Use last available snapshot rather than assuming every month end has a row.
- Maintain a continuous marked date table and calendar assumptions.
- Keep aggregations as measures for filter-sensitive results.
Explanation
Correct Answer
A:Accidental many-to-many modeling often signals a data quality or grain error.
Incorrect Answers
B:Semi-additive measures must handle missing snapshot days. Accidental many-to-many modeling often signals a data quality or grain error.
C:Time intelligence needs reliable date semantics; accidental many-to-many modeling often signals a data quality or grain error.
D:Calculated columns materialize row values and do not replace dynamic report totals. Accidental many-to-many modeling often signals a data quality or grain error.
Microsoft Power BI Data Analyst (PL-300) Practice Tests