Microsoft · PL-300

PL-300 Exam: Complete Microsoft Power BI Data Analyst Guide

Current PL-300 exam guide covering the $165 USD price, 100-minute limit, Power Query, DAX, Power BI domains, renewal, and preparation priorities.

Last verified September 6, 2026

PL-300 exam at a glance

Facts last verified September 6, 2026

Domain breakdown

Who should take the PL-300 exam?

PL-300 is designed for data analysts who turn business questions into understandable, actionable Power BI reports. The role sits between business stakeholders, who define the decision to support, and data or analytics engineers, who make reliable data available. The analyst is responsible for shaping that data into a useful model and delivering a report that people can interpret, trust, and use.

The exam is a good fit for business intelligence analysts, reporting analysts, Power BI developers, and Excel users moving into governed self-service analytics. It also suits consultants and subject-matter experts who already build Power BI solutions and want a recognized Microsoft credential. PL-300 is classified as intermediate: it is accessible, but it is not merely an introduction to dashboards.

There are no formal prerequisites. You can schedule PL-300 without another certification, a degree, or a required course. In practice, you should be able to import and transform messy data, design a star schema, write DAX measures, build an accessible report, publish it to the Power BI service, configure refresh, and restrict access appropriately.

Microsoft specifically expects proficiency with Power Query and Data Analysis Expressions (DAX). If you have only consumed reports or created visuals from a perfectly prepared spreadsheet, build several end-to-end solutions before attempting the exam.

Skills measured on PL-300

Microsoft's official PL-300 study guide lists four domains as of April 20, 2026. The first three each represent 25–30% of the exam, so preparation must stay balanced across data preparation, modeling, and reporting. The blueprint changes as Power BI evolves; check its change log when you start studying and again before you book.

Prepare the data (25–30%)

This domain begins before a visual exists. You must identify and connect to an appropriate source or shared semantic model, configure source credentials and privacy levels, and choose a storage mode. Understand how Import, DirectQuery, and DirectLake differ in data freshness, performance, source load, modeling flexibility, and operational needs. The right choice follows the scenario rather than a universal preference.

Data profiling and cleaning require more than removing blank rows. Use column quality, distribution, profile statistics, and data types to find unexpected values, nulls, duplicates, and import errors. Know how a transformation can silently change granularity or discard valid records, and verify the result instead of assuming a refresh means the data is correct.

Power Query is central to this section. Practice creating and transforming columns; grouping and aggregating rows; pivoting, unpivoting, and transposing; converting semi-structured data into tables; and merging or appending queries. Understand the difference between referencing and duplicating a query, and configure which queries load to the model.

Finally, shape source data into fact and dimension tables and create stable relationship keys. A strong candidate can explain where a transformation belongs, preserve the required grain, and produce a repeatable refresh rather than a one-off cleanup.

Model the data (25–30%)

Modeling tests whether your report rests on a reliable analytical structure. Be able to configure table and column properties, choose relationship cardinality and cross-filter direction, implement role-playing dimensions, and build a common date table. Favor a clear star schema; unnecessary bidirectional relationships and many-to-many designs often create ambiguity and make measures harder to reason about.

DAX is the other major component. The current objectives include aggregation measures, CALCULATE, time intelligence, basic statistical functions, semi-additive measures, quick measures, calculated columns and tables, and calculation groups. Do not study these as a formula list. Learn how filter context moves through relationships, how CALCULATE changes that context, and why the same expression can return different values at different levels of a visual.

Know when to use a measure instead of a calculated column. Measures calculate at query time and respond to filter context; calculated columns are stored in the model and evaluated during refresh. Practice common business patterns such as year-to-date results, prior-period comparison, percent of total, distinct counts, and closing balances.

Optimization completes the domain. Remove unused rows and columns, reduce excessive granularity, and use Performance Analyzer and DAX query view to locate slow visuals, measures, or relationships. The goal is not micro-optimization—it is recognizing model choices that increase size, create ambiguity, or force expensive calculations.

Visualize and analyze the data (25–30%)

This domain evaluates whether the report communicates a decision, not whether it contains many charts. Select visuals that match the comparison, trend, composition, distribution, or detail users need. Configure formatting, filters, slicers, themes, conditional formatting, and page properties without allowing decoration to obscure meaning.

Current objectives also include Copilot-assisted report creation and narrative visuals, paginated-report use cases, and visual calculations written with DAX. Know what these tools are appropriate for and validate generated output against the model and business question. Copilot can accelerate a draft, but it does not replace sound data modeling or review.

Usability covers bookmarks, tooltips, visual interactions, sorting, synchronized slicers, the Selection pane, buttons, drillthrough, navigation, export settings, automatic page refresh, and personalized visuals. Build both desktop and mobile layouts. Accessibility is explicitly measured, so practice logical tab order, useful alternative text, adequate contrast, clear labels, and designs that do not depend on color alone.

