Microsoft Power BI Quiz: Building Common Visuals
10 questions · exam conditions
0:00
Building Common VisualsQuestion 1 of 10

A finance report must show actual and budget amounts by fiscal quarter. Users must be able to expand each department to view its accounts while retaining fiscal quarters as separate column headings.

Which visual and field configuration should you use?

Use a matrix with Department and Account in Rows, Fiscal Quarter in Columns, and Actual and Budget in Values.
Use a table with Department, Account, Fiscal Quarter, Actual, and Budget as columns, and enable word wrapping.
Use a clustered column chart with Fiscal Quarter on the axis, Department in the legend, and Actual and Budget in tooltips.
Use a matrix with Fiscal Quarter and Department in Rows, Account in Columns, and Actual and Budget in Values.
← Back to quizzes

Microsoft Power BI Quiz

Microsoft Power BI Quiz: Building Common Visuals

Practice Building Common Visuals 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 Building Common Visuals, 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 finance report must show actual and budget amounts by fiscal quarter. Users must be able to expand each department to view its accounts while retaining fiscal quarters as separate column headings.

Which visual and field configuration should you use?

  1. Use a matrix with Department and Account in Rows, Fiscal Quarter in Columns, and Actual and Budget in Values. (correct answer)
  2. Use a table with Department, Account, Fiscal Quarter, Actual, and Budget as columns, and enable word wrapping.
  3. Use a clustered column chart with Fiscal Quarter on the axis, Department in the legend, and Actual and Budget in tooltips.
  4. Use a matrix with Fiscal Quarter and Department in Rows, Account in Columns, and Actual and Budget in Values.
Explanation: When a report needs hierarchical row expansion and fixed column headings for time periods, the matrix visual in Power BI is your go-to tool. It supports row hierarchies (drill-down), column groupings, and multiple value fields simultaneously — exactly what this scenario demands. Option A is correct because placing Department and Account in Rows creates the expandable hierarchy users need: they start at the department level and drill into individual accounts. Putting Fiscal Quarter in Columns keeps each quarter as a distinct column heading, and placing Actual and Budget in Values displays both measures side-by-side within each quarter. This configuration satisfies every requirement in the passage. Option B fails because a flat table has no hierarchy or drill-down capability. Every combination of Department, Account, and Fiscal Quarter would appear as a separate row, making the report cluttered and impossible to "expand." Word wrapping doesn't solve a structural problem. Option D uses a matrix but misconfigures it by placing Fiscal Quarter and Department in Rows — this turns fiscal quarters into expandable row categories rather than column headings, directly contradicting the requirement that quarters remain as separate column headings. Option C uses a clustered column chart, which is a chart, not a table-style layout. Putting Actual and Budget in tooltips (rather than visible bars or values) hides critical data from view and provides no expandable department-to-account hierarchy at all. Study tip: On Power BI questions, if you see the words "expand," "hierarchy," and "column headings" together, a matrix with the hierarchy in Rows and the time dimension in Columns is almost always the answer.

Question 2

A dataset contains one row for each completed month through the current month and contains no future dates. Executives need a visual that prominently displays the current month's customer-retention rate, compares it with a target measure, and includes a small historical trend.

Which configuration should you use?

  1. Use a KPI with Retention Rate as Indicator, Month as Trend axis, and Retention Target as Target goals. (correct answer)
  2. Use a card with Retention Rate as the field, Month as a visual filter, and Retention Target as conditional formatting.
  3. Use a line chart with Month on the X-axis, Retention Rate on the Y-axis, and Retention Target only in Tooltips.
  4. Use a gauge with Retention Rate as Value, Retention Target as Maximum value, and Month as a slicer.
