Microsoft Power BI Quiz: Bookmarks And Buttons For Navigation
10 questions · exam conditions
0:00
Bookmarks And Buttons For NavigationQuestion 1 of 10

A report contains an Overview page and a Profitability page. A slicer selection made on the Overview page must remain active when a user selects a button labeled Continue to Profitability. The button must participate in a bookmark-based story rather than use ordinary page navigation.

How should you configure the button and its bookmark?

Create the bookmark on Profitability with Current page enabled and Data disabled, and set the button action to that bookmark.
Create the bookmark on Profitability with Current page and Data enabled, and set the button action to that bookmark.
Create the bookmark on Profitability with Current page disabled and Data enabled, and set the button action to that bookmark.
Create the bookmark on Overview with Current page enabled and Data disabled, and set the button action to Page navigation.
← Back to quizzes

Microsoft Power BI Quiz

Microsoft Power BI Quiz: Bookmarks And Buttons For Navigation

Practice Bookmarks And Buttons For Navigation 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 Bookmarks And Buttons For Navigation, 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

A report contains an Overview page and a Profitability page. A slicer selection made on the Overview page must remain active when a user selects a button labeled Continue to Profitability. The button must participate in a bookmark-based story rather than use ordinary page navigation.

How should you configure the button and its bookmark?

  1. Create the bookmark on Profitability with Current page enabled and Data disabled, and set the button action to that bookmark. (correct answer)
  2. Create the bookmark on Profitability with Current page and Data enabled, and set the button action to that bookmark.
  3. Create the bookmark on Profitability with Current page disabled and Data enabled, and set the button action to that bookmark.
  4. Create the bookmark on Overview with Current page enabled and Data disabled, and set the button action to Page navigation.
Explanation: When working with Power BI bookmarks, you need to understand three key bookmark properties: Current page (which page the bookmark navigates to), Data (which captures slicer/filter state), and Display (which captures visual visibility). The goal here is to navigate to Profitability without overwriting the slicer selections the user made on Overview. Answer A is correct because creating the bookmark on the Profitability page with Current page enabled ensures the button navigates there, while Data disabled means the bookmark does not capture or restore a specific filter/slicer state — so whatever the user selected on Overview carries forward naturally through the report's cross-page filter context. This is precisely the bookmark-based story pattern Power BI recommends. Answer B is wrong because enabling Data alongside Current page causes the bookmark to freeze a specific slicer state at the time the bookmark was created. When triggered, it restores that frozen state, overwriting the user's Overview selections — the opposite of what you want. Answer C fails because disabling Current page means the bookmark won't navigate to Profitability at all. The page switch simply won't happen, breaking the story flow entirely. Answer D is a trap for students who confuse bookmark actions with page navigation actions. Setting the button action to Page navigation bypasses the bookmark system entirely, which violates the requirement to participate in a bookmark-based story. The bookmark is also created on the wrong page. Study tip: Remember the bookmark property rule: disable Data when you want user-driven slicers to persist across pages; enable Data only when you want to lock a specific filter snapshot.

Question 2

A report page contains an instruction panel, a Show help button, a Hide help button, and several analytical visuals. Two bookmarks must toggle the panel and the two buttons without changing filters, sorting, or the visibility of unrelated visuals.

Which bookmark configuration best meets the requirement?

  1. Select the panel and both buttons, use Selected visuals, enable Display, disable Data, and create the shown and hidden bookmarks. (correct answer)
  2. Select the panel and both buttons, use Selected visuals, disable Display, enable Data, and create the shown and hidden bookmarks.
  3. Select every object on the page, use All visuals, enable Display and Data, and create the shown and hidden bookmarks.
  4. Select only the analytical visuals, use Selected visuals, enable Display, disable Data, and create the shown and hidden bookmarks.
