Microsoft Power BI Quiz: Report Tooltips
10 questions · exam conditions
0:00
Report TooltipsQuestion 1 of 10

You have two enabled tooltip pages: Summary Tooltip and Margin Tooltip. Both are associated with Product[Category]. A product chart must always use Margin Tooltip, even if Power BI would automatically select Summary Tooltip.

What should you configure on the product chart?

Set the chart's tooltip type to Default and select Margin Tooltip as its drillthrough page.
Set the chart's tooltip type to Report page and select Margin Tooltip as the page.
Remove Product[Category] from the chart and add it only to Margin Tooltip's filters.
Set the chart's tooltip type to Auto and move Margin Tooltip before Summary Tooltip.
← Back to quizzes

Microsoft Power BI Quiz

Microsoft Power BI Quiz: Report Tooltips

Practice Report Tooltips in Microsoft Power BI with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Report Tooltips, giving you a quick way to practice the rules, question types, and explanations that matter most for Microsoft Power BI.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

You have two enabled tooltip pages: Summary Tooltip and Margin Tooltip. Both are associated with Product[Category]. A product chart must always use Margin Tooltip, even if Power BI would automatically select Summary Tooltip.

What should you configure on the product chart?

  1. Set the chart's tooltip type to Default and select Margin Tooltip as its drillthrough page.
  2. Set the chart's tooltip type to Report page and select Margin Tooltip as the page. (correct answer)
  3. Remove Product[Category] from the chart and add it only to Margin Tooltip's filters.
  4. Set the chart's tooltip type to Auto and move Margin Tooltip before Summary Tooltip.
Explanation: When Power BI has multiple report page tooltips associated with the same field, it uses an automatic selection process — and that automatic choice may not be the one you want. This question tests whether you understand how to override that automatic selection on a specific visual. To force a particular visual to always use a specific tooltip page, you go into that visual's Format pane, set the Tooltip type to Report page, and then manually select the desired page — in this case, Margin Tooltip. This gives you explicit, deterministic control regardless of what Power BI would choose automatically. That's exactly what option B describes, making it the correct answer. Option A is wrong because setting the tooltip type to "Default" surrenders control back to Power BI's automatic logic, and drillthrough pages are a completely separate feature from tooltips — mixing those two concepts is a classic trap on this exam. Option C is wrong because removing Product[Category] from the chart would break the visualization itself; tooltip page filters determine eligibility, not override priority for a specific visual. Option D is wrong because tooltip page ordering is not a feature Power BI uses to resolve conflicts between enabled tooltip pages — there is no "first wins" ordering rule, so reordering pages has no effect on which tooltip a visual displays. The key study takeaway: whenever a question asks how to guarantee a specific tooltip on a visual regardless of automatic selection, think Format pane → Tooltip → Report page → choose the page. "Auto" and "Default" both cede control to Power BI; only "Report page" lets you pin your choice.

Question 2

A sales page is filtered by a Date[Year] slicer and a Region[Region] slicer. A report tooltip is displayed when users hover over a product. Most tooltip visuals should respect the product, year, and region context. One card on the tooltip must show lifetime sales for the hovered product and region while ignoring only the year selection.

Which design best meets the requirement?

  1. Remove Date[Year] from the tooltip page and use the ordinary Sales measure on the card.
  2. Disable interactions from the year slicer to the source visual that launches the tooltip.
  3. Use a card measure that removes Date filters while retaining the product and region context. (correct answer)
  4. Add a second year slicer to the tooltip page and leave it without a selection.
