Microsoft Power BI Quiz: Drill Down And Drill Through
10 questions · exam conditions
0:00
Drill Down And Drill ThroughQuestion 1 of 10

A drill-through page can be opened from several summary pages. The report author adds a button labeled Back. Users expect the button to return them to whichever summary page initiated the drill-through, with that page's previous state preserved.

How should the button be configured?

Set the button action to Page navigation and choose the report's primary summary page as the destination.
Set the button action to Back so it returns through the user's drill-through navigation history.
Set the button action to Bookmark and capture the default state of every possible source page.
Set the button action to Drill through and select the current detail page as its destination.
← Back to quizzes

Microsoft Power BI Quiz

Microsoft Power BI Quiz: Drill Down And Drill Through

Practice Drill Down And Drill Through 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 Drill Down And Drill Through, 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 drill-through page can be opened from several summary pages. The report author adds a button labeled Back. Users expect the button to return them to whichever summary page initiated the drill-through, with that page's previous state preserved.

How should the button be configured?

  1. Set the button action to Page navigation and choose the report's primary summary page as the destination.
  2. Set the button action to Back so it returns through the user's drill-through navigation history. (correct answer)
  3. Set the button action to Bookmark and capture the default state of every possible source page.
  4. Set the button action to Drill through and select the current detail page as its destination.
Explanation: When you see a question about drill-through navigation in Power BI, focus on the user's journey — specifically, where they came from and how to return them there cleanly. Drill-through pages are designed to be reached from multiple source pages, so the return mechanism must be dynamic, not hardcoded. The Back button action is built precisely for this scenario. When configured with the Back action type, the button leverages Power BI's built-in navigation history, returning the user to whichever page triggered the drill-through — along with that page's prior filter and slicer state. This makes it universally correct regardless of which summary page the user originated from, which is exactly what the scenario requires. A is wrong because hardcoding a single summary page as the destination breaks the experience for users who drilled through from any other summary page. They'd land on the wrong page entirely — a classic trap when you try to manually replicate behavior that's already built in. C is wrong because bookmarks capture a static snapshot of a page's state at a specific moment. Managing a bookmark for every possible source page is impractical, fragile, and wouldn't dynamically reflect the user's actual prior state at drill-through time. D is wrong because setting the action to Drill through pointing at the current detail page creates a circular or redundant navigation — it doesn't return the user anywhere meaningful. As a study tip, remember: whenever a drill-through page must support multiple source pages with preserved state, the Back action is the only scalable solution. If the destination is fixed and known in advance, Page navigation makes sense — but not here.

Question 2

Users of a touch-oriented report should not need to open a right-click menu. After selecting one Customer row in a table, they must select a button to open a Customer Detail page filtered to that customer.

Which design meets the requirement with the least custom logic?

  1. Create a bookmark for each customer, and configure the button's action to select the corresponding bookmark dynamically.
  2. Add Customer as a synced slicer, and configure the button's action as Page navigation to Customer Detail.
  3. Add Customer to the target page's drill-through filters, and configure the button's action as Drill through to Customer Detail. (correct answer)
  4. Place Customer in the target page's tooltip fields, and configure the button's action as Web URL to Customer Detail.
Explanation: When a Power BI report needs row-level filtering triggered by a button tap — especially on touch devices — you should immediately think about drill-through, which is Power BI's built-in mechanism for navigating to a detail page pre-filtered to a specific context. Drill-through works by placing a field (like Customer) in the target page's drill-through filter well. Once configured, any button with its action set to "Drill through" automatically carries the selected row's context to that destination page — no custom measures, no DAX, no extra logic. The user selects a row in the table, taps the button, and lands on the Customer Detail page already filtered. That's exactly what option C describes, and it's the minimum-effort solution Power BI was designed to provide for this scenario. Option A is impractical at scale — creating a separate bookmark for every customer would be a maintenance nightmare and requires significant manual setup, the opposite of "least custom logic." Option B is tempting because synced slicers and page navigation are real features, but a synced slicer doesn't automatically reflect a table row selection without additional configuration (like a bridging slicer or interaction setup), adding complexity the question is asking you to avoid. Option D misuses the tooltip field well — it's meant for hover-over data summaries, not navigation filtering — and constructing a dynamic Web URL to simulate filtered navigation requires custom DAX expressions, which is far from minimal effort. The exam frequently tests whether you know which native Power BI feature handles a given UX pattern cleanly. Drill-through = row-context navigation to a detail page. Memorize that pairing.