Explanation: When working with Power BI bookmarks, you need to think carefully about two independent settings: what gets captured (Selected vs. All visuals) and which properties get captured (Display, Data, Current page, etc.). Questions like this test whether you can isolate exactly the right objects and properties to avoid unintended side effects. The requirement here is surgical: toggle only the panel and two buttons, touching nothing else — no filters, no sorting, no other visuals. That means you should select only those three objects and use Selected visuals, so the bookmark ignores everything else on the page. You need Display enabled because you're literally showing and hiding objects. You need Data disabled because capturing data properties (filters, slicers, sorting) would change the report's analytical state when a user clicks the bookmark — violating the requirement. Option A does exactly this: selects the right objects, scopes to Selected visuals, enables Display, and disables Data. Option B fails because it disables Display and enables Data — the exact opposite logic. It would capture filter/sort state instead of visibility, meaning the panel wouldn't actually appear or disappear. Option C captures every object on the page with All visuals and enables Data, which means toggling the help panel would also reset filters and sorting on your analytical visuals — a clear violation of the requirement. Option D selects the wrong objects entirely (the analytical visuals instead of the panel and buttons), so the bookmark would control the wrong elements. A useful rule of thumb: whenever a bookmark should only affect visibility, select just those objects, use Selected visuals, enable Display, and disable Data. This combination gives you a "purely cosmetic" bookmark.

Question 3

A report should automatically list its visible report pages and reflect page renames and reordering. A hidden Detail page must not appear in that list, but users must be able to open Detail from dedicated buttons on several summary pages.

Which design should you implement?

  1. Use a Page navigator that includes every page and make the Detail page button transparent in the navigator formatting.
  2. Use a Bookmark navigator for visible pages and unhide the Detail page whenever a user needs to navigate to it.
  3. Use standard bookmark buttons for every visible page and configure a Web URL action for the hidden Detail page.
  4. Use a Page navigator for visible pages and configure each dedicated button with a Page navigation action to the hidden Detail page. (correct answer)
Explanation: When designing navigation in Power BI, you need to match each tool to what it was built to do. The Page navigator visual is specifically designed to auto-populate with report pages, reflect renames and reordering dynamically, and — critically — respect page visibility settings. That makes it the right foundation for this scenario. Option D is the correct design because it uses a Page navigator scoped to visible pages only, which automatically excludes the hidden Detail page and stays current without manual maintenance. The dedicated buttons on summary pages then use a Page navigation action pointing directly to the hidden Detail page, which Power BI fully supports — hidden pages are still navigable via explicit actions even though they're invisible in the navigator. This cleanly separates the two navigation patterns the requirements demand. Option A fails because making a button transparent doesn't remove it from the navigator's logic or prevent accidental interaction — it's a cosmetic workaround, not a real solution, and the hidden page would still technically be "included." Option B introduces unnecessary complexity. Unhiding the Detail page dynamically requires bookmark management and defeats the purpose of keeping it hidden; it also risks the page briefly appearing in the navigator during state transitions. Option C abandons the Page navigator entirely in favor of manual bookmark buttons, meaning you lose the automatic renaming and reordering behavior the requirements explicitly demand. A Web URL action for a hidden page is also an unreliable workaround that breaks in embedded or restricted environments. The key study tip: on Power BI exam questions, whenever you see requirements for automatic page list maintenance plus selective navigation to hidden pages, think Page navigator (visible) + Page navigation action.

Question 4

Users can open a Product Detail page from either a Sales page or an Inventory page. The Product Detail page needs one button that returns each user to whichever report page they visited immediately before opening Product Detail.

Which button action should you configure?

  1. Configure a Bookmark action that stores the default state of the Product Detail page.
  2. Configure a Page navigation action with Sales as the button's fixed destination.
  3. Configure a Back action so the button follows the user's report navigation history. (correct answer)
  4. Configure a Drill through action with Inventory as the fixed destination page.