Explanation: When a report tooltip inherits filter context from the source page, every active filter — slicers, cross-filters, and visual-level filters — flows into the tooltip. The challenge here is surgical: you need to strip out only the year filter while keeping product and region context intact on a single card, without disturbing the other tooltip visuals. The cleanest solution is a DAX measure that uses REMOVEFILTERS (or ALL) targeting only the Date table or Date[Year] column. Something like CALCULATE([Sales], REMOVEFILTERS(Date[Year])) evaluates lifetime sales within whatever product and region context is active, which is exactly what the requirement describes. That's why C is correct — it applies the filter manipulation at the measure level, precisely and without side effects. A is wrong because removing Date[Year] from the tooltip page entirely would break the other visuals that should respect the year selection. You'd lose year context for everything, not just that one card. B is tempting but misunderstands how tooltip filter context works. Disabling interactions from the year slicer to the source visual changes what the source visual shows — it doesn't change the filter context passed to the tooltip. The tooltip still inherits the slicer's filter. D adds a year slicer to the tooltip page with no selection, but the inherited year filter from the source page would still override or conflict with it. Tooltip pages don't neutralize inherited context this way. A useful rule of thumb: whenever you need to selectively ignore one filter while preserving others, reach for CALCULATE with a targeted REMOVEFILTERS — that's DAX's scalpel for filter context manipulation.

Question 3

A tooltip page is working correctly, but report consumers can also select it from the page tabs and view it as a mostly empty report page. You need to remove it from normal navigation without breaking its tooltip behavior.

Which action should you take?

  1. Delete the tooltip page after assigning it to all required visuals.
  2. Hide the tooltip page while leaving its tooltip settings enabled. (correct answer)
  3. Disable Allow use as tooltip and retain its visual assignments.
  4. Replace the tooltip page with a hidden drillthrough destination.
Explanation: When working with tooltip pages in Power BI, you need to understand that two independent settings control their behavior: the tooltip designation (set in Page Information under Format) and the page visibility. These settings operate separately, which is exactly what this question tests. To solve the problem — keeping tooltip functionality intact while hiding the page from normal navigation — you simply hide the page by right-clicking its tab and selecting Hide Page. Hidden pages are invisible to report consumers browsing tabs, but Power BI's tooltip engine still recognizes and renders them when a user hovers over an assigned visual. This is option B, and it's the correct approach because it addresses both requirements simultaneously without breaking anything. Option A is wrong because deleting the page would destroy the tooltip entirely — you can't assign visuals to a page that no longer exists. Option C traps you with a logical contradiction: disabling "Allow use as tooltip" turns the page back into a regular report page, removing its tooltip function and defeating the entire purpose. The visual assignments would also become meaningless without the tooltip setting active. Option D introduces drillthrough pages, which are an entirely different feature used for navigating to filtered detail views — they don't function as hover tooltips at all, making this a category error. A useful rule of thumb: in Power BI, visibility and functionality are often decoupled. Hidden pages, hidden visuals, and disabled interactions can preserve underlying behavior while changing what users see. On exam questions about page management, always ask yourself whether the setting you're changing affects display or function — they're frequently independent.

Question 4

A manager wants a tooltip to contain a slicer and a button. After hovering over a data point, the manager expects to change the slicer and then select the button to open a detailed page. The tooltip currently disappears when the pointer leaves the source data point.

Which design should you recommend?

  1. Keep the report tooltip and enable persistent hover mode on its slicer and button.
  2. Convert the tooltip button to a bookmark navigator and enable visual headers.
  3. Increase the tooltip canvas size so users can move the pointer into the tooltip.
  4. Use a drillthrough page for the interactive analysis and keep the tooltip informational. (correct answer)
