Microsoft Power BI Data Analyst PL-300 Practice Test 12
Question 110
A sales table must enrich each invoice with a customer segment from a Customer lookup using CustomerID. After the correct solution is implemented, which result provides the MOST DIRECT evidence that the requirement actually works?
- A single example row looks plausible, but unmatched keys and duplicate matches were not examined
- The transformed table displays expected column headings, but the underlying row grain has not been checked
- The query finishes refresh without errors, but resulting totals and keys have not been reconciled
- Each invoice has its matching segment and unmatched invoices are visible for data-quality handling
Explanation
Correct Answer
D:Each invoice has its matching segment and unmatched invoices are visible for data-quality handling This exercises the requested business outcome and the necessary positive or negative boundary.
Incorrect Answers
A:One positive example can conceal lost or multiplied rows elsewhere in the reshaped data.
B:Correct headers alone do not demonstrate correct append, merge, pivot or group-by cardinality.
C:A successful refresh can still yield the wrong business grain or aggregate values.
Question 111
An activity log has rows with Status values Open and Closed and a Count field, and a summary table needs a separate column for each Status value. A pilot instead implemented the following proposed change: Unpivot the existing Status column. The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- Transposition does not yield the requested entity-by-status aggregation
- Appending doubles observations without creating status columns
- Pivot turns distinct status values into columns and aggregates values when needed
- Unpivot expands columns into rows rather than yielding Open and Closed count columns
Explanation
Correct Answer
D:Unpivot expands columns into rows rather than yielding Open and Closed count columns This specifically addresses the deployed or proposed alternative: Unpivot the existing Status column.
Incorrect Answers
A:Transposition does not yield the requested entity-by-status aggregation That limitation describes Transpose the log without first choosing keys, not the specified approach.
B:Appending doubles observations without creating status columns That limitation applies to a different alternative (Append another copy of the activity log), not the one here.
C:Pivot turns distinct status values into columns and aggregates values when needed This supports the recommended design but does not diagnose why the specified alternative fails.
Question 112
Monthly sales files have the same columns and must be stacked into one table without joining on a key. A pilot instead implemented the following proposed change: Merge the queries on the invoice identifier. The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- Merge joins columns from matching rows and can duplicate data instead of stacking months
- Relationships do not produce the requested single stacked transaction table
- Pivot changes the table shape and does not simply concatenate monthly records
- Append combines rows from aligned tables into a longer table
Explanation
Correct Answer
A:Merge joins columns from matching rows and can duplicate data instead of stacking months This specifically addresses the deployed or proposed alternative: Merge the queries on the invoice identifier.
Incorrect Answers
B:Relationships do not produce the requested single stacked transaction table That limitation describes Create a many-to-many model relationship between each monthly table, not the specified approach.
C:Pivot changes the table shape and does not simply concatenate monthly records That limitation applies to a different alternative (Pivot the Month column into many new columns), not the one here.
D:Append combines rows from aligned tables into a longer table This supports the recommended design but does not diagnose why the specified alternative fails.
Question 113
A semantic model contains unique product rows and repeated sales lines by ProductKey, and product slicers must filter Sales without filtering other product attributes backward. After the correct solution is implemented, which result provides the MOST DIRECT evidence that the requirement actually works?
- One aggregate value is nonblank, but filtering has not been tested from each intended dimension
- The model saves successfully, but source keys and report totals have not been reconciled
- Slicing Product Category filters matching sales rows and does not unexpectedly filter unrelated dimensions
- The relationship diagram displays a line between tables, but no matching-key uniqueness test has run
Explanation
Correct Answer
C:Slicing Product Category filters matching sales rows and does not unexpectedly filter unrelated dimensions This exercises the requested business outcome and the necessary positive or negative boundary.
Incorrect Answers
A:An unfiltered total cannot establish that the model's date roles and cross-filter paths behave as specified.
B:Saving a model does not rule out duplicate dimension rows, ambiguous paths or fact multiplication.
D:A visible relationship is not proof that the dimension key and relationship cardinality are valid.
Question 114
A semantic model imported many unused high-cardinality transaction text columns and file size is excessive. A pilot instead implemented the following proposed change: Set every text column to Don't summarize. The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- A theme cannot reduce the semantic model's stored data volume
- Summarization settings do not remove cached high-cardinality data
- Additional calculated columns increase rather than reduce model memory
- Fewer unnecessary distinct strings reduce storage and encoding overhead in Import models
Explanation
Correct Answer
B:Summarization settings do not remove cached high-cardinality data This specifically addresses the deployed or proposed alternative: Set every text column to Don't summarize.
Incorrect Answers
A: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:Additional calculated columns increase rather than reduce model memory That limitation applies to a different alternative (Add another calculated copy of the unused columns), 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 115
A legacy model contains Sales related bidirectionally to both Geography and Customer, plus another path between Geography and Customer, producing ambiguous filter results. Which Power BI or Power Query action BEST meets the stated requirement?
- Keep deliberate single-direction dimension-to-fact paths and remove unnecessary bidirectional relationships
- Create multiple active alternate paths between the same tables
- Turn every relationship inactive
- Set every relationship to Both because more propagation always helps
Explanation
Correct Answer
A:A clean star filter flow reduces ambiguous propagation paths and makes slicer behavior predictable This addresses the specific requirement: a legacy model contains Sales related bidirectionally to both Geography and Customer, plus another path between Geography and Customer, producing ambiguous filter results.
Incorrect Answers
B:Competing active paths do not automatically resolve ambiguity or produce intended results This alternative therefore fails an explicit scenario constraint.
C:Inactive paths break normal dimension filters rather than resolving the model design This alternative therefore fails an explicit scenario constraint.
D:Additional both-direction paths can increase ambiguity and affect performance This alternative therefore fails an explicit scenario constraint.
Question 116
A report already filters a set of allowed product colors and the new measure must further require Red without reintroducing Red if it was previously excluded. Which Power BI or Power Query action BEST meets the stated requirement?
- Use REMOVEFILTERS(Product[Color])
- Use a normal replacement CALCULATE color filter without KEEPFILTERS
- Use KEEPFILTERS inside CALCULATE for the Red color constraint
- Change only the report title to indicate Red
Explanation
Correct Answer
C:KEEPFILTERS intersects the new filter with existing Color selections instead of overwriting them This addresses the specific requirement: a report already filters a set of allowed product colors and the new measure must further require Red without reintroducing Red if it was previously excluded.
Incorrect Answers
A:Removing Color filters erases the original user restriction entirely This alternative therefore fails an explicit scenario constraint.
B:A normal filter on the same column may replace the existing color selection This alternative therefore fails an explicit scenario constraint.
D:A title does not affect DAX filter intersection semantics This alternative therefore fails an explicit scenario constraint.
Question 117
A monthly table displays a numerical total but the analyst wants a simple percentage-of-grand-total measure without manually building complex DAX. A pilot instead implemented the following proposed change: Use Sort Descending on the visual. The business requirement was not met. Which technical limitation MOST DIRECTLY explains the result?
- Sorting does not calculate percentage of any grand total
- Quick measures generate DAX for common calculations that can then be reviewed and modified
- Percent formatting alone does not divide each value by the overall total
- A fixed calculated label does not respond to report filters
Explanation
Correct Answer
A:Sorting does not calculate percentage of any grand total This specifically addresses the deployed or proposed alternative: Use Sort Descending on the visual.
Incorrect Answers
B:Quick measures generate DAX for common calculations that can then be reviewed and modified This supports the recommended design but does not diagnose why the specified alternative fails.
C:Percent formatting alone does not divide each value by the overall total That limitation applies to a different alternative (Apply Percentage number formatting to the existing total amount), not the one here.
D:A fixed calculated label does not respond to report filters That limitation describes Use a calculated table containing a fixed percent label, not the specified approach.
Question 118
Finance needs Gross Margin Percent and some filtered regions have zero revenue, so division errors must be handled intentionally. Which Power BI or Power Query action BEST meets the stated requirement?
- Use the raw slash operator with no zero-denominator policy
- Replace missing revenue with a fixed 1 in the source
- Use SUM([Gross Margin]) divided by row count
- Use DIVIDE([Gross Margin], [Revenue], BLANK()) for the ratio
Explanation
Correct Answer
D:DIVIDE safely handles a zero denominator and can return a deliberate alternate result This addresses the specific requirement: finance needs Gross Margin Percent and some filtered regions have zero revenue, so division errors must be handled intentionally.
Incorrect Answers
A:Unprotected division can produce undesirable special results in zero-revenue contexts This alternative therefore fails an explicit scenario constraint.
B:Inventing revenue changes the underlying financial data to mask a calculation edge case This alternative therefore fails an explicit scenario constraint.
C:An already evaluated measure is not a column to sum and row count is the wrong denominator This alternative therefore fails an explicit scenario constraint.
Question 119
A large DirectQuery Sales source repeatedly computes the same weekly totals and reports need low-latency common aggregates. Which Power BI or Power Query action BEST meets the stated requirement?
- Use the detailed transaction table for every summary without aggregates
- Create a high-cardinality calculated column per query request
- Consider a supported aggregation table that answers common group-by requests
- Disable all date filters to improve query speed
Explanation
Correct Answer
C:Aggregations can serve repeated summary queries without scanning the detailed source for every visual This addresses the specific requirement: a large DirectQuery Sales source repeatedly computes the same weekly totals and reports need low-latency common aggregates.
Incorrect Answers
A:Repeated detail scans can exceed latency requirements This alternative therefore fails an explicit scenario constraint.
B:Extra detailed calculations do not substitute for reusable summary storage This alternative therefore fails an explicit scenario constraint.
D:Removing necessary filters changes the business result instead of optimizing its execution This alternative therefore fails an explicit scenario constraint.
Question 120
A report stores one row per sales line but the analyst created a related Customer table with three rows per CustomerID; totals increase unexpectedly. After the correct solution is implemented, which result provides the MOST DIRECT evidence that the requirement actually works?
- One aggregate value is nonblank, but filtering has not been tested from each intended dimension
- 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
- Sales totals reconcile and Customer has one row per CustomerID at the declared grain
Explanation
Correct Answer
D:Sales totals reconcile and Customer has one row per CustomerID at the declared grain This exercises the requested business outcome and the necessary positive or negative boundary.
Incorrect Answers
A:An unfiltered total cannot establish that the model's date roles and cross-filter paths behave as specified.
B:Saving a model does not rule out duplicate dimension rows, ambiguous paths or fact multiplication.
C:A visible relationship is not proof that the dimension key and relationship cardinality are valid.