Explanation: When a question asks you to display a single prominent metric, compare it to a target, and show a historical trend in one visual, your instinct should immediately point to the KPI visual in Power BI — that's precisely what it was designed for. The KPI visual has three dedicated field wells that map perfectly to this scenario: Indicator (the current metric value), Trend axis (the time dimension that drives the sparkline), and Target goals (the benchmark for comparison). Answer A uses all three correctly — Retention Rate as the Indicator gives the prominent current value, Month as the Trend axis generates the small historical sparkline, and Retention Target as the Target goals enables the built-in above/below comparison styling. This is a textbook KPI use case. Answer B falls short because a card visual displays only a single number with no built-in trend or target comparison — conditional formatting is not a substitute for a target benchmark displayed alongside the metric. Answer C uses a line chart, which shows trend history well but buries the current value and provides no meaningful target comparison; placing the target only in Tooltips makes it far from "prominent." Answer D misuses the gauge visual — a gauge shows progress toward a maximum value but has no trend/sparkline capability at all, and using Month as a slicer just filters the data rather than displaying history. Study tip: Memorize the three field wells of the KPI visual — Indicator, Trend axis, and Target goals — and recognize that any question combining "current value + target + trend" is almost always pointing to a KPI visual on the Power BI exam.

Question 3

A fact table has no rows for months in which no support tickets were opened. A related calendar table contains every month. The report must show a 24-month line in which months without tickets appear as zero rather than disappearing or being connected across.

Which approach should you use to build the visual?

  1. Use the fact-table ticket date on a categorical X-axis, enable Show items with no data, and set the line interpolation to stepped.
  2. Use the fact-table ticket date on a continuous X-axis, enable data labels, and replace null ticket dates in Power Query.
  3. Use Calendar Month Name on a continuous X-axis, disable Show items with no data, and plot the implicit count of Ticket ID.
  4. Use Calendar MonthStart on a categorical X-axis, enable Show items with no data, and plot a measure that returns zero for blank counts. (correct answer)
Explanation: When building a time-series line chart that must display every month — including months with no data — you need to think carefully about two independent decisions: the X-axis type and the data source driving it. The calendar table is your anchor here. Because the fact table has gaps, driving the X-axis from the fact table will always produce holes, regardless of other settings. Using Calendar MonthStart (a date field from the complete calendar table) on a categorical X-axis forces Power BI to render one slot per month, in order, with no skipping. Enabling Show items with no data then ensures months with zero tickets still appear as categories. Finally, plotting a measure — rather than an implicit count — lets you use COALESCE or + 0 logic to return zero instead of BLANK, which is what closes the visual gap and plots a flat zero rather than an interrupted line. That's exactly what D does, making it correct. A fails because the X-axis is driven by the fact-table ticket date — months with no tickets simply don't exist in that column, so "Show items with no data" has nothing to show. Stepped interpolation doesn't solve missing categories. B uses a continuous X-axis, which interpolates between existing points rather than placing a true zero at each absent month. Replacing null dates in Power Query doesn't create new month rows either. C uses Month Name (text) on a continuous axis, which Power BI doesn't support meaningfully — text fields can't be continuous. Disabling "Show items with no data" would actively remove empty months. Study tip: Remember the pairing — calendar table for the axis + categorical type + measure returning zero. Any break in that trio reintroduces gaps.

Question 4

An InventorySnapshot table stores the ending inventory balance for every warehouse on every day. A report page is filtered to one warehouse and must display only that warehouse's balance on the most recent date in the current filter context. No trend or target is required.

Which implementation is most appropriate?

  1. Create an average daily inventory measure and display that measure in a KPI visual.
  2. Add the Inventory Balance column to a card and retain its default Sum aggregation.
  3. Create a latest-visible-date inventory measure and display that measure in a card visual. (correct answer)
  4. Add Date and Inventory Balance to a table, sort Date descending, and show all rows.
Explanation: When a report needs to surface a single, current value — not a sum, average, or trend — your tool of choice is a well-crafted DAX measure displayed in a card visual. The key design challenge here is isolating the inventory balance for the most recent date available in the current filter context (the selected warehouse), which requires custom DAX logic, not a default column aggregation. Option C is correct because a measure like CALCULATE([Inventory Balance], LASTDATE('InventorySnapshot'[Date])) dynamically finds the latest date visible after all slicers and filters are applied, then returns only that balance. Wrapping it in a card visual gives you a clean, single-number display — exactly what the requirement describes. Option A fails on two counts: the KPI visual is designed for goal-vs-actual comparisons with trend lines, which the scenario explicitly says aren't needed. Additionally, averaging daily balances would produce a meaningless blend of historical figures, not the current snapshot. Option B is tempting but dangerous. Dropping a raw column into a card with Sum aggregation adds all inventory balances across every date in the filter context — not just the most recent one. You'd get a wildly inflated number. Option D technically surfaces the correct row, but showing a full sorted table forces the user to read the first row manually. It's not a single-value display, it's noisy, and it doesn't scale cleanly with dynamic filters. Study tip: On Power BI exam questions, whenever you see "most recent," "latest," or "current value," think DAX time intelligence (like LASTDATE or MAXX) paired with a card visual — not raw column aggregations.

