Microsoft Power BI Quiz: Slicers

10 questions · exam conditions

0:00

SlicersQuestion 1 of 10

A report has Summary and Detail pages. A Region slicer appears on Summary. A different Region slicer appears on Detail. Selecting West on Summary must also filter Detail, but the Detail slicer must remain hidden so users cannot change the region from that page.

What should you configure?

Use Single select on both slicers, and disable interaction on the Detail page.

Use Edit interactions to filter Detail, and lock the Detail slicer in place.

Use a page-level Region filter on Summary, and hide the Detail slicer header.

Use Sync slicers to sync both pages, and clear Visible for the Detail page.

← Back to quizzes

Microsoft Power BI Quiz

Microsoft Power BI Quiz: Slicers

Practice Slicers 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 Slicers, 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

What should you configure?

Use Single select on both slicers, and disable interaction on the Detail page.
Use Edit interactions to filter Detail, and lock the Detail slicer in place.
Use a page-level Region filter on Summary, and hide the Detail slicer header.
Use Sync slicers to sync both pages, and clear Visible for the Detail page. (correct answer)

Explanation: When working with slicers across multiple pages in Power BI, the key concept to understand is the Sync Slicers pane, which gives you two independent controls for each slicer: whether it syncs (shares its selection with other pages) and whether it's visible on a given page. These two settings work independently, which is exactly what makes this scenario solvable. The correct approach, answer D, uses Sync Slicers to connect both Region slicers so that selecting "West" on Summary automatically filters Detail. Crucially, you then uncheck Visible for the Detail slicer — this hides it from users on that page while keeping the sync active. The filter still applies; users just can't see or interact with the slicer directly. Answer A fails because "disable interaction" controls how visuals respond to each other on the same page — it doesn't create cross-page filtering at all. You'd still have two isolated slicers. Answer B misunderstands Edit Interactions, which also only governs within-page visual relationships. "Locking" a slicer in place refers to its position during editing, not hiding it from end users or syncing it cross-page. Answer C confuses page-level filters with slicer behavior. A page-level filter on Summary doesn't propagate to Detail, and hiding a slicer header only removes the title label — the slicer control itself remains visible and interactive. For your study strategy, remember the Sync Slicers pane has two checkboxes per page: sync (shares the value) and visible (shows the slicer UI). You can sync without showing — that combination is a favorite exam scenario.

Question 2

On one report page, a Laboratory slicer should filter a results matrix and a sample-count card. A compliance card must always show the organization-wide value, regardless of the laboratory selection. Other page filters must continue to affect the compliance card.

Which action should you take?

Use Edit interactions and set the slicer's effect on the compliance card to None. (correct answer)
Turn Single select on and select every laboratory individually.
Remove the Laboratory field from the model relationship used by the matrix.
Hide the slicer and enable Select all before publishing the report.

Explanation: When you need a visual to ignore a specific slicer while still responding to other filters, you're working in the domain of interaction editing in Power BI. The key insight is that slicers, by default, cross-filter every compatible visual on the page — but you can override that behavior visual-by-visual. Selecting the slicer and opening Format > Edit interactions reveals interaction buttons above each visual: filter, highlight, or none. Setting the compliance card to None means the Laboratory slicer won't touch it, yet page-level filters (date ranges, status filters, etc.) still apply normally because those aren't slicer interactions — they're filter pane rules. This is exactly what the scenario requires, making A the correct action. B is a trap. Even if you select every laboratory individually using single select, the compliance card still responds to whichever laboratory is currently selected — it never shows the true organization-wide value reliably. C would break the matrix's ability to slice by laboratory in the first place, since you'd be removing the very relationship the matrix depends on. That damages functionality rather than preserving it. D is irrelevant misdirection. Hiding a slicer and enabling "Select all" doesn't stop the slicer from filtering visuals — it just hides the control from users while all values remain selected by default. The compliance card would still be vulnerable to interaction changes. Study tip: On Power BI exam questions, whenever you see "this visual must ignore a specific slicer but still respond to other filters," think Edit interactions → None. It's a surgical tool that targets one slicer-to-visual relationship without affecting anything else.

Question 3

A page has Department, Assay Type, and Fiscal Period slicers. Users need a Reset analysis button that restores only these three slicers to their published selections. The button must not change the page, visual visibility, spotlight state, or selections in other visuals.

Which implementation best satisfies the requirement?

Add a Clear all slicers button and configure each slicer for Single select.
Create a bookmark using All visuals, capture Display only, and assign it to the button.
Create a bookmark using Selected visuals for the three slicers, capture Data, and assign it to the button. (correct answer)
Add a page-navigation button and set the destination to the current report page.

