Examworthyexamworthy.comMicrosoft Power BI Data Analyst (PL-300) cheat sheet
Microsoft
Free to share. Examworthy is not affiliated with or endorsed by Microsoft; PL-300 and related marks belong to their respective owners.
At a glance
Format: Multiple choice and multiple response, at a Pearson VUE testing center or online proctored
Domain weight map
Heaviest first - spend your time hereHow this exam thinks
PL-300 is the full analyst workflow tested on documented specifics: prepare in Power Query, model with a star schema and DAX, visualise for the audience, and deploy with refresh and row-level security, and the right answer is almost always the one exact behaviour Microsoft's docs describe.
Spot the trap
Tempting wrong answers, and why they failTempting but wrong
A direct many-to-many relationship with single cross-filter direction is Microsoft's recommended way to relate two dimensions like Salesperson and Region.
Why it fails
Direct many-to-many is supported, but the guidance recommends a bridging (factless fact) table when relating two dimensions because it preserves clearer filter propagation and is documented as the best practice.
Model the Data
Tempting but wrong
Power Query Online and Power Query for Desktop have completely separate, mismatched user experiences for shaping data.
Why it fails
Wrong. Although two Power Query experiences exist (Online and Desktop), both provide almost the same ribbon-driven shaping experience in every scenario. They differ only in a few features, such as fuzzy grouping and the Percentile and Count distinct values aggregations being Online-only.
Prepare the Data
Tempting but wrong
A stacked column chart with unit price as the legend is a good way to reveal correlation between unit price and units sold across many SKUs.
Why it fails
Stacked columns compare category totals, not the intersection of two numerical measures across hundreds of points. To reveal correlation and clusters between unit price and units sold, use a scatter chart that plots each SKU at the intersection of the two values.
Visualize and Analyze the Data
Tempting but wrong
A workspace Contributor can publish a brand-new app from the workspace for the first time.
Why it fails
Publishing the first version of an app is a Yes only for Admin and Member roles. Contributors can update an existing app when a workspace Admin explicitly delegates update rights, but they cannot create or publish an app for the first time. Member is the least-privileged role that can publish.
Deploy and Maintain Assets
Tempting but wrong
To relate Salesperson and Region in a many-to-many association, you can just denormalise Region attributes into the Salesperson table so the model needs only one dimension.
Why it fails
Denormalising the region attributes collapses the relationship and breaks the ability to filter independently by region, so it never represents the many-to-many association. The recommended pattern is a bridging (factless fact) table that holds salesperson and region keys, with each dimension joined to the bridge.
Model the Data
Tempting but wrong
Automatic Page Refresh in Power BI works on pages backed by an Import semantic model.
Why it fails
Wrong. Automatic Page Refresh is only available for DirectQuery data sources, not Import. The minimum refresh interval depends on workspace type and capacity admin settings.
Prepare the Data
Tempting but wrong
A donut chart can surface the correlation between unit price and units sold across hundreds of SKUs.
Why it fails
Donut charts show part-to-whole composition for a small number of categories, not correlation. Use a scatter chart, which plots data points at the intersection of two numerical values and reveals correlations and clusters.
Visualize and Analyze the Data
Tempting but wrong
You should grant a tenant-level Power BI admin role just to let someone publish an app from a single workspace.
Why it fails
Tenant admin roles oversee policy and are far more than is needed to publish one app. The least-privilege role that can publish a new app from a workspace is Member, which holds app publish, unpublish, and permission rights alongside Admin.
Deploy and Maintain Assets
Key terms
Exam-day rules
- Read the scenario for what the analyst needs first, then match it to the exact documented behaviour. Distractors are written to sound reasonable; the right answer is the precise rule Microsoft's docs state, not the one that feels intuitive.
- When a question says best practice or recommended, reach for the canonical pattern: a star schema over a flat table, a measure over a calculated column, a bridging table for many-to-many, and pre-summarising during ETL for the biggest model-size cut.
- On any role or licence question, pick the least-privileged role and the minimum licence that still does the job. Member, not Admin, publishes a new app; Pro or PPU, not free, creates a workspace.
- For DAX, decide measure versus calculated column by where it runs: query-time aggregation that responds to filters is a measure; a per-row value stored at refresh is a calculated column, and it widens the model.
- Watch the documented edge cases the exam loves: data alerts only on gauges, KPIs, and cards pinned from report visuals; sensitivity labels cover subscription attachments but not the email body or preview image.
Revision schedule
- Day 1Map the blueprint and book a date
- Week 1Drill Power Query hands-on
- Weeks 2 to 3Go deep on modelling and DAX
- Week 4Build visualisation and Copilot fluency
- Week 5Master deploy, security, and the role matrix