Question 5

For a single calendar year, a line chart uses the text column Month Name on its X-axis. Power BI displays the months alphabetically. The model also contains Month Number, with January equal to 1 and December equal to 12.

What should you do while retaining the month names as the displayed labels?

  1. Place Month Number before Month Name on the X-axis, then sort the visual by the plotted measure in ascending order.
  2. Set Month Name to Sort by column using Month Number, then sort the visual by Month Name in ascending order. (correct answer)
  3. Change the X-axis to continuous while keeping only the text-based Month Name column on that axis.
  4. Sort the visual by Month Number descending, then reverse the line chart's Y-axis display direction.
Explanation: When Power BI displays a text column on a chart axis, it sorts alphabetically by default — which turns your calendar months into "April, August, December..." chaos. The fix requires teaching Power BI the intended sort order without sacrificing your readable month name labels. This is exactly what the Sort by Column feature is designed for. Option B is the correct approach. By navigating to the Month Name column in your data model and setting its "Sort by Column" property to Month Number, you establish a hidden numeric backbone that Power BI uses for ordering. When you then sort the visual by Month Name ascending, it sorts by Month Number under the hood, producing January through December in the correct sequence — while the axis still displays the friendly text labels your audience expects. Option A is tempting but wrong: placing Month Number on the axis before Month Name would cause the numeric values to appear as visible labels, breaking the requirement to retain month names as the displayed text. You'd also be sorting by the plotted measure, not by chronological order. Option C won't work because switching the axis to "continuous" requires a numeric or date data type. A text-based column like Month Name cannot be rendered on a continuous axis — Power BI simply won't allow it. Option D is a trap built on misunderstanding. Sorting by Month Number descending gives you reverse chronological order (December to January), and reversing the Y-axis flips values up/down — neither action produces a correctly ordered January-to-December display. Study tip: Whenever a text column needs custom sort order in Power BI, your first instinct should be "Sort by Column." It's one of the most commonly tested modeling concepts on this exam.

Question 6

Auditors need a visual containing one row for every invoice, with Invoice ID, invoice timestamp, customer, and amount. Invoice ID is unique and stored as text. They do not need subtotals, drill controls, or pivoted columns.

Which visual configuration most directly meets the requirement?

  1. Use a matrix with Customer in Rows, invoice timestamp in Columns, and Invoice ID and amount in Values.
  2. Use a table containing Invoice ID, invoice timestamp, customer, and amount, and sort it by invoice timestamp. (correct answer)
  3. Use a card containing Invoice ID and amount, and control the displayed invoice with a timestamp slicer.
  4. Use a table containing only customer and amount, then place Invoice ID and timestamp in Tooltips.
Explanation: When auditors need a flat, row-level view of transactional data — every invoice visible, no aggregation, no pivoting — your go-to visual in Power BI is the table. The table visual displays individual rows exactly as they exist in the data, making it ideal for detailed audit trails. Option B is the correct configuration because a table with Invoice ID, invoice timestamp, customer, and amount gives auditors precisely what they asked for: one row per invoice, all four required fields visible, sortable by timestamp. Since Invoice ID is unique text, it won't aggregate or collapse rows, preserving the one-row-per-invoice requirement perfectly. Option A fails because a matrix is designed for cross-tabulation — it pivots data into a grid with row and column headers, creating subtotals and drill paths. The auditors explicitly don't need pivoted columns or subtotals, so a matrix introduces unwanted complexity and restructures the data rather than displaying it flat. Option C is impractical for auditors who need to see all invoices simultaneously. A card shows a single aggregated value; pairing it with a slicer forces users to filter one invoice at a time, making it nearly impossible to review the full dataset efficiently. Option D hides critical information. Placing Invoice ID and timestamp in Tooltips means those fields only appear on hover — they're invisible in the default view. Auditors need all four fields always visible in the report itself, not buried in hover states. Study tip: On Power BI exam questions, match the visual type to the data shape the user needs — flat rows → table, cross-tab comparisons → matrix, single KPIs → card.