Explanation: Bookmark behavior in Power BI is the core concept here. When you create a bookmark, you control two critical dimensions: scope (which visuals are included) and properties (what gets captured — Data, Display, or All). Getting these wrong produces a button that does too much or too little. The requirement is surgical: reset exactly three slicers, touch nothing else. Option C achieves this by using Selected visuals (targeting only the three slicers) and capturing only the Data property (which stores filter/selection state). When triggered, the bookmark restores those slicers to their saved selections while leaving every other visual's state — visibility, spotlight, cross-filter selections — completely untouched. That's a precise, scoped reset. Option A fails because "Clear all slicers" wipes every slicer on the page, not just the three specified ones, and Single select only constrains future user input — it doesn't restore a published default state. Option B is close but wrong in an important way: using All visuals means the bookmark captures the state of every visual on the page. Triggering it could inadvertently restore visibility states, spotlight settings, or selections in other visuals — violating the requirement to leave everything else unchanged. Option D navigates to the current page, which Power BI treats as a full page reload. This resets all visuals uniformly and doesn't provide the targeted, bookmark-controlled behavior the requirement demands. Your study tip: whenever a question asks for a targeted reset of specific visuals, think "Selected visuals + Data only." If a question asks for a full-page state snapshot, then All visuals + All properties is appropriate.

Question 4

A report author locks a Treatment slicer in the Selection pane so it cannot be accidentally moved during report development. After publication, consumers can still choose different treatments. The author expected locking to prevent this.

Which explanation and corrective action are most appropriate?

Locking affects only multi-select; enable Single select to prevent consumers from changing the value.
Locking prevents layout edits, not data selection; hide or remove the slicer if consumers must not change it. (correct answer)
Locking works only for dropdowns; convert the slicer to Dropdown and republish the report.
Locking requires Select all; enable that option and save the currently selected treatment.

Explanation: When working with Power BI's Selection pane, it's important to distinguish between two separate concepts: layout control and data interaction. The Selection pane offers two icons per visual — one for visibility (the eye icon) and one for locking position. Locking a visual anchors it so it cannot be accidentally repositioned or resized during report authoring. It has absolutely no effect on how report consumers interact with that visual's data after publication. This is exactly why B is correct. The slicer lock prevents layout edits in editing mode only. Once published, consumers interact with slicers normally — selecting, deselecting, and filtering as designed. If you need to prevent consumers from changing a filter value, the right approach is to hide or remove the slicer entirely, and instead apply a fixed filter through the Filters pane or report-level settings. The distractors each introduce plausible-sounding but fabricated behaviors. A incorrectly claims locking is tied to multi-select behavior — these features are completely unrelated. C invents a rule that locking only applies to dropdown-style slicers, which has no basis in Power BI's functionality; locking is visual-type agnostic. D suggests that enabling "Select all" somehow preserves a selection state through locking — this conflates slicer configuration options with the Selection pane's purpose, which is purely structural. A useful tip for this exam: whenever you see a question involving the Selection pane, mentally separate authoring-time behavior from consumer-time behavior. Power BI's authoring tools (lock, hide in Selection pane) almost never restrict what published consumers can do — that requires a different toolset entirely.

Question 5

A page contains Country and Site slicers. Selecting a country should filter all analytical visuals, but the Site slicer must continue displaying the complete enterprise-wide site list so users can compare availability across countries. The Country slicer currently reduces the Site slicer's values.

What should you configure without changing the semantic model?

Enable Select all on the Site slicer and select it before choosing a country.
Use Edit interactions and set the Country slicer's interaction with the Site slicer to None. (correct answer)
Turn Single select off for Country and turn Single select on for Site.
Sync the Country and Site slicers and hide the Site slicer on the page.

Explanation: When you need to control how one visual affects another in Power BI, the key tool is Edit Interactions, found on the Format ribbon when a visual is selected. This feature lets you specify, for each visual on the page, whether a selected slicer or visual should filter it, cross-highlight it, or have no effect on it at all — without touching the underlying semantic model. Setting the Country slicer's interaction with the Site slicer to None (option B) is exactly the right move here. When you select the Country slicer and open Edit Interactions, each other visual displays an interaction icon. Clicking the "none" icon (a circle with a line) on the Site slicer tells Power BI: "Country selections should leave this slicer untouched." All analytical visuals still respond to the Country slicer normally, while the Site slicer continues showing the full enterprise-wide list. Option A misunderstands how "Select All" works — it's a selection shortcut, not an interaction control, and it doesn't prevent the slicer's values from being filtered by another slicer. Option C confuses single-select/multi-select behavior, which controls how many items a user can pick, not whether cross-slicer filtering occurs. Option D involves the Sync Slicers pane, which manages whether a slicer appears or applies across multiple report pages — hiding a slicer doesn't preserve its full value list or solve the filtering problem. A useful study habit: whenever a Power BI question describes one visual unexpectedly affecting another, immediately think Edit Interactions — it's the go-to tool for fine-tuning visual-to-visual filtering behavior without modifying the data model.

