Overview
Visualize and analyze the data is 25–30% of the PL-300 exam and is where the model becomes insight for users. It has three objective groups. Creating reports covers selecting and formatting appropriate visuals, creating a narrative visual and report pages with Copilot, applying themes and conditional formatting, slicing and filtering, paginated reports, and visual calculations with DAX. Enhancing reports covers bookmarks, custom tooltips, interactions between visuals, navigation, sorting, sync slicers, grouping and layering with the Selection pane, drillthrough, export settings, mobile layouts, personalization, accessibility, and automatic page refresh. Identifying patterns and trends covers the Analyze feature, grouping, binning and clustering, AI visuals, reference lines, error bars and forecasting, outlier and anomaly detection, and using Copilot to summarize the model.
The exam rewards choosing the right visual for the message, building usable and accessible reports, and using Power BI's analytical and AI features, including Copilot, to surface insight.
How it's tested
PL-300 questions in this domain describe a reporting or analysis need and ask which visual, enhancement or analytical feature to use. PL-300 questions are scenario-based and hands-on, so read the data situation and choose the Power BI feature, DAX pattern or configuration it points to before answering.
-
Choose the visual
A data and message are described, and you choose the appropriate visual or report type.
-
Enhance the report
A usability or navigation need is described, and you choose bookmarks, drillthrough, sync slicers or another feature.
-
Analyze and find insight
An analytical need is described, and you choose the AI visual, forecasting, anomaly detection or Copilot feature.
A report must let users click a product in a summary page and jump to a detailed page filtered to that product. A plain filter or slicer does not carry the selected context to another page. Configuring drillthrough, with the detail page set to receive the product as a drillthrough filter, lets users right-click a product and navigate to the filtered detail page, which is the enhancement feature the exam expects for context-carrying navigation.
Functional groups 3
Official functional groups from the Microsoft outline, in outline order.
3.1 Create reportsChoosing and formatting visuals, Copilot, themes, filtering and visual calculations.
- What it means
- This covers selecting an appropriate visual, formatting and configuring visuals, creating a narrative visual with Copilot, applying and customizing a theme, applying conditional formatting, slicing and filtering, using Copilot to create or suggest content for a report page, configuring the report page, choosing when to use a paginated report, and creating visual calculations with DAX.
- What to understand
- Choosing the right visual for the data and message is a core skill: bar and column for comparison, line for trends over time, and so on. Formatting, themes and conditional formatting improve clarity, and slicers and filters focus the data. Copilot can generate narrative visuals and report content. Paginated reports suit pixel-perfect, printable output. Visual calculations compute within a visual.
- How it shows up
- A reporting need is described, and you must choose the visual, formatting, Copilot or paginated-report option.
- Common confusion
- Choosing a visual that does not fit the message, or confusing a standard report with a paginated report for printable output.
3.2 Enhance reports for usability and storytellingBookmarks, drillthrough, interactions, navigation, accessibility and mobile.
- What it means
- This covers configuring bookmarks, custom tooltips, interactions between visuals, report navigation, sorting, sync slicers, grouping and layering with the Selection pane, drillthrough navigation, export settings, mobile layouts, personalization, accessibility, and automatic page refresh.
- What to understand
- Enhancements make reports usable and tell a clear story. Bookmarks capture states for navigation and storytelling, drillthrough carries context to a detail page, sync slicers coordinate filtering across pages, and edit interactions control how visuals affect each other. Designing for mobile and accessibility broadens reach, and automatic page refresh keeps live reports current. These features turn a basic report into a polished one.
- How it shows up
- A usability or navigation need is described, and you must choose the enhancement feature.
- Common confusion
- Confusing drillthrough (carries context to a detail page) with drilldown (navigates a hierarchy within a visual), or bookmarks with filters.
3.3 Identify patterns and trendsAnalyze feature, AI visuals, forecasting, anomalies and Copilot.
- What it means
- This covers using the Analyze feature in Power BI, using grouping, binning and clustering, using AI visuals, using reference lines, error bars and forecasting, detecting outliers and anomalies, and using Copilot to summarize the underlying semantic model.
- What to understand
- Power BI includes analytical and AI features to find insight beyond basic charts: the Analyze feature explains changes, grouping, binning and clustering segment data, AI visuals like key influencers and decomposition tree surface drivers, forecasting projects trends, and anomaly detection flags outliers. Copilot can summarize the model. Knowing which feature answers which analytical question is the skill.
- How it shows up
- An analytical need is described, and you must choose the AI visual, forecasting, anomaly or Copilot feature.
- Common confusion
- Confusing the AI visuals, such as key influencers (drivers of a metric) with the decomposition tree (interactive breakdown).
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Visual selection
Matching the visual to the message.
- Remember
- Bar for comparison, line for trends.
- Tested as
- Reporting questions.
- Trap
- Choosing an ill-fitting visual.
-
Conditional formatting
Formatting values by rules.
- Remember
- Highlights important values.
- Tested as
- Reporting questions.
- Trap
- Overlooking it for emphasis.
-
Copilot in reports
Generates narrative and report content.
- Remember
- Newer PL-300 capability.
- Tested as
- Reporting questions.
- Trap
- Missing the Copilot features.
-
Paginated reports
Pixel-perfect, printable output.
- Remember
- For formatted, printable documents.
- Tested as
- Reporting questions.
- Trap
- Using a standard report for print.
-
Bookmarks
Capture report states for navigation.
- Remember
- For storytelling and toggles.
- Tested as
- Enhancement questions.
- Trap
- Confusing with filters.
-
Drillthrough
Carries context to a detail page.
- Remember
- Right-click to a filtered page.
- Tested as
- Enhancement questions.
- Trap
- Confusing with drilldown.
-
Sync slicers
Coordinate slicers across pages.
- Remember
- Consistent filtering.
- Tested as
- Enhancement questions.
- Trap
- Unsynced slicers across pages.
-
Edit interactions
Control how visuals filter each other.
- Remember
- Set highlight, filter or none.
- Tested as
- Enhancement questions.
- Trap
- Leaving default interactions wrong.
-
Accessibility and mobile
Designing for all users and devices.
- Remember
- Broadens report reach.
- Tested as
- Enhancement questions.
- Trap
- Ignoring accessibility or mobile.
-
AI visuals
Key influencers, decomposition tree.
- Remember
- Surface drivers and breakdowns.
- Tested as
- Analysis questions.
- Trap
- Confusing the AI visuals.
-
Forecasting and anomalies
Projecting trends and flagging outliers.
- Remember
- Built-in analytical features.
- Tested as
- Analysis questions.
- Trap
- Overlooking these features.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Drillthrough vs. drilldown
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Drillthrough | Navigate to a detail page with context | Carries the selected filter | Confusing with drilldown |
| Drilldown | Move through a hierarchy in a visual | Stays in the visual | Confusing with drillthrough |
Standard vs. paginated report
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Standard report | Interactive Power BI report | Exploration and dashboards | Using for pixel-perfect print |
| Paginated report | Pixel-perfect, printable | Formatted documents and tables | Using for interactive exploration |
Key influencers vs. decomposition tree
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Key influencers | Shows drivers of a metric | What influences an outcome | Confusing with the tree |
| Decomposition tree | Interactive breakdown by dimension | Drill into contributing factors | Confusing with key influencers |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Filter instead of drillthrough
- What candidates pick
- Use a page filter to let users jump to product detail with context.
- Why it looks right
- Filters control data.
- Why it's wrong
- Drillthrough carries the selected item's context to a dedicated detail page; a page filter does not provide that navigation.
Clue to watch for Users should click an item and navigate to a filtered detail page.
-
Standard report for print
- What candidates pick
- Use a standard interactive report for a precisely formatted, printable invoice.
- Why it looks right
- It is the usual report type.
- Why it's wrong
- Paginated reports provide pixel-perfect, printable output suited to formatted documents and large tables.
Clue to watch for The output must be printed with exact formatting.
-
Wrong visual
- What candidates pick
- Use a pie chart to show a trend over many time periods.
- Why it looks right
- Pie charts are familiar.
- Why it's wrong
- A line chart shows trends over time; a pie chart is for part-to-whole with few categories.
Clue to watch for The message is a trend across time.
-
Unsynced slicers
- What candidates pick
- Add separate slicers on each page and expect them to stay in sync.
- Why it looks right
- Each page has its slicer.
- Why it's wrong
- Sync slicers coordinate the same slicer across pages so filtering stays consistent.
Clue to watch for Filtering should carry across report pages.
-
Ignore accessibility
- What candidates pick
- Design a report without considering accessibility or mobile layouts.
- Why it looks right
- The desktop report looks fine.
- Why it's wrong
- Accessibility features and mobile layouts ensure the report works for all users and devices, which the exam expects.
Clue to watch for The report must serve diverse users and devices.
Answer framework
For any Domain 3 scenario, use these steps to find the answer PL-300 expects.
- Choose the visual that fits the data and message, using the right chart type and paginated reports for printable output.
- Format with themes and conditional formatting, apply slicers and filters, and use Copilot to help generate report content.
- Enhance usability with bookmarks, drillthrough for context navigation, sync slicers, and correct edit interactions.
- Design for accessibility and mobile, and use automatic page refresh for live data.
- Find insight with the Analyze feature, AI visuals, forecasting and anomaly detection, and use Copilot to summarize the model. Where two options seem to fit, choose the one that most precisely matches the scenario's data, message or requirement.
Practice question
Want more like this? The PL-300 practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Approach this domain as turning the model into clear, usable insight, and practice building reports in Power BI Desktop. Start with visual selection, learning which chart fits which message (comparison, trend, part-to-whole, distribution), and when a paginated report is needed for print. Practice formatting, themes and conditional formatting.
Then master the enhancement features, which are heavily tested: bookmarks for navigation and storytelling, drillthrough for context-carrying navigation (distinct from drilldown), sync slicers, edit interactions, and designing for accessibility and mobile. Learn the analytical and AI features, the Analyze feature, key influencers and decomposition tree, forecasting and anomaly detection, and the newer Copilot capabilities the current outline adds.
Because the exam tests doing and the current features, build an interactive, accessible report using drillthrough, bookmarks and an AI visual. Because PL-300 is hands-on, practice every task in Power BI Desktop and the Power BI service with real data rather than only reading, and review missed practice questions by domain to find weak spots. Afterwards, move to Domain 4, Manage and secure Power BI.
FAQ
How much of PL-300 is Domain 3?
Visualize and analyze the data is 25–30% of the exam, one of three equally weighted largest domains, covering reporting and analysis.
How do I choose the right visual?
Match the visual to the message: column or bar charts for comparisons, line charts for trends over time, pie or donut for part-to-whole with few categories, scatter for relationships, and tables or matrices for detail. The message and data shape determine the choice.
What is the difference between drillthrough and drilldown?
Drillthrough navigates to a separate detail page carrying the selected item's context as a filter. Drilldown moves through a hierarchy within the same visual, such as from year to quarter to month.
When should I use a paginated report?
For pixel-perfect, printable output such as formatted invoices, statements or large detailed tables. Standard Power BI reports are interactive and suited to exploration and dashboards rather than precise print layouts.
What do sync slicers do?
They coordinate the same slicer across multiple report pages so that a selection on one page applies consistently on the others, keeping filtering in sync across the report.
What Copilot and AI features does PL-300 now cover?
The current outline includes using Copilot to create narrative visuals, suggest and create report content, and summarize the semantic model, plus AI visuals like key influencers and the decomposition tree, forecasting, and anomaly detection.
How does Domain 3 connect to the rest of the exam?
The reports here visualize the model from Domain 2, built on the data prepared in Domain 1, and the reports and workspaces are then managed, shared and secured in Domain 4.
Test your Domain 3 knowledge
You have covered visual selection, report enhancement and analytical and AI features. Test whether you can build usable, insightful reports under exam conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the PL-300 AI tutor Get any concept explained your way