PL-300 exam tips: how to pass first time
The best PL-300 exam tip is to read the constraint before the options: almost every question hinges on one phrase such as only one active relationship, without giving workspace access, or must refresh daily. The exam tests whether you can pick the right Power BI feature for a stated requirement, so the options usually all sound plausible, and one word decides which is correct. These tips are about technique; the content is in the domain guides.
Before the exam
- Take the free official practice assessment to see the wording. It shows the style and difficulty of real questions.
- Use the exam sandbox once, so the interface and the question types are not new on the day.
- Re-read the current outline the evening before. Check Direct Lake, Copilot, visual calculations and DAX query view; the outline names them.
- Sleep and arrive early. For a proctored exam, the check-in takes time. See the exam day guide.
How to read a question
- Find the goal: what must the user be able to do or see?
- Find the constraint: least effort, no code, no extra licence, must refresh, must not see other regions.
- Find the object: is it a query, a relationship, a measure, a visual, a model, a workspace?
- Only then read the options and remove the ones that break the constraint.
The object matters because the same word means different things in different places. A filter in Power Query removes rows before load. A filter in DAX changes calculation context. A filter on a visual changes only that visual. A row-level security filter limits who sees which rows. Four layers, one word.
Power Query questions
- Merge is columns, append is rows. If the output needs more columns, it is merge; more rows, append.
- Order of steps matters. Fix values before changing the data type; filter early to reduce data.
- Reference follows the original, duplicate does not.
- Unpivot other columns survives new columns; unpivot selected columns does not.
- If a question says the change must happen at the source or must not change the query, think again about whether Power Query is the right tool.
Modelling and DAX questions
- Ask what the filter context is. For any measure, say what filters apply on the row of the visual, then what CALCULATE does to them.
- Measure versus column. Ratios, totals and anything that must respond to slicers is a measure. Anything needed on an axis, in a slicer or in a relationship is a column.
- One active relationship. A second one is inactive and activated by USERELATIONSHIP.
- Time intelligence needs a proper date table. If YTD or last year looks wrong, suspect the date table before the formula.
- Prefer a star schema. When an option flattens everything into one table, or relies on many-to-many or bi-directional filters, a simpler star answer is probably on offer.
Report design questions
- Choose the simplest visual. A line for trend, a bar for comparison, a card for one number.
- Match the feature to the interaction. Drillthrough goes to a detail page, a tooltip shows on hover, a bookmark saves a state, a sync slicer carries selections between pages.
- Accessibility is testable. Alt text, tab order, contrast and not relying on colour alone are all in scope.
- Paginated reports are for pixel-perfect, printable, multi-page output.
Service and security questions
- Role boundaries are the favourite. Know exactly where Viewer, Contributor, Member and Admin differ.
- App for consumers, workspace for builders.
- A gateway is for on-premises sources. A cloud source usually needs none.
- RLS has two halves: roles with DAX filters in Desktop, members in the service. Admin, Member and Contributor bypass it.
- Promote versus certify: anyone with write access can promote; only authorised reviewers can certify.
Case studies and time
Case studies share one long scenario across several questions. Skim the requirements first, then the data description, and return to the text only when a question needs a fact. Do not try to memorise the whole scenario. If a question has you stuck for more than a couple of minutes, mark it, move on and come back.
Yes/no series about one scenario usually cannot be revisited once you move on, so answer them carefully the first time.
Traps that cost marks
| Trap | Reality |
|---|---|
| Choosing the most powerful option | The question wants the least effort or least privilege |
| Merging when you need to append | Merge adds columns |
| Two active relationships | Only one is allowed |
| Defining RLS in Desktop and stopping | Members are added in the service |
| Adding managers as Contributors, expecting RLS to work | Contributors bypass RLS |
| Using a gateway for a cloud source | Not normally required |
| Summing a ratio column | Use a measure |
After you read this
Practise on realistic questions. Start with the five free sample questions, then take the 20-question practice test under time pressure. See study resources for the official material.