Explanation: When designing navigation in Power BI reports, the key question to ask is: does the destination need to be fixed, or does it depend on where the user came from? This question tests whether you understand dynamic vs. static navigation actions. The scenario describes a page that can be reached from multiple sources, and the button must return users to whichever page they came from — that's inherently dynamic. The Back action (C) is built exactly for this purpose: it reads the user's navigation history and returns them to the previously visited page, regardless of where that was. No additional configuration is needed beyond selecting "Back" as the action type. Choice A is a trap because Bookmarks capture a snapshot of a page's visual state (filters, visibility, slicer selections) — they're for restoring a specific view, not for navigating backward through history. Applying a bookmark doesn't know or care where the user came from. Choice B is wrong because Page navigation always routes to a fixed, predetermined page. If you hardcode Sales as the destination, users arriving from Inventory will be sent to the wrong page — exactly the problem you're trying to avoid. Choice D misapplies Drill through, which is designed for passing filter context forward into a detail page, not for returning users to a previous page. Setting Inventory as a fixed drill-through destination also ignores the dynamic requirement entirely. Study tip: On the Power BI exam, whenever a question mentions "whichever page the user came from" or returning to a variable prior page, that's your signal to choose the Back action — it's the only action type that respects navigation history dynamically.

Question 5

A button has Action enabled and is assigned to a valid bookmark. It works when the report is opened in reading view in the Power BI service. In Power BI Desktop edit mode, an author selects the button with a normal click and concludes that the bookmark action is broken.

What should the author do to test the action in Power BI Desktop?

  1. Double-click the button so Desktop opens the bookmark without entering object-selection mode.
  2. Hold Shift while selecting the button so Desktop temporarily switches the report into reading view.
  3. Hold Ctrl while selecting the button so Desktop follows the configured action instead of selecting the object. (correct answer)
  4. Disable the Selection pane before selecting the button so Desktop automatically invokes its assigned action.
Explanation: When working with interactive elements like buttons in Power BI Desktop, you need to understand a fundamental behavioral difference between edit mode and reading view. In edit mode, clicking any visual or object selects it for editing — Desktop assumes you want to manipulate the object, not interact with it as an end user would. This is why a normal click on a button won't trigger its bookmark action, even if that action is perfectly configured. To simulate end-user behavior while still in edit mode, you hold Ctrl while clicking the button. This tells Power BI Desktop to follow the button's assigned action — navigating to the bookmark — rather than entering object-selection mode. So C is correct: the bookmark action isn't broken at all; the author simply needs to use Ctrl+Click to test it properly. Choice A is wrong because double-clicking a button in Desktop typically enters text-editing mode for the button label, not action execution. Choice B is the most tempting distractor — Shift+Click is commonly used in many tools for multi-selection, not for switching behavioral modes, and it has no special "reading view simulation" behavior in Power BI Desktop. Choice D is incorrect because the Selection pane controls object visibility and layering; disabling it has no effect on how button actions are triggered. A handy study tip: remember the Ctrl+Click = action trigger rule as the Desktop equivalent of a reader's click. On the exam, if you see a scenario where a button or link "doesn't work" in Desktop, the answer almost always involves Ctrl+Click rather than a configuration problem.

Question 6

An analyst creates a bookmark while a card displays last month's revenue. After the semantic model refreshes, a manager selects the bookmark and expects the card to show the exact old revenue total that was visible when the bookmark was created.

What should the analyst explain?

  1. The bookmark stores a copy of each visual's result, so the old card total should return after every refresh.
  2. The bookmark restores captured report state, but the card recalculates from current model data under that restored state. (correct answer)
  3. The bookmark stores imported rows for the page, but only when its Data option is enabled during creation.
  4. The bookmark restores old values only when invoked by a button rather than from the Bookmarks pane.
Explanation: Whenever you see a Power BI question about bookmarks, anchor your thinking to what a bookmark actually captures: report state, not data snapshots. A bookmark records things like filter selections, slicer positions, visual visibility, and page context — it is essentially a saved configuration of how the report looks and behaves, not a frozen copy of query results. This is exactly why B is correct. When the manager selects the bookmark, Power BI restores the captured state (filters, slicers, visual settings), and then the card visual recalculates its value by querying the underlying semantic model using that restored state. If the model has refreshed with new data, the card will reflect the updated numbers — not the old ones. The bookmark never preserved the revenue figure itself. A is the most tempting wrong answer because it sounds intuitive — people often assume bookmarks work like screenshots. They do not. No visual result is ever stored inside a bookmark. C introduces a believable-sounding detail about a "Data" option, but while bookmarks do have a Data toggle (which controls whether cross-filter/highlight state is captured), this setting does not cause the bookmark to cache actual imported rows or historical metric values. D is simply fabricated — the bookmark behaves identically whether triggered from the Bookmarks pane or a button; the invocation method changes nothing about how data is retrieved. Your study tip: remember the phrase "state, not data." Bookmarks save how the report is configured, and visuals always recalculate live from the model under that configuration. Any answer claiming bookmarks store historical query results is a trap.

