PL-300 study scenarios: three profiles
How you should study for PL-300 depends on which of its four domains your daily work already covers. Three of them (Prepare the data, Model the data, Visualize and analyze the data) are each worth 25–30%, and Manage and secure Power BI is worth 15–20%, so a background that is strong in one domain still leaves roughly two thirds of the exam to learn or verify. The 100-minute exam needs 700 out of 1000.
Example profiles, not real people. The profiles below are illustrative planning examples built from the official exam outline. They are not reviews or reports of anyone’s result.
The study plan assumes four weeks at 8 to 10 hours a week for someone who opens Power BI Desktop at work, and says to double that without any Power BI experience. The budgets below are planning assumptions derived from it and from the domain weights, not promises.
Profile one: the Excel power user who builds pivot tables all day
Starting point. Comfortable with tables, lookups and charts; has probably loaded a file into Power BI Desktop and dragged fields onto a canvas. Has not written DAX measures with CALCULATE or thought about relationships and filter direction.
Where the time goes. Model the data (25–30%) is the heart of it: a date table, cardinality, cross-filter direction and measures that behave under filter context. Prepare the data (25–30%) is close behind, because Power Query steps such as unpivot, merge versus append and reference versus duplicate queries are new ground. Visualize and analyze (25–30%) is mostly familiar.
The trap. Treating a measure like a cell formula. Excel habits produce calculated columns where a measure is needed, and flat tables where a star schema is expected.
Suggested order. Prepare the data, then Model the data (spend the longest here), then Manage and secure, then Visualize and analyze last as a lighter pass.
Time budget. A reasonable planning assumption is the doubled plan, 64 to 80 hours over eight weeks, with about half of it split between the first two domains.
Profile two: the report builder who consumes models someone else made
Starting point. Designs report pages every week on top of a shared semantic model. Knows bookmarks, drillthrough, themes and slicers well. Rarely touches the source queries or the relationships, and has never configured row-level security.
Where the time goes. The visual domain is already strong, so the budget moves to Prepare the data and Model the data, and to the workspace and security objectives in the smallest domain: the four workspace roles, apps and audiences, gateways, scheduled refresh, sensitivity labels and RLS. Those questions are predictable and often lost by people who have only ever been a Viewer or Contributor.
The trap. Assuming the exam is a report-design test. Skipping the data and model weeks because “the model already exists” gives away over half the paper.
Suggested order. Model the data, Prepare the data, Manage and secure, then a short review of the newer outline items in Visualize and analyze, such as visual calculations and the Copilot objectives.
Time budget. Following the study plan’s advice to compress the report-design week, a planning assumption is around 24 to 30 hours over three weeks, with most of the saved time spent on filter context, inactive relationships and workspace permissions.
Profile three: the SQL developer who has never designed a report
Starting point. Strong with joins, keys and fact and dimension thinking, so the data-shaping and star-schema ideas come quickly. Little experience of visual choice, storytelling, accessibility or the Power BI service.
Where the time goes. Visualize and analyze (25–30%) and Manage and secure (15–20%) carry the new learning: custom tooltips, sync slicers, mobile layout, paginated reports versus Power BI reports, then promotion and certification, subscriptions and alerts. Model the data still needs DAX, which behaves nothing like SQL aggregation.
The trap. Doing in DAX what would be a join or a group by in SQL, and writing measures that return the right number only at one level of detail.
Suggested order. Model the data first, to translate the SQL instincts into filter context; then Visualize and analyze; then Manage and secure; then a quick pass over Prepare the data.
Time budget. A planning assumption is the standard four weeks, 32 to 40 hours, with the second and third weeks of the study plan given the largest share.
The three profiles side by side
| Profile | Front-load | Main risk |
|---|---|---|
| Excel power user | Model the data, Prepare the data | Spreadsheet habits in DAX and in table design |
| Report builder on shared models | Prepare the data, Model the data, workspace security | Treating PL-300 as a report-design exam |
| SQL developer | Model the data, then Visualize and analyze | SQL-style thinking in measures; thin service knowledge |
How to check which PL-300 profile fits before booking
Take the free official practice assessment on Microsoft Learn cold and read the per-domain breakdown rather than the total. The domain you score lowest on is your profile’s front-loaded area, whatever your job title says. Then work through the five free sample questions and a timed practice test to see whether the weak area stays weak, and read the exam format page for the question types and the retake rules.
Once the model and DAX side feels solid, DP-600 is the usual engineering step beyond this exam, and the PL-300 vs DP-600 comparison explains where the two differ.