Question 3

A published Sales Summary report must drill through to a Customer Detail page in a separate published report. Both reports are maintained in the same Power BI workspace, but they use independent semantic models.

Which set of actions is required to support cross-report drill-through?

  1. Use matching drill-through field names and data types, enable cross-report drill-through as required, and publish both reports to the same workspace. (correct answer)
  2. Use any fields connected by equivalent business logic, enable personal bookmarks, and publish the reports to separate workspaces.
  3. Create identical page names in both reports, enable synchronized slicers, and distribute both reports through the same organizational app.
  4. Combine both semantic models into one composite model, enable automatic page refresh, and use ordinary page navigation between reports.
Explanation: When you see a question about cross-report drill-through in Power BI, focus on three core requirements: field alignment, a specific setting that must be enabled, and workspace placement. Cross-report drill-through lets a report page in one report navigate to a detail page in a separate report, passing filter context along the way. For this to work, Power BI requires that the drill-through fields in both reports share the same name and compatible data types — this is how the platform maps the filter context from the source report to the destination page. You also must explicitly enable cross-report drill-through in the destination report's settings (under Options). Finally, both reports must live in the same workspace so Power BI can resolve the cross-report reference. Answer A correctly captures all three of these requirements. Answer B fails on multiple counts: fields don't just need to be "logically equivalent" — they need matching names and types. Personal bookmarks are unrelated to drill-through navigation, and publishing to separate workspaces breaks the cross-report link entirely. Answer C introduces synchronized slicers and identical page names, neither of which is a cross-report drill-through requirement. Synchronized slicers manage slicer state within a single report, not between reports. Page names in the destination report are referenced internally but don't need to match names in the source report. Answer D proposes merging the models into a composite model, which is one possible architecture but not a requirement for cross-report drill-through. Automatic page refresh and ordinary page navigation are entirely unrelated features. A reliable study tip: memorize the three pillars — matching field names/types, enable the setting, same workspace — as a checklist whenever cross-report drill-through appears on the exam.

Question 4

A Customer Detail page has Customer ID in its drill-through filters well. The page also has a fixed page-level filter of Customer Status = Active. A user drills through from an inactive customer, and every visual on the destination page is blank even though transactions exist for that customer.

What should you do to make the page display the selected customer's data regardless of status?

  1. Remove or revise the fixed Active page filter because it intersects with the incoming inactive Customer ID filter. (correct answer)
  2. Remove Customer ID from the drill-through filters well because page-level filters override all drill-through fields.
  3. Enable Keep all filters because this causes the incoming Customer ID to replace conflicting destination filters.
  4. Change the Back button to Page navigation because navigation history prevents inactive records from being evaluated.
Explanation: When troubleshooting blank visuals after a drill-through in Power BI, your first instinct should be to trace the filter chain: what filters exist on the destination page, and could any of them conflict with or restrict the incoming drill-through context? In this scenario, the Customer Detail page carries a fixed page-level filter of Customer Status = Active. When a user drills through on an inactive customer, Power BI passes that Customer ID into the drill-through filters well — but the page-level filter simultaneously demands Active status. These two filters combine with AND logic, meaning the visual asks for records where Customer ID matches and Status = Active. Since the target customer is inactive, zero rows satisfy both conditions, producing blank visuals. Removing or revising that fixed Active filter eliminates the conflict and lets the incoming Customer ID return results regardless of status — making A the correct fix. B is wrong because removing Customer ID from the drill-through well would break the drill-through mechanism entirely; drill-through fields are what carry context from the source page, not something that competes with page filters. C mischaracterizes how Keep all filters works — that setting preserves additional source-page filters when drilling through, it does not replace or override conflicting destination-page filters. D is a pure distractor; changing the Back button type affects navigation history only and has no bearing on how filters are evaluated. As a study tip, remember that page-level filters and drill-through filters stack — they don't replace each other. Whenever drill-through produces unexpected blanks, check whether the destination page has standing filters that could conflict with the incoming context.