Explanation: When you see a question about Power BI tooltips with interactive elements, ask yourself a fundamental question: can report tooltips actually support sustained user interaction? The answer is no — by design, report tooltips are transient overlays that disappear the moment your pointer leaves the source visual. They are built for displaying information, not receiving input. This is why D is correct. A drillthrough page is a dedicated report page that users navigate to intentionally, where slicers, buttons, and other interactive elements work as expected. The manager's real goal is interactive analysis — filtering data and triggering navigation — which drillthrough pages are purpose-built to support. The tooltip can still exist to surface summary information on hover, while the drillthrough handles the heavy lifting. A misrepresents how Power BI works. There is no "persistent hover mode" for tooltips — this feature simply doesn't exist. A slicer inside a tooltip cannot be meaningfully interacted with because the tooltip closes before the user can click anything. B introduces a bookmark navigator, which is a valid Power BI feature, but placing one inside a tooltip doesn't solve the core problem: the tooltip still disappears on pointer-leave. Converting the button type doesn't change the tooltip's transient behavior. C is a plausible-sounding workaround, but increasing the canvas size does not prevent the tooltip from closing when the pointer exits the source data point. The tooltip boundary behavior is not tied to canvas dimensions. Your study tip: tooltips = read-only, drillthrough = interactive. On the PL-300 exam, any scenario requiring user input within a tooltip is a signal to recommend drillthrough instead.

Question 5

A custom report tooltip named Customer Preview was created in Report A. Report B uses a different semantic model but contains equivalent customer fields. An author attempts to select Customer Preview as the tooltip page for a visual in Report B, but the page is unavailable.

What should the author do?

  1. Publish both reports to the same workspace and assign the page after publication.
  2. Enter Report A's URL as the report tooltip page for the visual in Report B.
  3. Create or copy an equivalent enabled tooltip page into Report B and validate its fields. (correct answer)
  4. Configure Customer Preview as cross-report drillthrough and select it as the tooltip.
Explanation: When working with report tooltips in Power BI, it's essential to understand that tooltip pages are scoped to the report they live in. They are not shared assets that other reports can reference — each report manages its own tooltip pages independently, tied to its own data model and field structure. Because tooltip pages belong to their host report, the only way to use a custom tooltip in Report B is to have that page exist within Report B itself. The author must either recreate the tooltip page from scratch or copy it into Report B, then ensure the page is enabled as a tooltip and that all fields referenced on it map correctly to Report B's semantic model. This is exactly what C describes, making it the correct answer. Option A is a trap — publishing reports to the same workspace enables cross-report drillthrough, not tooltip sharing. Workspace proximity has no effect on tooltip page availability across reports. Option B is simply not a feature Power BI supports; you cannot reference another report's URL as a tooltip source for a visual. Option D confuses two distinct features: cross-report drillthrough allows navigation between reports on user interaction, but it is not a mechanism for tooltip display and cannot be configured as one. A useful rule of thumb: tooltip pages and drillthrough pages are report-local. If something needs to work in a report, it needs to exist in that report. On the exam, watch for questions that tempt you to "share" page-level features across reports — Power BI doesn't work that way, and the correct answer will almost always involve recreating or copying the asset into the target report.

Question 6

You want a custom report tooltip to appear only on a matrix. Other visuals use the same Product[Category] field but must retain their standard tooltips. The custom page is enabled for tooltip use.

Which configuration best avoids unintentionally applying the custom tooltip to the other visuals?

  1. Add Product[Category] to the page's Tooltip fields and leave every visual on the page set to Auto.
  2. Assign the custom tooltip page to every visual on the report page and then disable cross-highlighting for the non-matrix visuals.
  3. Hide the custom tooltip page and add Product[Category] as a report-level filter to restrict its scope.
  4. Leave the Tooltip fields on the custom page unconfigured and explicitly assign the custom page to the matrix only. (correct answer)
Explanation: When working with custom report tooltips in Power BI, you need to understand two distinct mechanisms for controlling which visuals use a custom tooltip page: the Tooltip fields on the custom page (which enables automatic matching) and the explicit assignment at the visual level (which gives you direct, intentional control). If you leave the Tooltip fields on the custom page empty and instead go directly to the matrix's Format pane to assign the custom tooltip page, only that matrix will display it — regardless of what fields other visuals share. This is exactly what option D describes, and it's the safest, most targeted approach. Option A is the classic trap. Adding Product[Category] to the page's Tooltip fields tells Power BI to automatically apply that tooltip to any visual using that field. Since your other visuals also use Product[Category], they'd all inherit the custom tooltip — the opposite of what you want. Option B misunderstands the purpose of cross-highlighting. Disabling cross-highlighting affects how visuals interact during selections, not whether a custom tooltip appears. This configuration doesn't restrict tooltip behavior at all. Option C introduces confusion between page visibility and tooltip scope. Hiding a tooltip page is actually required for it to function as a tooltip, but adding a report-level filter on Product[Category] doesn't restrict which visuals display the tooltip — it filters the data shown across the report, which is an entirely different thing. As a study tip, remember this rule of thumb: explicit beats automatic. Whenever you want precise tooltip targeting, skip the Tooltip fields and assign the page directly to the specific visual.