Question 7

A report must compare total quarterly revenue among four regions and also show how three product categories contribute to each region's total. All revenue values are nonnegative, and differences in absolute totals are important.

Which visual best satisfies both comparison requirements in a single visual?

  1. Use a line chart with Region on the X-axis, Product Category in the legend, and Revenue on the Y-axis.
  2. Use a 100% stacked column chart with Region on the axis, Product Category in the legend, and Revenue in Values.
  3. Use a clustered column chart with Product Category on the axis, Region in the legend, and Revenue in Values.
  4. Use a stacked column chart with Region on the axis, Product Category in the legend, and Revenue in Values. (correct answer)
Explanation: When a question asks you to satisfy two comparison goals at once — cross-group totals and within-group breakdowns — you need a visual that encodes both pieces of information simultaneously without sacrificing either. A stacked column chart does exactly this. Each column's total height represents the region's overall revenue, letting you compare absolute totals across the four regions at a glance. Meanwhile, each column is divided into colored segments representing the three product categories, revealing each category's contribution to that region's total. This is why D is the correct answer: Region on the axis drives the cross-region comparison, and Product Category in the legend drives the composition breakdown — both requirements fulfilled in one visual. Option B, the 100% stacked column chart, destroys the absolute-total comparison by normalizing every column to 100%. You can see proportions, but since every column reaches the same height, you lose the ability to compare which region has more total revenue — which the question explicitly requires. Option A, the line chart, is designed for trends over continuous time. Connecting discrete regional categories with a line implies a relationship between adjacent points that doesn't exist here, and it doesn't naturally show part-to-whole composition. Option C flips the axis and legend assignments. Putting Product Category on the axis groups bars by category rather than by region, so comparing one region's total across all four regions becomes visually fragmented and unintuitive. Study tip: On Power BI exam questions, whenever you see two requirements — compare group totals and show category breakdown — stacked column chart is almost always the answer. 100% stacked is the classic distractor when absolute values matter.

Question 8

A sales model contains Product, Revenue, Gross Margin Percentage, and Units Sold. You need a scatter chart with one bubble per product. The horizontal position must represent revenue, the vertical position must represent gross margin percentage, and bubble size must represent units sold.

Which field assignment meets the requirement?

  1. Place Revenue on the X-axis, Gross Margin Percentage on the Y-axis, Product in Legend, and Units Sold in Size. (correct answer)
  2. Place Product on the X-axis, Gross Margin Percentage on the Y-axis, Revenue in Size, and Units Sold in Tooltips.
  3. Place Revenue on the X-axis, Gross Margin Percentage on the Y-axis, Units Sold in Legend, and Product in Tooltips.
  4. Place Revenue on the X-axis, Units Sold on the Y-axis, Product in Legend, and Gross Margin Percentage in Size.
Explanation: When configuring a scatter chart in Power BI, think of it as a coordinate system where each visual property maps to a specific field well: X-axis controls horizontal position, Y-axis controls vertical position, Details (or Legend) determines how data points are grouped into individual bubbles, and Size controls bubble diameter. The question gives you four explicit requirements: one bubble per product, revenue on the horizontal axis, gross margin percentage on the vertical axis, and units sold driving bubble size. Answer A satisfies all four — Revenue on X-axis sets horizontal position, Gross Margin Percentage on Y-axis sets vertical position, Product in Legend creates one distinct bubble per product, and Units Sold in Size scales each bubble appropriately. Every requirement maps cleanly to the correct field well. B fails immediately because it places Product on the X-axis, making product the horizontal dimension rather than revenue — and Revenue gets demoted to Size, violating two requirements at once. C almost looks correct at first glance (Revenue on X, Gross Margin on Y), but it puts Units Sold in Legend instead of Size. Legend creates separate data series or colors — it doesn't control bubble size, so the visual wouldn't communicate units sold through bubble area. D swaps Gross Margin Percentage and Units Sold entirely, putting Units Sold on the Y-axis and Gross Margin Percentage in Size, which reverses both of those requirements. A useful strategy: when a question describes a scatter chart, mentally check each visual property (X, Y, Size, Detail/Legend) against each stated requirement one by one. Distractors on this exam frequently swap two fields, betting you'll only skim the answer rather than verify every mapping.