Question 5

A sales model contains a marked Date table with the columns Calendar Year, Fiscal Year, Fiscal Quarter, Month Name, and Date. A report currently uses the automatically generated date hierarchy. Users must drill from Fiscal Year to Fiscal Quarter to Month Name, and the same drill path must be available in several visuals.

What should you do?

  1. Create a hierarchy in the Date table with Fiscal Year, Fiscal Quarter, and Month Name in that order, and use it in each visual. (correct answer)
  2. Add the three fiscal columns separately to each visual, and enable the drill-through option on every report page.
  3. Create a field parameter containing the three fiscal columns, and configure the parameter to permit drill-through navigation.
  4. Continue using the automatic date hierarchy, and change the model's regional settings to use the organization's fiscal calendar.
Explanation: When a question asks about enabling a consistent drill path across multiple visuals in Power BI, you should think about custom hierarchies — a core modeling feature that lets you define the exact order users navigate through data levels. In Power BI, you can right-click a table in the Fields pane and create a named hierarchy by dragging fields into a specific order. Once built, that hierarchy appears as a single reusable object you can drop into any visual. This is precisely what the scenario demands: a Fiscal Year → Fiscal Quarter → Month Name drill path available in several visuals. Answer A is correct because creating a hierarchy in the Date table accomplishes both goals — it enforces the exact drill order and lets you reuse it consistently without reconfiguring each visual individually. Answer B fails because adding three separate columns to a visual does not automatically create a drill hierarchy — Power BI treats them as independent fields unless grouped into a hierarchy. "Drill-through" is also a different feature (navigating to a detail page), not the same as drilling down within a visual. Answer C misuses field parameters, which are designed to let users dynamically swap measures or dimensions in a visual, not to define a fixed drill path. Answer D is incorrect because the automatic date hierarchy follows the calendar year structure Power BI generates internally; changing regional settings does not redefine that hierarchy to match a fiscal calendar, and you'd lose control over the exact field sequence. A handy rule: whenever a question mentions a reusable, fixed drill path across visuals, think custom hierarchy in the model — not drill-through pages, field parameters, or auto-generated hierarchies.

Question 6

A model contains Product[Category] and a disconnected Selector[Category]. Both columns display the same category names. A source visual uses Selector[Category], while a destination page uses Product[Category] in its drill-through filters well. The expected drill-through destination does not appear from the source visual.

What is the most appropriate correction?

  1. Create a measure that returns the selected category text and place that measure in the target page's drill-through well.
  2. Rename Selector[Category] to Category because matching displayed column names alone establish drill-through compatibility.
  3. Replace Selector[Category] in the source visual with Product[Category], or configure the target with the exact source field. (correct answer)
  4. Enable bidirectional filtering on an unrelated relationship so Power BI treats both category columns as the same field.
Explanation: Drill-through in Power BI works by matching the exact field placed in the destination page's drill-through well against the field used in the source visual. When you right-click a data point, Power BI checks whether the field driving that visual matches what the target page expects — it's a field-identity check, not a value-matching check. Here's why that matters: even if Selector[Category] and Product[Category] display identical category names, Power BI treats them as completely different fields because they come from different tables with no relationship connecting them. The drill-through engine sees a mismatch and simply hides the destination option — which is exactly the symptom described. The fix, as answer C states, is to either use Product[Category] in the source visual (so the field identity aligns with the drill-through well), or reconfigure the target page's drill-through well to accept Selector[Category]. Either approach creates the necessary field match. Answer A is tempting but wrong — measures cannot be placed in the drill-through well; only columns can serve as drill-through filters. Answer B reflects a common misconception: renaming columns so their display names match does nothing, because Power BI tracks field identity by table-and-column lineage, not display name. Answer D is a red herring; bidirectional filtering affects how filter context propagates across related tables, but these tables are explicitly disconnected, and no relationship trick makes two unrelated columns the same field. Your study tip: whenever you see drill-through issues on the exam, immediately ask yourself, "Do the source field and the drill-through well field share the same table-column identity?" If not, no amount of naming tricks or measures will fix it — you must align the actual fields.