Question 7

You create a page named Product Tooltip that contains a card and a small bar chart. You want the page to appear as a report tooltip when users hover over product data points. The page currently appears as a normal full-sized report page.

Which page-level setting is essential to make the page available for selection as a report tooltip?

  1. Set the page view to Fit to page and hide the Filters pane.
  2. Set the canvas page type to Tooltip and enable Allow use as tooltip. (correct answer)
  3. Enable Maintain layer order and hide the page from navigation.
  4. Set the display mode to Actual size and enable persistent filters.
Explanation: When working with report tooltips in Power BI, you need to understand that a tooltip page isn't just any page — it requires specific configuration to signal to Power BI that it should behave as a hoverable overlay rather than a standard report page. To enable this behavior, you must open the page's Format settings, change the Canvas type to "Tooltip," and toggle on Allow use as tooltip. These two settings work together: changing the canvas type resizes the page to tooltip dimensions and registers it as a tooltip candidate, while the toggle makes it selectable when you configure visuals to use custom tooltips. This is exactly what option B describes, making it the correct answer. Option A is a trap — "Fit to page" is a view setting that controls how the page displays in your browser window, not how it functions. Hiding the Filters pane is a cosmetic choice, not a functional requirement for tooltips. Option C references "Maintain layer order," which is a selection/rendering feature unrelated to tooltip configuration entirely; hiding the page from navigation is sometimes done alongside tooltip setup but is not the essential setting that enables tooltip availability. Option D mentions "Actual size" display mode and persistent filters — neither of these has any bearing on tooltip page registration. A useful memory anchor: think of it as a two-key lock — canvas type plus the tooltip toggle. If either is missing, the page won't appear as an option when you try to assign a custom tooltip to a visual. On the Power BI exam, watch for questions that isolate one configuration step — the correct answer will always target the setting that enables the feature, not one that merely adjusts appearance.

Question 8

All visuals on an executive page should display a custom report tooltip except one KPI visual, which must display no tooltip. The custom tooltip page must remain available to the other visuals.

What should you do?

  1. Turn off Tooltips in the KPI visual's formatting settings only. (correct answer)
  2. Disable Allow use as tooltip on the custom tooltip page.
  3. Remove all Tooltip fields from the custom tooltip page.
  4. Hide the KPI visual by using the Selection pane.
Explanation: When working with tooltips in Power BI, it's important to understand that tooltip behavior is controlled at two levels: the page level (where you configure a page as a tooltip) and the visual level (where individual visuals can opt in or out). This question tests whether you know how to selectively exclude one visual from a shared tooltip experience without disrupting everyone else. The correct approach is A — turning off Tooltips in the KPI visual's formatting settings. Every visual in Power BI has a "Tooltips" toggle under its Format pane. Setting it to off for just that one KPI suppresses its tooltip entirely, while all other visuals continue using the custom tooltip page normally. This is a surgical, visual-level fix that doesn't touch the page configuration. B is wrong because disabling "Allow use as tooltip" on the custom tooltip page removes it from all visuals simultaneously — the exact opposite of what the scenario requires, which is keeping it available for the other visuals. C is similarly destructive. Removing Tooltip fields from the custom tooltip page would break the tooltip for every visual on the report page, not just the KPI. D is a trap. Hiding a visual via the Selection pane controls its visibility in the report canvas — it doesn't affect tooltip behavior at all, and it would remove the KPI from view entirely, which isn't the goal. A useful study tip: on the Power BI exam, when a question asks you to affect one visual without changing behavior for others, the answer almost always involves that visual's individual formatting settings rather than a page-level or dataset-level change.

