PL-300 Prepare the data Practice Question
You have a Power BI report that uses a dataset with many columns. You want to reduce the dataset size by removing columns that are not used in any report visual. What is the best practice?
⚠ Common exam trap
Test-takers frequently confuse hiding columns (which only affects the user interface) with physically removing them, leading them to choose option D, but only removal before loading reduces dataset size.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Remove the columns in Power Query Editor before loading
Removing columns in Power Query Editor before they are loaded into the data model physically excludes them from the dataset, reducing its size and improving performance. This is the only method that prevents unused columns from consuming memory and storage in the in-memory VertiPaq engine.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Remove the columns in Power Query Editor before loading
Why this is correct
Removing columns in Power Query Editor before loading is the only true data-reduction method among the options. This action prevents the column's data from ever being imported into the model, reducing the .pbix file size, memory footprint, and refresh time. It also improves report performance because fewer columns are processed during queries. This is the recommended approach when a column is not needed for any analysis.
- ✗
Use the Q&A feature to exclude columns
Why it's wrong here
Q&A is a natural-language query feature that lets users type questions and get answers as visuals. It cannot modify the data model physically or logically; it only queries the existing tables, columns, and measures. There is no 'exclude column' command in Q&A—it is purely a query interface, not a data transformation tool. Using Q&A to try to exclude columns would have no effect on the dataset structure.
- ✗
Apply report-level filters to exclude the columns
Why it's wrong here
Report-level filters in Power BI restrict which rows appear in visuals and pages based on column values, such as filtering to a specific year or region. They do not remove columns from the dataset; the columns remain fully available in the model and are still stored, compressed, and queried. Filters only affect the result sets returned to the report, not the schema or size of the underlying data model. Therefore, applying report-level filters cannot reduce dataset size.
- ✗
Hide the columns in the model view
Why it's wrong here
Hiding columns in the model view simply removes the column from the field list shown in report views, making it less accessible to report authors. The column data is still physically stored in the model, occupies memory, and contributes to the dataset size, and it can still be used in DAX calculations via explicit references. Hiding is a design-time feature for simplifying navigation or enforcing row-level security, but it does not reduce storage or improve refresh performance.
Go deeper
Related to this question
About these practice questions
One of 524 original PL-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-300 exam.