Question 6

A Category slicer permits multiple selections. Users frequently select a subset and then need a clearly labeled item inside the slicer that restores an unrestricted category state. The report author does not want users to rely on the visual header's clear-selection icon.

Which configuration best meets the requirement?

Enable Show Select all option in the slicer's selection settings. (correct answer)
Enable Single select and rename the first category to All.
Enable Multi-select with CTRL and hide the slicer header.
Disable slicer interactions for every visual on the page.

Explanation: When a slicer question describes users needing a labeled item within the slicer itself to reset their selection, you should immediately think about built-in slicer settings rather than workarounds — Power BI has a native feature designed exactly for this. Enabling Show "Select all" option (choice A) adds a clearly labeled "Select all" item directly inside the slicer list. When users click it, every category becomes selected, effectively restoring the unrestricted state. It's visible, intuitive, and lives inside the slicer — exactly what the passage requires. This is the correct configuration. Choice B is a trap. Renaming a data value to "All" doesn't actually select all categories — it just creates a misleading label for one real category value. Users would think they're seeing everything, but the data would be filtered to only that renamed item. This is a data integrity problem masquerading as a UI solution. Choice C misreads the requirement entirely. Enabling multi-select with CTRL changes how users make selections, not how they reset them. Hiding the slicer header also removes the title, reducing clarity — the opposite of what's needed. Choice D disables interactions altogether, which means slicers won't filter visuals at all. This doesn't restore an "unrestricted" state in any meaningful way — it simply breaks the slicer's purpose. Study tip: On Power BI exam questions, when you see phrases like "labeled item inside the visual" or "users shouldn't rely on the header icon," look for native formatting/settings options first. Power BI's built-in slicer settings (Selection pane → Show "Select all") are frequently tested precisely because they solve UX problems cleanly without data manipulation.

Question 7

A long Facility slicer is changed from List style to Dropdown style to conserve report-canvas space. Before the change, users could select multiple facilities without holding Ctrl. The same interaction must remain available after the style change.

What additional selection-setting change is required solely because the slicer was changed to Dropdown style?

Multi-select with CTRL must be enabled because dropdowns always require Ctrl.
Single select must be enabled because dropdown slicers support only one value.
No change is required; the existing multi-selection settings can remain in effect. (correct answer)
Select all must be enabled because dropdowns otherwise clear prior selections.

Explanation: When working with Power BI slicers, it's important to understand that slicer style (List vs. Dropdown) and slicer selection behavior (single-select, multi-select, Select All) are completely independent settings. Changing the visual presentation of a slicer does not reset or alter its underlying selection configuration. Because these settings are independent, switching a slicer from List to Dropdown style preserves whatever multi-selection behavior was already configured. If users could previously select multiple items without holding Ctrl — meaning the "Single select" toggle was off — that same setting carries over automatically to the Dropdown style. No additional change is needed, which makes C the correct answer. A is wrong because it describes a behavior that doesn't exist in Power BI. Dropdown slicers do not inherently require Ctrl for multi-selection. The Ctrl requirement is controlled by the "Multi-select with CTRL" toggle, which applies equally to both List and Dropdown styles and is off by default. B is wrong because it states a false limitation. Dropdown slicers fully support multi-selection — users can check multiple items from the dropdown list just as they would in a List-style slicer, provided single-select mode is not enabled. D is wrong because changing the slicer style does not cause prior selections to clear automatically, nor does the Dropdown style have any special behavior that would require enabling "Select All" to preserve multi-selection capability. A good study tip: on Power BI exam questions, always distinguish between a slicer's visual format and its interaction settings — they operate on separate configuration layers and don't interfere with each other.

Question 8

A report contains a list slicer for Study Phase. Users must be able to select several phases by clicking each value. They should not have to hold Ctrl, and clicking an already selected value should remove that value from the selection.

Which slicer configuration should you use?

Turn Single select off and turn Multi-select with CTRL off. (correct answer)
Turn Single select off and turn Multi-select with CTRL on.
Turn Single select on and turn Multi-select with CTRL off.
Turn Single select on and enable the Select all option.