Question 9

A page named Regional Details has been formatted with the Tooltip canvas page type. When you configure a chart to use a report page tooltip, Regional Details does not appear in the Page list. Other tooltip pages do appear.

What is the most likely change required on Regional Details?

  1. Enable Allow use as tooltip in the page information settings. (correct answer)
  2. Add the chart's measure to the page-level filter pane.
  3. Hide Regional Details from the report page navigation.
  4. Change the page view from Fit to page to Actual size.
Explanation: When working with report page tooltips in Power BI, there are two distinct steps to creating a functional tooltip page: setting the canvas type to Tooltip and explicitly enabling the page for tooltip use. Many students miss that second step, which is exactly what this question tests. The page Regional Details has the correct canvas type already applied, but it's still not appearing in the tooltip Page list. This happens because Power BI requires you to also toggle on "Allow use as tooltip" within the page information settings panel. Without this flag enabled, Power BI simply won't expose the page as a selectable tooltip option on other visuals — even if the canvas type is correctly set. Enabling this setting, answer A, resolves the issue directly. Answer B is a distractor that confuses tooltip configuration with filter behavior. Adding a measure to the page-level filter affects what data is shown, not whether the page appears in the tooltip selection list. Answer C — hiding the page from navigation — is actually a recommended best practice for tooltip pages so they don't clutter your navigation bar, but it has no bearing on whether the page appears in the tooltip Page list. In fact, you can hide a page and it will still appear as a tooltip option once properly configured. Answer D is irrelevant entirely; page view zoom settings control how the canvas renders visually and have no effect on tooltip availability. As a study tip, remember the two-step rule for tooltip pages in Power BI: set the canvas type to Tooltip, then enable "Allow use as tooltip" in page information. Forgetting either step is a common real-world (and exam) mistake.

Question 10

A report tooltip page has Allow use as tooltip enabled. You add Product[Category] to the page's Tooltip fields. A column chart on another page uses Product[Category] on its axis, and its tooltip configuration remains set to Auto.

What should occur when a user hovers over a category column?

  1. Power BI can automatically display the report tooltip page filtered to the hovered category. (correct answer)
  2. Power BI displays only the default tooltip until the page is explicitly assigned to the chart.
  3. Power BI opens the report tooltip page as a drillthrough destination for the selected category.
  4. Power BI displays the tooltip page without category filtering because Auto removes hover context.
Explanation: When working with report tooltips in Power BI, it helps to understand the two mechanisms at play: the tooltip page setup and the visual's tooltip configuration. These work together, and knowing how they interact is exactly what this question tests. Power BI's Auto tooltip setting is the key here. When a visual's tooltip is set to Auto, Power BI automatically scans all report tooltip pages and checks whether their Tooltip fields match the fields used in the visual. If a tooltip page has "Allow use as tooltip" enabled and its Tooltip fields include a field that the visual already uses — in this case, Product[Category] on the axis — Power BI will automatically serve that tooltip page when the user hovers, filtered to the specific category being hovered. No manual assignment is needed. This makes A the correct answer. B is incorrect because it describes behavior that would apply if the tooltip were set to a specific page manually, or if Auto didn't find a matching field. Since the fields do match, Auto handles the connection without explicit assignment. C confuses tooltip functionality with drillthrough — drillthrough is a separate feature that navigates to a destination page on click, not on hover. These are distinct interactions and should not be mixed up. D is the opposite of how Auto works; rather than removing hover context, Auto actively uses the hover context to filter the tooltip page to the relevant category. As a study tip, remember that Auto = smart matching: Power BI compares tooltip page fields against visual fields automatically. If they align, the tooltip activates without any manual wiring.