PL-300 Key Performance Indicator (KPI) Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Focus on key performance indicators (KPIs) that align with business goals.

  Why this is correct

  A Power BI KPI visual compares a DAX measure against a defined goal (e.g., a target value in a separate measures table), giving executives an instant signal of whether strategic objectives are on track. Because every visual on an executive dashboard competes for attention, choosing only KPIs that tie directly to business goals ensures the dashboard drives decisions rather than merely displaying data. This avoids the trap of including vanity metrics that look interesting but are not actionable in the context of the company's strategy.

• ✓

  Use consistent colors and fonts to maintain a professional look.

  Why this is correct

  Applying a single Power BI theme (a JSON file) enforces consistent background, font, and data color palettes across every page and visual, which reduces cognitive load and makes the dashboard easier to scan. When color is used for conditional formatting, consistent semantics become critical: for example, green should always mean positive and red negative, so executives are not forced to re-learn the legend on each report. Brand-consistent styling also improves trust and perceived credibility in the data.

• ✓

  Provide high-level summaries with the ability to drill down if needed.

  Why this is correct

  An executive dashboard should start with top-level KPI cards and aggregated visuals (e.g., a column chart showing revenue by quarter) and use Power BI drill-down modes, expand/collapse buttons, or drill-through pages to reveal finer details such as region or product-level data. This layered approach supports the executive's need for a fast grasp of trend and variance while still enabling exploration of the cause behind an anomaly. Hierarchy in the data model or axis enables the transition from summary to detail without requiring a separate report page.

• ✗

  Include as many interactive slicers as possible for flexibility.

  Why it's wrong here

  Placing many slicers on a dashboard visually clutters the canvas and forces executives to override the preset context just to see the data, which slows decision-making and increases the risk of inconsistent cross-filtering across visuals. In Power BI, every slicer is an active filter on all other visuals on the page, so adding dozens of slicers not only consumes valuable space but also degrades performance because each slicer selection triggers a re-query of the data model. A better practice is to use a few high-value slicers (like date range and major segment) and rely on built-in drill-down or drill-through for less common filtering needs.

• ✗

  Use detailed tables to show all underlying data.

  Why it's wrong here

  A dense data table that lists every transaction forces executives to scroll through hundreds of rows to derive a pattern, which defeats the purpose of a dashboard—instant visual insight. In Power BI, table visuals do not aggregate by default and can render slowly when the underlying fact table has many rows, especially when combined with other visuals on the same page. If the stakeholder truly needs the raw detail, use a drill-through page from an aggregated visual or provide a report-level export to Excel instead of cluttering the dashboard with the entire dataset.

Go deeper

Related to this question