Reducing loaded data in Power Query with grouping and column removal
You have a Power BI semantic model that contains two queries. You discover that a report based on the model has performance issues. You plan to use Power Query to reduce the data loaded to the model. Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct answer is worth one point.
Community Votes
100% of anonymous learners picked answer AC. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Microsoft's data-reduction guidance names exactly these levers: remove unnecessary columns and rows before load, and group or summarize detail to the grain the report actually needs.
A report on a two-query semantic model underperforms, and Power Query must be used to cut the data volume loaded into the model, with two complementary actions to pick.
Treating query consolidation as data reduction — Append and Merge change how tables come together (and often grow row or column counts), while query groups are pure authoring hygiene with zero effect on model size.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Applying group by and summarize techniques (A) collapses detail rows to a higher grain before load, directly shrinking fact tables — the official data-reduction guidance for import models lists grouping and aggregating as a first-line technique. Removing unnecessary columns and rows (C) eliminates fields and records no visual consumes, which reduces both the dataset size and refresh load. Microsoft's import modeling guidance names column and row removal as the most effective data reduction step.Why the Other Options Are Wrong
Appending queries (B) stacks tables into more rows, growing rather than shrinking the model. Merging queries (D) adds lookup columns to a table, increasing column count unless other reductions follow — on its own it reduces nothing. Creating a new query group (E) merely organizes queries in the editor's folder tree; the data loaded is byte-identical.Community Comment Notes
Several commenters anchor A and C to the official import-modeling-data-reduction guidance page. One adds the useful observation that Append can actually increase dataset size, and that a query group only affects Power Query editor organization.Official Reference
Related Analysis
Practice All PL-300 Questions
Access 116 questions with complete answers and detailed explanations.
View Full PL-300 Practice Test →