Question 9

A service manager wants to show monthly ticket volume divided among Email, Phone, and Chat. The manager wants the viewer to see changes in the overall workload and the contribution of each channel over time. Ticket counts cannot be negative.

Which visual is the best fit?

  1. Use an unstacked area chart with Month on the X-axis, Ticket Count in Values, and Channel in the legend.
  2. Use a 100% stacked area chart with Month on the X-axis, Ticket Count in Values, and Channel in the legend.
  3. Use a stacked area chart with Month on the X-axis, Ticket Count in Values, and Channel in the legend. (correct answer)
  4. Use a scatter chart with Month on the X-axis, Ticket Count on the Y-axis, and Channel in the legend.
Explanation: When choosing a chart for time-series data that shows both a total trend and part-to-whole breakdown, ask yourself two questions: Do I need to see how the total changes over time? Do I need to see how each segment contributes to that total? If both answers are yes, a stacked area chart is your tool. A stacked area chart layers each category on top of the previous one, so the top edge of the entire chart represents the combined total ticket volume each month. At the same time, the thickness of each colored band shows that channel's individual contribution. This is exactly what the service manager needs — visibility into overall workload growth or decline, plus each channel's share. That makes C the correct answer. A is tempting but wrong. An unstacked area chart plots each channel independently from the zero baseline, so bands overlap rather than stack. You can see individual channel trends, but the "total" is not visually represented — and overlapping areas create ambiguity, especially with three series. B sounds close, but a 100% stacked area chart normalizes every month to 100%, destroying absolute volume information entirely. You can see proportional share shifts, but you lose all visibility into whether the overall workload grew or shrank — which is a stated requirement. D, the scatter chart, is designed to show correlations between two continuous numeric variables. Using Month (a time dimension) on the X-axis with channel in the legend produces a disconnected point plot with no sense of cumulative volume or trend continuity. A useful rule of thumb: if the question mentions "changes over time and contribution," default to a stacked area chart before considering 100% stacked or unstacked variants.

Question 10

A report must rank 18 clinical test types by total processing time. Several test names are long, users need to read the labels without rotating them, and the highest total must appear first.

Which visual design should you choose?

  1. Use a clustered bar chart with Test Type on the Y-axis, Processing Time on the X-axis, sorted descending by Processing Time. (correct answer)
  2. Use a clustered column chart with Test Type on the X-axis, Processing Time on the Y-axis, sorted alphabetically by Test Type.
  3. Use a line chart with Test Type on the X-axis, Processing Time on the Y-axis, sorted descending by Processing Time.
  4. Use a stacked bar chart with Processing Time on the Y-axis, Test Type in the legend, sorted descending by Test Type.
Explanation: When choosing a chart for ranked categorical data in Power BI, ask yourself three questions: How many categories are there? Are the labels long? Does sort order matter? Your answers drive the visual choice. With 18 test types and long names, a bar chart (horizontal bars) is your best friend. It places category labels on the Y-axis, giving each label generous horizontal space — no rotation required. Sorting descending by Processing Time ensures the highest total appears at the top, satisfying the requirement that "the highest total must appear first." That makes A the correct answer: a clustered bar chart with Test Type on the Y-axis, sorted descending by Processing Time. B fails on two counts. A column chart places Test Type on the X-axis, which forces long labels to rotate or overlap — exactly what the scenario prohibits. Alphabetical sorting also ignores the ranking requirement entirely. C uses a line chart, which implies continuity or trend over a sequence (like time). Clinical test types are discrete, unordered categories, so connecting them with a line is misleading and inappropriate. Line charts are for trends, not rankings. D describes a stacked bar chart with Test Type in the legend, which means all 18 test types would be stacked into a single bar — making individual comparison impossible. Sorting descending by Test Type is also alphabetical-ish, not by Processing Time, so it violates the ranking requirement. Study tip: On Power BI questions, match the axis to the label length — long labels belong on the Y-axis (bar chart), and sort order should always reflect the business requirement, not default alphabetical behavior.