Explanation: When configuring a Power BI list slicer, you need to understand two independent settings: Single select and Multi-select with CTRL. Think of them as controlling how many items can be chosen and what action triggers multi-selection. The scenario requires three behaviors: multiple values can be selected, no Ctrl key is needed, and clicking a selected value deselects it. This points directly to Answer A — turning Single select off (enabling multi-selection) and turning Multi-select with CTRL off (so users click freely without holding Ctrl). With both settings off, clicking any value toggles it in or out of the selection, which is exactly the described behavior. Answer B fails because turning Multi-select with CTRL on forces users to hold Ctrl to add items to the selection — directly violating the requirement that they shouldn't need to. Answer C contradicts itself functionally: turning Single select on restricts the slicer to one value at a time, so turning Multi-select with CTRL off becomes irrelevant — you can never select multiple phases regardless. Answer D also keeps Single select on, which means only one study phase can be active at once. The "Select all" option lets users pick every value at once, but it doesn't solve the need to individually toggle multiple specific phases. A useful memory trick: "Single select on = exactly one choice." Whenever the requirement says users must pick several values, Single select must be off. Then ask whether Ctrl is required — if not, Multi-select with CTRL goes off too.

Question 9

A field parameter contains Revenue, Margin, and Units. The parameter is placed in a slicer and used by a chart. The chart must display exactly one of the three measures at a time. Currently, users can select Revenue and Margin together, causing both measures to appear.

What should you change while preserving the field parameter design?

Enable Single select for the field parameter slicer. (correct answer)
Enable Multi-select with CTRL for the field parameter slicer.
Enable Select all for the field parameter slicer.
Disable the slicer's interaction with the parameter chart.

Explanation: When working with field parameters in Power BI, think about slicer settings as your first tool for controlling user selection behavior — not the parameter itself or its underlying DAX. A field parameter slicer behaves like any other slicer, meaning by default it allows multi-selection. When users can pick both Revenue and Margin simultaneously, the chart renders both measures at once, breaking the "exactly one measure" requirement. The fix is straightforward: enabling Single select on the slicer (option A) forces users to choose only one field at a time, preserving the field parameter design entirely while enforcing the one-measure display rule. You do this in the slicer's Format pane under Slicer settings → Selection → Single select. Option B, enabling Multi-select with CTRL, makes the problem worse — it still permits multiple selections, just requiring the CTRL key. This doesn't restrict the user to one measure. Option C, Select all, would actually allow every measure to appear simultaneously, the opposite of what you want. Option D, disabling the slicer's interaction with the chart, would sever the connection entirely — the slicer would stop controlling the chart, so the chart couldn't switch measures at all, defeating the purpose of the field parameter. A useful study tip: on Power BI exam questions involving slicers, always separate what the slicer contains from how it behaves. Field parameters are often paired with slicer behavior questions, and the answer is almost always found in the slicer's Selection settings rather than in editing the parameter's DAX or visual interactions.

Question 10

A report uses two bookmarks named Clinical View and Financial View to change visual visibility. Users select several hospitals in a slicer, but moving between the bookmarks restores the hospital selection that existed when each bookmark was created. The bookmarks do not need to store any filter or slicer state.

How should you modify the bookmarks?

Enable Multi-select with CTRL on the slicer and update both bookmarks.
Turn off the Display property for both bookmarks and then update them.
Enable Single select on the hospital slicer and recreate both bookmarks.
Turn off the Data property for both bookmarks and then update them. (correct answer)

Explanation: When working with Power BI bookmarks, you need to understand that each bookmark can independently capture three types of state: Display (visual visibility), Data (filters, slicers, and cross-highlights), and Current Page. The key to this question is recognizing which property controls slicer selections. The scenario describes bookmarks that are resetting the hospital slicer to whatever state existed at creation time — a classic sign that the Data property is enabled. Since the bookmarks only need to toggle visual visibility, you should turn off the Data property for both bookmarks and then update them. With Data disabled, the bookmarks will no longer capture or restore any filter or slicer state, letting users freely change hospital selections without those choices being overridden when switching views. That makes D the correct answer. A is a trap — enabling multi-select on the slicer changes how users interact with it, but doesn't affect whether the bookmark restores a saved slicer state. The problem persists. B is wrong because the Display property controls whether visuals are shown or hidden, which is exactly what these bookmarks should be managing — turning it off would break their core purpose. C is a red herring; Single select is a slicer configuration option that limits the user to one choice at a time, but again has no bearing on how bookmarks capture and restore state. As a study tip, memorize the three bookmark properties — Data, Display, Current Page — and what each one controls. Exam questions often describe a symptom (like unwanted filter resets) and ask you to identify which property to toggle. Matching the symptom to the right property is the skill being tested.