Question 7

A report contains eight bookmarks. Five are story scenes and three are utility bookmarks used to open and close panels. Users should see navigation choices only for the five story scenes. If a story bookmark is renamed or reordered, the navigation control should update automatically.

What should you do?

  1. Place the five story bookmarks in a bookmark group and configure a Bookmark navigator to use that group. (correct answer)
  2. Place all eight bookmarks in one group and hide the utility bookmarks by changing their button text color.
  3. Create five standard buttons with bookmark actions and manually synchronize their labels and positions after every change.
  4. Create a Page navigator and configure each story bookmark as a hidden report page in the Pages pane.
Explanation: When a question describes a mix of "real" navigation bookmarks and behind-the-scenes utility bookmarks, your focus should be on Power BI's Bookmark navigator and bookmark groups — the built-in tools designed to solve exactly this problem. Power BI lets you organize bookmarks into named groups. A Bookmark navigator visual can then be pointed at a specific group, displaying only the bookmarks inside it. Crucially, it reads the group's contents dynamically: if you rename or reorder a bookmark within that group, the navigator updates automatically — no manual rework required. Option A does precisely this: isolating the five story bookmarks in their own group gives users a clean navigation experience while the three utility bookmarks remain invisible to the control. Option B is a cosmetic workaround, not a real solution. Hiding buttons by matching their text color to the background is fragile, unprofessional, and doesn't actually remove the utility bookmarks from the navigator's logic — they can still be stumbled upon. Option C describes a fully manual process. Creating individual buttons with bookmark actions means you must update labels, positions, and actions yourself every time a bookmark changes. This directly contradicts the requirement for automatic updates and introduces ongoing maintenance burden. Option D confuses two separate features. Page navigators surface report pages, not bookmarks. Bookmarks and pages are distinct objects in Power BI, and you cannot configure a bookmark as a "hidden report page." A useful pattern to remember: whenever a question mentions navigation that must auto-update after bookmark changes, the answer almost always involves a Bookmark navigator tied to a bookmark group — that pairing is Power BI's purpose-built solution.

Question 8

A report author needs a Reset this page button. It must restore all slicers and Filter pane filters to their authored defaults. It must not navigate to another page or restore saved visibility states for pop-up panels. The button will be used only on the page where the bookmark is created.

Which bookmark settings should the author use?

  1. Enable Data, disable Display and Current page, select only the page background, and assign the bookmark to the button.
  2. Disable Data, enable Display and Current page, select All visuals, and assign the bookmark to the button.
  3. Enable Data and Current page, enable Display, select All visuals, and assign the bookmark to the button.
  4. Enable Data, disable Display and Current page, select All visuals, and assign the bookmark to the button. (correct answer)
Explanation: When building a Reset this page button in Power BI, you need to think carefully about what each bookmark setting actually controls: Data captures slicer/filter states, Display captures visual visibility (show/hide), and Current page determines whether clicking the bookmark navigates to a specific page. For a reset button, you want to restore slicer and filter defaults — so Data must be enabled. You do not want to restore visibility states of pop-up panels, so Display must be disabled. You also do not want the button to navigate anywhere, so Current page must be disabled. Finally, selecting All visuals ensures every slicer and filter on the page is captured in that reset state. That's exactly what D describes, making it the correct configuration. A is wrong because it selects "only the page background" instead of All visuals — this means the bookmark won't capture any slicer or filter states, defeating the entire purpose of a reset button. B is wrong on two counts: it disables Data (so no slicer/filter states are captured at all) and enables Current page (which would cause unwanted page navigation), directly violating the requirements. C is wrong because it enables both Display and Current page. Enabling Display means the bookmark will restore visibility states of pop-up panels — explicitly prohibited by the scenario — and enabling Current page introduces page navigation behavior the author wants to avoid. A useful memory rule: Data = filters/slicers, Display = show/hide states, Current page = navigation. Match each requirement to its setting before evaluating answer choices, and the correct combination becomes obvious.