Question 7

A summary page displays sales by Product Category. A detail page contains transaction rows and must be reachable by right-clicking a category. The detail page should show transactions only for the selected category.

How should you configure the detail page?

  1. Add Product Category to the tooltip fields well and enable drill-down mode on the transaction table.
  2. Add Transaction ID to the drill-through filters well and rely on the category relationship to infer individual transactions.
  3. Add Product Category as a report-level filter and configure a page-navigation button on the summary page.
  4. Add Product Category to the drill-through filters well on the detail page and ensure the source visual uses that model field. (correct answer)
Explanation: When a question describes navigating from a summary visual to a filtered detail page via right-click, you're being tested on Power BI's drill-through feature — not tooltips, not page navigation buttons, and not report-level filters. Drill-through works by designating a field in the drill-through filters well on the destination (detail) page. When a user right-clicks a data point on any source visual that uses that same field, Power BI automatically passes the selected value as a filter context to the detail page. That's exactly what the scenario describes: right-clicking a category on the summary page to land on a transaction page scoped to that category. So D is correct — you place Product Category in the drill-through filters well on the detail page, and as long as the summary visual uses that same model field, the context transfer happens automatically. A is wrong because the tooltip fields well controls what appears in hover-over tooltips, not right-click navigation. Drill-down mode iterates through a hierarchy within the same visual — it doesn't route you to another page. B is a fabricated workflow; adding Transaction ID to the drill-through well would make right-click work on individual transaction rows, not categories, and there's no mechanism for Power BI to "infer" the category from a transaction ID field in the drill-through well. C describes manual page navigation with a button and a static report-level filter — that approach doesn't pass dynamic selection context from a visual; every user would see the same unfiltered (or identically filtered) page. As a study tip: whenever you see "right-click to navigate with context," think drill-through filters well on the destination page — that's the defining setup for this feature on the exam.

Question 8

A matrix has Region, Country, and Store in its Rows hierarchy. It initially displays one row for each Region. Users must expose countries while retaining the region groupings so that countries with identical names remain distinguishable.

Which command should users select?

  1. Go to the next level in the hierarchy, which replaces Region with Country for the matrix.
  2. Expand all down one level in the hierarchy, which displays Region and Country together. (correct answer)
  3. Turn on drill-down mode and select one Region, which displays countries for every region.
  4. Drill through to a detail page, which adds Country beneath each Region in the matrix.
Explanation: When working with matrix visuals in Power BI, hierarchy navigation is a critical skill. The key distinction to understand is the difference between replacing a level and expanding a level — these produce very different results, and exam questions frequently test whether you know which behavior each command produces. The requirement here has two conditions: expose countries AND retain region groupings so that same-named countries (like "Springfield" in different regions) remain distinguishable. Option B — Expand all down one level — satisfies both. It adds Country as a subordinate row beneath each Region, keeping the full context visible. Every country appears nested under its parent region, so identical country names are clearly differentiated by their regional group. Option A describes "Go to the next level," which replaces Region entirely with Country. You lose regional groupings, making identical country names indistinguishable — directly violating the requirement. Option C describes drill-down mode with a single region selected. This shows countries only for that one clicked region, hiding all other regions entirely. It doesn't expose countries across all regions simultaneously. Option D conflates "drill through" with hierarchy expansion. Drill through in Power BI navigates to a separate report page filtered by a data point — it's a cross-page feature completely unrelated to expanding rows within a matrix. Study tip: Memorize the three matrix hierarchy buttons as a set: Go to next level (replaces the current level), Expand all down one level (adds the next level beneath), and Drill down (shows the next level for one selected item only). Exam questions almost always hinge on the expand-vs-replace distinction.