Analysis features include grouping, binning, clustering, AI visuals, reference lines, error bars, forecasting, and anomaly detection. You should know what each reveals and when its output could mislead. The exam favors choosing a feature that answers the stated analytical need over adding complexity to a report.

Manage and secure Power BI (15–20%)

The smallest domain is still essential because a useful report must operate safely after publication. Know how to create and configure workspaces, publish or update content, package reports into apps, create dashboards, and choose a distribution method. Distinguish workspace collaboration from broad report consumption instead of adding every viewer as a workspace member.

Operational topics include subscriptions, data alerts, content promotion and certification, gateways, and scheduled semantic-model refresh. Be able to determine when an on-premises data gateway is required, which credentials are used, and where to investigate a failed refresh. Publishing a report is only the start of its service lifecycle.

Security objectives span workspace roles, item-level access, semantic-model permissions, row-level security, security-group membership, and sensitivity labels. These controls solve different problems. Practice mapping requirements such as “manage the workspace,” “build a new report from this model,” “view only the western region,” and “mark exported data as confidential” to the narrowest appropriate control.

How to prepare for PL-300

Start with the blueprint and create one practical task for every objective group. A useful portfolio project begins with imperfect data from at least two sources, cleans it in Power Query, loads a star schema, adds tested DAX measures, and delivers desktop and mobile reports. Publish it to a workspace, configure refresh, add row-level security, and have another account test the final experience.

A six-week sequence works well for candidates with basic Power BI exposure: data connection and Power Query; dimensional modeling; DAX and filter context; reporting and accessibility; Power BI service administration and security; then timed review. Spend more time on the weakest domain, but do not skip governance because its percentage is smaller.

Use Microsoft's free learning paths and the instructor-led PL-300T00 course as the official sequence. Keep a short “use when / avoid when” notebook for commonly confused choices such as Import versus DirectQuery versus DirectLake, merge versus append, measure versus calculated column, workspace role versus sharing, and RLS versus object permissions.

PL-300 practice questions

Microsoft provides a free Practice Assessment from the PL-300 certification page. Use it after completing at least one full project, then map every missed question back to a blueprint objective. A good review explains why the correct option satisfies the scenario and why the alternatives do not.

Use only objective-aligned practice material. Avoid exam dumps or any source claiming to reproduce live questions; those materials can violate Microsoft's candidate agreement and do not develop the judgment needed to build production Power BI solutions.

PL-300 vs. DP-600

PL-300 focuses on the Power BI data analyst workflow: preparing data, building semantic models, writing DAX, designing reports, and managing Power BI content. DP-600 targets a broader Fabric analytics engineer role and expects work across enterprise-scale semantic models, lakehouses, warehouses, deployment, governance, and other Microsoft Fabric capabilities.

Choose PL-300 if your immediate goal is report development and self-service analytics in Power BI. Choose DP-600 if you already work across Fabric and own more of the analytical platform. The exams can complement each other, but PL-300 is not a formal prerequisite. See the full DP-600 exam guide for its current scope.

Is the PL-300 certification worth it?

PL-300 is valuable when Power BI appears in your current responsibilities or target job descriptions. It gives employers a recognizable signal across the complete report lifecycle, including areas that portfolios sometimes omit: data quality, model design, performance, refresh, governance, and security. It does not replace business-domain knowledge or a body of real reports that you can explain.

The credential aligns most directly with Power BI data analyst, business intelligence analyst, reporting analyst, and junior Power BI developer roles. It can also support consultants and business analysts who build governed analytics for their teams. Its value is strongest when paired with examples showing how your analysis changed a decision or process, not simply screenshots of dashboards.

The certification is valid for one year. Renewal is free through an online, unproctored assessment during the six months before expiration, so maintenance requires current Power BI knowledge rather than another paid proctored exam.

PL-300 exam-day notes

• Microsoft gives you 100 minutes for the assessment. The total appointment is longer to include check-in, instructions, the candidate agreement, and optional feedback.
• Microsoft does not publish a fixed question count. Most Microsoft certification exams typically contain 40–60 questions, but the actual number can vary.
• PL-300 is proctored and may contain interactive components. Use Microsoft's exam sandbox to learn the interface before test day.
• As an associate exam, PL-300 permits restricted access to Microsoft Learn during the assessment. The timer continues, so use Learn only for targeted lookups.
• A passing result is a scaled score of 700 or higher; 700 does not necessarily mean 70% correct.
• Register with a personal Microsoft account. Microsoft warns that exam records tied to a work or school account can become unrecoverable when you leave that organization.

Prep resources

← More Microsoft exams