Question 9

A page has Region, Product, and Discount Parameter slicers. A Reset categories button must restore only Region and Product to their authored defaults. The user's current Discount Parameter selection must remain unchanged, and the button must not alter visual visibility.

How should you create the bookmark used by the button?

  1. Select all three slicers, choose All visuals, enable Data, disable Display, and save every default selection in the bookmark.
  2. Select Region and Product, choose Selected visuals, enable Data, disable Display, and save their default selections in the bookmark. (correct answer)
  3. Select Region and Product, choose Selected visuals, disable Data, enable Display, and save their default selections in the bookmark.
  4. Select the Discount Parameter slicer, choose Selected visuals, enable Data, disable Display, and save its current selection in the bookmark.
Explanation: When working with bookmarks in Power BI, the key distinction is between scope (which visuals the bookmark affects) and properties (what aspects of those visuals get captured). Every bookmark can target either all visuals or only selected ones, and independently control whether it captures Data (filter/slicer states) and Display (visibility). Mastering this matrix is essential for building precise reset buttons. The scenario requires resetting only Region and Product slicers without touching the Discount Parameter or hiding/showing anything. That points directly to B: you select just the Region and Product slicers, choose Selected visuals so the bookmark ignores everything else on the page, enable Data so their default filter states are captured, and disable Display so visibility remains untouched. When the button triggers this bookmark, only those two slicers reset — exactly what the requirement describes. A fails because choosing All visuals means the bookmark captures the Discount Parameter slicer too, which would override the user's current selection when triggered — violating the requirement to leave it unchanged. C disables Data and enables Display, which is backwards. Disabling Data means no slicer states are captured or restored, so the reset does nothing functionally. Enabling Display means the bookmark could alter visual visibility, which the requirement explicitly forbids. D targets the Discount Parameter slicer instead of Region and Product, which is the opposite of the goal. This would freeze or reset the one slicer that should be left alone. A useful rule of thumb: Selected visuals + Data ON + Display OFF is the standard recipe for a "reset specific slicers" button that leaves everything else untouched.

Question 10

A bookmark named Scene 2 was created while a chart was visible and a narrative text box was hidden. The author later changes the page so the chart is hidden and the text box is visible. Selecting Scene 2 still restores the original visibility arrangement.

What should the author do to make Scene 2 restore the new arrangement?

  1. Set the page to the desired arrangement, select Scene 2 in the Bookmarks pane, and choose Update. (correct answer)
  2. Rename Scene 2 after changing the arrangement so Power BI refreshes the bookmark's captured state.
  3. Move Scene 2 to a different bookmark group so the group recalculates the bookmark's visibility state.
  4. Change the button action from Bookmark to Page navigation so it reads the current visibility arrangement.
Explanation: When working with bookmarks in Power BI, it helps to think of each bookmark as a snapshot — it captures the exact state of your report page (filters, visuals, visibility) at the moment it was created. The key insight is that bookmarks don't dynamically track your page; they freeze a moment in time. To change what a bookmark remembers, you have to explicitly tell Power BI to retake that snapshot. That's exactly what Update does. Option A is correct: you first arrange the page into the desired state (chart hidden, text box visible), then select Scene 2 in the Bookmarks pane, and click Update. Power BI overwrites the old snapshot with the new one, so selecting Scene 2 now restores the new arrangement. It's a deliberate, manual process — nothing in Power BI automatically refreshes a bookmark when you change your page layout. Option B is wrong because renaming a bookmark only changes its label — Power BI does not re-capture any page state when you rename. The stored snapshot remains completely unchanged. Option C is wrong because bookmark groups are just organizational folders; moving a bookmark between groups has no effect on what state the bookmark has recorded. Option D is wrong because switching from Bookmark to Page navigation changes the type of action entirely — Page navigation jumps to a different report page rather than restoring a visibility state, so it doesn't solve the problem at all. A good study tip: on the PL-300 exam, whenever you see a question about bookmarks behaving "stale" or not reflecting changes, the answer almost always involves the Update command — remember, bookmarks never self-update.