Question 9

A source page is filtered to Fiscal Year 2026 and Online sales. A user drills through from the West Region data point to a regional detail page. Region is the only field in the destination page's drill-through filters well. The detail page must retain Fiscal Year, Channel, and Region when opened.

Which configuration should you use?

  1. Synchronize the source slicers to the destination page and replace the drill-through action with page navigation.
  2. Turn off Keep all filters so the destination automatically receives every source-page and visual filter.
  3. Add only Fiscal Year and Channel to the drill-through filters well and remove Region from that well.
  4. Turn on Keep all filters for the drill-through page so the source context accompanies the Region value. (correct answer)
Explanation: When you configure a drill-through in Power BI, you need to understand two distinct filter mechanisms: the drill-through filters well (which carries the specific field the user clicked) and the Keep all filters toggle (which determines whether the source page's broader filter context — slicers, visual filters, page filters — travels with the user to the destination). Questions like this test whether you can separate those two responsibilities. In this scenario, the destination page already has Region in its drill-through well, so the West Region value is passed automatically. The remaining challenge is preserving Fiscal Year 2026 and Online sales (Channel). Those values live on the source page as filters/slicers, not in the drill-through well. Turning on Keep all filters is precisely the toggle that carries that surrounding filter context to the destination — meaning all three filters (Fiscal Year, Channel, and Region) arrive intact. Option D is correct. Option A introduces page navigation, which bypasses drill-through entirely and loses the automatic passing of the clicked data point. Syncing slicers adds complexity and doesn't guarantee the Region value is passed correctly from the visual context. Option B is backwards — turning off Keep all filters does the opposite of what you want; it strips the source context from the drill-through, leaving only the field in the drill-through well. Option C misunderstands the well's purpose. Adding Fiscal Year and Channel to the drill-through well would require users to right-click those fields specifically, breaking the intended Region-based drill-through behavior. Study tip: Memorize this pairing — the drill-through well handles what field triggered the action, while Keep all filters handles everything else on the source page. They're complementary, not interchangeable.

Question 10

A column chart uses the hierarchy Country > State > City. It currently displays total sales by Country. A user selects the Go to the next level in the hierarchy command.

What will the chart display?

  1. States for every country, with the Country level removed from the displayed axis. (correct answer)
  2. States only for the country whose column was most recently selected by the user.
  3. Countries and their states together, preserving both levels on the displayed axis.
  4. Cities for every state because the command expands all remaining hierarchy levels.
Explanation: When working with hierarchies in Power BI visuals, you need to distinguish between two similar-sounding drilling commands: "Go to the next level" and "Expand all down one level." Confusing these two is the most common trap on hierarchy-related exam questions. "Go to the next level in the hierarchy" replaces the current level entirely with the next one. So when a chart is showing Countries and you trigger this command, it drops down to States — showing States for every country — and the Country level is no longer displayed on the axis. That's exactly what answer A describes, making it correct. Answer B describes the behavior of drill down (single-column drilling), where you click a specific column and Power BI filters deeper into that one item's children. This is a different interaction entirely — it requires selecting a specific data point first. Answer C describes the "Expand all down one level" command, which adds the next level beneath the current one, keeping both Country and State visible simultaneously on the axis. This is the key distinction: expand preserves the parent level, while "Go to the next level" replaces it. Answer D is a double misconception — it incorrectly skips a level (going straight to Cities) and conflates the behavior with an expand-all action. "Go to the next level" only moves down one level at a time. As a study tip, memorize this trio: Drill Down (one item's children), Go to Next Level (all items, replaces current level), and Expand Down (all items, adds to current level). Power BI exam questions frequently test exactly these distinctions.