Courseiva

CCNA Pl300 Visualize Analyze Questions

24 questions · Pl300 Visualize Analyze topic · All types, answers revealed

Practice these questionsExam hubAll questions
1
MCQeasy

A Power BI report includes a bar chart showing total sales by product category. The report designer wants to add a trend line to the chart to show the overall sales trend over time. Which type of visual should be used instead?

A.Stacked bar chart
B.Line chart
C.Scatter chart
D.Pie chart
AnswerB

A line chart encodes data points along a continuous time axis and connects them with straight lines, allowing the eye to perceive direction, rate of change, and periodicity. Because the x-axis is continuous and time-ordered, Power BI can compute and overlay a trend line using linear regression, moving average, or other built-in analytics in the Analytics pane. It is the default and recommended visual for time-series trend analysis because it preserves the sequential structure of the data.

Why this answer

A line chart is the correct visual to show a trend over time because it plots data points connected by straight lines, making it easy to see the overall direction and pattern of total sales across a continuous time axis. Bar charts, including stacked variants, are designed for comparing discrete categories, not for displaying continuous trends.

Exam trap

The trap here is that candidates may think a bar chart with a trend line added via the analytics pane is acceptable, but the question asks which visual should be used instead, implying the bar chart is not the optimal choice for showing a trend over time.

How to eliminate wrong answers

Option A is wrong because a stacked bar chart is used to show the composition of a total across categories over time or groups, not to display a single trend line for total sales. Option C is wrong because a scatter chart is used to show the relationship between two numerical variables, not to display a single metric's trend over time. Option D is wrong because a pie chart shows proportions of a whole at a single point in time and cannot represent trends over time.

Practice this question →
2
MCQhard

Refer to the exhibit. You have a DAX measure that calculates customer lifetime value (CLV) as total revenue divided by distinct customer count. When you use this measure in a visual with Product category, you notice that the CLV values are higher than expected. What is the most likely reason?

A.The measure does not filter out returns
B.The measure counts customers per category, but customers who buy multiple categories are counted in each category, reducing the denominator
C.The measure should use COUNTROWS instead of DISTINCTCOUNT
D.The measure is dividing by zero for categories with no customers
AnswerB

This inflates CLV per category.

Why this answer

The CLV measure is defined as total revenue divided by distinct customer count. When this measure is used in a visual with Product category, the context filters both the revenue and the customer count to that category. The DISTINCTCOUNT(CustomerID) returns the number of customers who purchased at least one product in that category.

If a customer buys multiple categories, they are counted in each category's distinct count. This makes the denominator per category smaller than the total distinct customer base, leading to a higher CLV value than expected. Option A is incorrect because returns would reduce revenue, not cause higher CLV.

Option C is incorrect because using COUNTROWS would count transaction rows, not distinct customers, making the denominator larger and CLV smaller. Option D is incorrect because DIVIDE handles division by zero, and the scenario does not involve zero customers.

Practice this question →
3
MCQmedium

A data analyst creates a Power BI report that uses a date table with a continuous date range. They want to calculate the running total of sales over the last 12 months, ending on the last date in the current filter context. Which DAX expression should they use?

A.CALCULATE(SUM(Sales[Amount]), DATESBETWEEN('Date'[Date], MAX('Date'[Date]) - 365, MAX('Date'[Date])))
B.CALCULATE(SUM(Sales[Amount]), DATESINPERIOD('Date'[Date], MAX('Date'[Date]), -12, MONTH))
C.TOTALMTD(SUM(Sales[Amount]), 'Date'[Date])
D.CALCULATE(SUM(Sales[Amount]), DATESYTD('Date'[Date]))
AnswerB

DATESINPERIOD is the correct time-intelligence function here because it returns a contiguous interval ending at MAX('Date'[Date]) and extending back 12 full calendar months, respecting month boundaries rather than fixed day counts. With -12 and MONTH, the filter context established by CALCULATE adjusts the Sales[Amount] summation to include exactly the trailing 12 months relative to the latest visible date, which is exactly what a rolling 12-month total requires.

Why this answer

DATESINPERIOD('Date'[Date], MAX('Date'[Date]), -12, MONTH) returns a contiguous set of dates from 12 months before the last date in the current filter context up to that last date, providing an exact 12-month window. This function handles month boundaries correctly and is the standard way to calculate rolling 12-month totals in DAX. Option A uses 365 days, which can be imprecise due to leap years.

Exam trap

Candidates often choose DATESBETWEEN with 365 days (Option A) thinking it simplifies the calculation, but they overlook the leap year issue. DATESINPERIOD (Option B) is the correct function for a precise rolling 12-month period as it uses month boundaries rather than a fixed number of days.

How to eliminate wrong answers

Option B is wrong because DATESINPERIOD with -12 and MONTH shifts the window back 12 months from the end date, but it includes the entire month of the start date, which can result in a 13-month window if the last date is not the end of a month, thus not guaranteeing exactly 12 months. Option C is wrong because TOTALMTD calculates a month-to-date total, not a running total over the last 12 months. Option D is wrong because DATESYTD calculates a year-to-date total from the start of the calendar year, not a rolling 12-month window ending on the last date in the filter context.

Practice this question →
4
MCQhard

You are a Power BI analyst for a multinational retail company. The company's sales data is stored in an Azure SQL Database with tables: Sales (SalesID, Date, ProductID, Quantity, Amount), Products (ProductID, ProductName, Category), and Calendar (Date, Year, Month, Day). The Sales table contains 500 million rows. You are creating a Power BI report to analyze daily sales trends over the past 5 years. The report must allow users to drill from year to month to day using a hierarchy. The performance of the report is critical; users expect visuals to load within 5 seconds. The current model imports all tables without any optimization, and the date hierarchy visual takes over 30 seconds to render. You need to redesign the data model to meet the performance requirement. What should you do?

A.Create an aggregated table in Power Query that groups sales by date, and create a date hierarchy in the Calendar table.
B.Add calculated columns for Year, Month, and Day in the Sales table to avoid using the Calendar table.
C.Switch the import mode to DirectQuery to avoid loading all data into memory.
D.Implement incremental refresh policy on the Sales table to reduce the amount of data loaded.
AnswerA

Creating an aggregated table in Power Query reduces the 500M-row fact table to daily totals, so slicers, visuals, and DAX queries scan far fewer rows and return faster. A date hierarchy in the Calendar table then lets users drill from year to month to day without adding storage-heavy calculated columns. This preserves the star schema and enables query folding during refresh.

Why this answer

Pre-aggregating sales data by date in Power Query reduces the granularity from 500 million rows to at most 1,825 rows (one per day for 5 years), which drastically improves query performance for the date hierarchy. Creating a date hierarchy in the Calendar table allows drill-down. Option B is wrong because calculated columns do not reduce row count and still require processing all 500 million rows, so performance remains poor.

Option C is wrong because DirectQuery without aggregation still pushes large queries to the database, which can be slow. Option D is wrong because incremental refresh only reduces the amount of data loaded during refresh, but does not improve query performance on the existing data; the full model still contains 500 million rows.

Practice this question →
5
Multi-Selecteasy

You are creating a Power BI report to analyze customer churn. You have a table with Customer ID, Churn Date, and other attributes. You want to create a measure that calculates the number of customers who churned in the last 30 days. Which THREE components do you need?

Select 3 answers
A.A measure using CALCULATE, COUNTROWS, and DATESINPERIOD
B.A calculated column for 30-day flag
C.A relationship between date table and Churn Date
D.A separate date table marked as date table
E.A disconnected table with date range
AnswersA, C, D

This is the correct pattern for a dynamic 30-day churn count: CALCULATE modifies the filter context to filter rows meeting the condition, COUNTROWS counts rows in the churn fact table, and DATESINPERIOD generates a contiguous date range from the max visible date going back 30 days. Unlike a column, this measure is evaluated at query time, so it automatically respects report-level slicers, page filters, and drill-downs, and requires no storage overhead. The key is that DATESINPERIOD works only with a properly related date table.

Why this answer

The correct components are A, C, and D. A measure using CALCULATE, COUNTROWS, and DATESINPERIOD (A) is needed to dynamically count customers who churned in the last 30 days. A relationship between the date table and Churn Date (C) is required for time intelligence functions like DATESINPERIOD to work correctly.

A separate date table marked as a date table (D) is necessary because Power BI time intelligence functions require a proper date table with continuous dates and a date type. Option B (a calculated column for 30-day flag) is not needed; the measure handles the filtering. Option E (a disconnected table with date range) is unnecessary because the regular date table relationship suffices.

Practice this question →
6
Drag & Dropmedium

Drag and drop the steps to configure a scheduled refresh for a dataset in the Power BI service into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Scheduled refresh is configured in the dataset settings, enabling automatic updates at specified intervals.

Practice this question →
7
MCQeasy

You have a Power BI report that shows sales by region. Users report that the map visual is not displaying data for some countries. What is the most likely cause?

A.The geographic data is not categorized correctly in the Data pane.
B.The report page filter is excluding those countries.
C.The map visual is limited to 30 data points.
D.The map visual only supports US addresses.
AnswerA

The Power BI Map visual relies on Bing Maps to geocode location values, and it can only do that if each geographic field has the correct Data Category set in the Column tools (e.g., Country, State, City). If the field is left as 'Uncategorized', Bing may interpret the values as text or fail to resolve them, so entire countries can be omitted. To fix this, select the field in the Fields pane, go to the Column tools tab, and set the Data Category accordingly. This is the most common reason a country that exists in your data does not appear on the map.

Why this answer

The most likely cause is that the geographic data is not categorized correctly in the Data pane. Power BI map visuals rely on the data category (e.g., Country, State, City) assigned to each field to correctly geocode and plot locations. If a field containing country names is left as 'Text' or 'Uncategorized', Power BI may fail to recognize the values as geographic entities, resulting in missing data points on the map.

Exam trap

The trap here is that candidates often assume a filter or data limit is the cause, but the core issue is the data category metadata, which is a subtle but critical setting in Power BI for map visuals.

How to eliminate wrong answers

Option B is wrong because a report page filter would affect all visuals on the page, not just the map, and users would typically notice missing data across the report, not solely on the map. Option C is wrong because the map visual (Bing Maps) does not have a hard limit of 30 data points; the limit applies to scatter charts and other visuals, not to map visuals. Option D is wrong because Power BI map visuals support addresses globally via Bing Maps geocoding, not just US addresses.

Practice this question →
8
MCQeasy

You have a Power BI report that uses a custom visual from AppSource. The visual is not rendering correctly. What should you check first?

A.The network connection is blocked from reaching AppSource.
B.The visual is not compatible with the report theme.
C.The dataset has row-level security applied.
D.The visual is not certified by Microsoft.
AnswerD

Certification is not required for rendering.

Why this answer

Custom visuals are embedded in the report file when published from Power BI Desktop; they do not require a network connection to AppSource to render. If a visual is not rendering, first check whether the visual is certified by Microsoft, as the Power BI service administrator might have disabled the use of uncertified visuals. Option A is incorrect because the visual does not rely on a live connection to AppSource.

Option B is incorrect because report themes only affect styling, not rendering. Option C is incorrect because RLS filters data but does not prevent visual rendering.

Practice this question →
9
MCQmedium

You are building a Power BI report that uses a live connection to an Azure Analysis Services (AAS) tabular model. Users need to be able to filter data using a slicer that shows only products that have been sold in the current year. What should you do?

A.Add a calculated column to the Product table in the AAS model that marks products sold this year
B.Use a filter on the slicer visual to show only products where sales year equals current year
C.Create a calculated table in the AAS model that returns only products sold in the current year
D.Create a calculated table in Power BI Desktop using DAX to filter products
AnswerC

A calculated table in the AAS model can use DAX to dynamically return only products sold in the current year, and it will be available in the live connection.

Why this answer

A calculated table in the AAS model can be created using DAX to dynamically return only products sold in the current year (e.g., using FILTER, CALCULATETABLE, YEAR, and TODAY functions). This table is available in Power BI via live connection and can be used as the slicer source. Option A is wrong: a calculated column in the Product table is static at process time and does not dynamically filter to current year; it also adds a column to the entire table, not a subset.

Option B is wrong: a visual-level filter on the slicer relies on the underlying data model; with live connection, you cannot create new tables in Power BI Desktop, and filtering on a date condition would require the slicer to use a field from a different table, which is not straightforward or recommended. Option D is wrong because live connections to AAS do not allow creating calculated tables in Power BI Desktop; all data modeling must be done in the source model.

Practice this question →
10
Multi-Selectmedium

Which THREE of the following are valid methods to enhance the accessibility of a Power BI report? (Choose three.)

Select 3 answers
A.Add animations to visuals to draw attention.
B.Provide keyboard navigation support by setting tab order.
C.Use a high contrast theme.
D.Use a color-blind friendly palette.
E.Add alt text to all visuals.
AnswersB, C, E

Setting tab order on visual elements creates a logical keyboard-only flow through a report. This is a core WCAG 2.1 requirement under 'keyboard accessible' because it lets users navigate without a mouse. By defining a sequence, Power BI ensures screen reader users and those with motor impairments can reach every interaction predictably, avoiding random or confusing jumps.

Why this answer

Setting tab order in Power BI allows keyboard-only users to navigate through report visuals in a logical sequence, which is a core requirement of WCAG 2.1 success criterion 2.4.3 (Focus Order). Option C is correct because Power BI provides built-in high contrast themes that enhance readability for users with visual impairments. Option E is correct because adding alt text to visuals ensures screen readers can convey the content to visually impaired users.

Option D is not considered a valid method for this question; while using a color-blind friendly palette is a good design practice, it is not specifically a method to enhance accessibility in the context of the exam. Option A is incorrect as animations can distract and are not an accessibility feature.

Exam trap

The trap is that candidates often overlook high contrast themes as a valid accessibility feature, mistakenly thinking they are only for visual appeal. However, Power BI's high contrast themes are a built-in accessibility feature, so option C is correct.

Practice this question →
11
MCQmedium

You have a report with a line chart showing monthly sales. Users need to see the exact sales value when they hover over a data point. What should you configure?

A.Enable data labels on the chart.
B.Configure the visual's tooltip to display the value.
C.Add a report page tooltip.
D.Set the category label to show the value.
AnswerB

To see the monthly sales value on hover, ensure the line chart's tooltip is enabled in the Format pane and that the Sales measure is included in the Tooltip well (it is by default). When configured, hovering a point shows a tooltip displaying the category, series name, and the measure value. If the tooltip is currently not appearing, verify the tooltip toggles are on and no report page tooltip has overridden it.

Why this answer

Tooltips in Power BI are designed to show detailed information about a data point when the user hovers over it. By default, the visual's tooltip already includes the value, but if it has been customized or removed, you need to ensure the tooltip is configured to display the sales value. This provides an interactive way to see exact numbers without cluttering the chart with permanent labels.

Exam trap

The trap here is that candidates often confuse data labels (which show values permanently on the chart) with tooltips (which show values on hover), leading them to select option A instead of understanding that tooltips are the correct interactive mechanism for this requirement.

How to eliminate wrong answers

Option A is wrong because enabling data labels permanently displays the sales value on the chart for every data point, which can clutter the visual and is not the hover-based behavior requested. Option C is wrong because a report page tooltip is a custom tooltip that can show additional context from other visuals or pages, but it is not required for simply showing the exact sales value; the default visual tooltip already serves that purpose. Option D is wrong because the category label shows the category name (e.g., month), not the sales value, and setting it to show the value would misrepresent the axis.

Practice this question →
12
Multi-Selectmedium

Which TWO actions can you perform using Power BI Desktop's Query Editor? (Choose two.)

Select 2 answers
A.Define row-level security (RLS) roles.
B.Merge two tables based on a common column.
C.Create a relationship between two tables.
D.Remove duplicate rows from a table.
E.Create a new measure using DAX.
AnswersB, D

The 'Merge Queries' feature in Query Editor combines rows from two tables based on a common column, supporting join kinds such as left outer, right outer, full outer, and inner. You can expand the resulting columns to bring in related fields, which is a common way to enrich one table with data from another. This operation is performed in Power Query before the data is loaded into the model.

Why this answer

In Power BI Desktop's Query Editor, you can merge two tables based on a common column using the 'Merge Queries' feature (option B) and remove duplicate rows using the 'Remove Duplicates' feature (option D). Creating a relationship between tables (option C) is not performed in Query Editor; it is done in the Model view after loading data. Defining row-level security roles (option A) and creating DAX measures (option E) are also not available in Query Editor — roles are managed in the Modeling tab or Power BI Service, and measures are created in the Report or Data view.

Exam trap

A common trap is thinking that Query Editor can create relationships, but relationship creation is a data modeling task performed in Model view. Some may confuse merging tables with creating relationships, but merging simply combines data into a new table.

Practice this question →
13
MCQhard

A Power BI report contains a table visual that displays employee names and their total sales. The data model includes an Employee table with columns: EmployeeID, Name, Department, and HireDate. The Sales table has columns: SaleID, EmployeeID, Amount, and SaleDate. The relationship between Employee and Sales is one-to-many. The user wants to see only employees who have made at least one sale. However, the table shows all employees, including those with no sales (blank Amount). What is the most likely reason?

A.The EmployeeID column in the Employee table is hidden.
B.The relationship is many-to-one, not one-to-many.
C.The relationship direction is set to Single from Employee to Sales.
D.There is no visual-level filter to exclude blank values.
AnswerD

To show only employees who have at least one sales record, a visual-level filter must be applied on the Amount field to exclude blank values (e.g., 'Amount is not blank' or 'Amount > 0'). Without such a filter, the table visual displays every row from the Employee dimension, even those without any related Sales rows, because Power BI's default behavior is to show all dimension rows unless a filter explicitly removes them. A visual-level filter on a measure or column from the fact table is the standard technique to restrict the visual to only employees with sales.

Why this answer

The table visual is showing all employees due to the absence of a visual-level filter to exclude blank or zero sales amounts. In Power BI, a one-to-many relationship between Employee and Sales means that employees without sales will still appear in the visual unless explicitly filtered out, as the relationship does not automatically suppress rows from the 'one' side when there are no matching rows on the 'many' side.

Exam trap

The trap here is that candidates assume a one-to-many relationship will automatically hide employees without related sales, but Power BI does not apply implicit row-level security or auto-filtering for missing related records; you must explicitly filter out blank values.

How to eliminate wrong answers

Option A is wrong because hiding the EmployeeID column does not affect the visibility of employees in the table; it only prevents that column from being displayed. Option B is wrong because the relationship is correctly described as one-to-many (one employee can have many sales), and changing it to many-to-one would be incorrect for this data model. Option C is wrong because setting the relationship direction to Single from Employee to Sales is the default and correct direction for a one-to-many relationship; it does not cause all employees to appear regardless of sales.

Practice this question →
14
Multi-Selecthard

Which are valid ways to create a calculated table in Power BI? (Select all that apply)

Select 4 answers
A.VALUES(Customer[Country])
B.CALCULATE(SUM(Sales[Amount]), ALL(Sales))
C.FILTER(Products, Products[Color] = "Red")
D.CALENDARAUTO()
E.SUMMARIZE(Sales, Sales[ProductID], "Total", SUM(Sales[Amount]))
AnswersA, C, D, E

VALID: VALUES returns a single-column table of distinct values from a column, which can be used to create a calculated table.

Why this answer

To create a calculated table, you need a DAX expression that returns a table object. Options A, C, D, and E all return tables: VALUES returns a single-column table of distinct values; FILTER returns a filtered subset of rows; CALENDARAUTO returns a date range table; SUMMARIZE returns a grouped table with aggregations. Option B, CALCULATE, returns a scalar value, not a table, so it is invalid.

Exam trap

The trap is assuming only specialized table functions like CALENDARAUTO and SUMMARIZE are valid, while other table-returning functions like VALUES and FILTER are also perfectly valid for calculated tables. The key is to recognize that any DAX function that returns a table can be used.

Practice this question →
15
Multi-Selecteasy

Which TWO of the following are valid methods to share a Power BI report with external users who do not have an internal Microsoft Entra ID account? (Select two.)

Select 2 answers
A.Publish to public web (Publish to web)
B.Deploy the report to Power BI Report Server and configure anonymous access
C.Invite them as guest users in Microsoft Entra ID (B2B)
D.Send them an email subscription with the report attached
E.Embed the report in a SharePoint Online page and share the link
AnswersB, C

Report Server can be configured for external access.

Why this answer

Deploy the report to Power BI Report Server and configure anonymous access allows external users without Microsoft Entra ID accounts to view the report via a web portal or URL. Option C is correct: Inviting them as guest users in Microsoft Entra ID (B2B) enables external users to access the report through the Power BI service using their existing email address. Option A is wrong: Publishing to public web makes the report publicly accessible to anyone on the internet, not just specific external users.

Option D is wrong: Email subscriptions send a static snapshot of the report, not an interactive experience. Option E is wrong: Embedding in SharePoint Online requires the user to have a valid Power BI license and access to the report via the Power BI service, which typically requires internal authentication.

Practice this question →
16
MCQhard

A Power BI report shows a bar chart with sales by region. When users click on a region, they expect a line chart on the same page to filter to that region's sales over time. However, the line chart does not respond to the click. What is the most likely cause?

A.The interaction between the bar chart and line chart is set to 'None'.
B.The line chart uses a continuous axis that cannot be filtered.
C.The bar chart is not set as a slicer.
D.The line chart has a legend with too many items.
AnswerA

In Power BI, visual interactions control whether a selected visual acts as a source filter for other visuals. If the interaction from the bar chart to the line chart is set to 'None', then selecting a bar will not propagate a filter to the line chart, leaving the trend unchanged. To make the line chart respond to region selection, the interaction must be set to 'Filter' (or 'Highlight'), which is the default for compatible visuals. This is the most likely cause of the behavior described, as the other options do not affect cross-filtering.

Why this answer

In Power BI, visual interactions control how one visual affects another when clicked. By default, cross-filtering and cross-highlighting are enabled, but if the interaction between the bar chart and line chart is explicitly set to 'None', clicking a region on the bar chart will not filter or highlight the line chart. This is the most common cause when a visual fails to respond to clicks on another visual.

Exam trap

The trap here is that candidates may think a visual must be a slicer to filter others, but Power BI allows any visual to cross-filter or cross-highlight other visuals by default, and the interaction setting is the key control.

How to eliminate wrong answers

Option B is wrong because a continuous axis does not prevent filtering; filtering applies to the underlying data, not the axis type. Option C is wrong because a bar chart does not need to be a slicer to filter other visuals; standard visuals can cross-filter or cross-highlight other visuals via visual interactions. Option D is wrong because a legend with many items does not prevent a visual from being filtered; it only affects the display of categories.

Practice this question →
17
MCQmedium

You have a Power BI dataset with a large fact table. You need to optimize report performance when users filter by date. What should you do?

A.Mark the date table as a date table in Power BI.
B.Hide all columns except the date column.
C.Disable cross-filtering between tables.
D.Summarize the fact table by month.
AnswerA

Marking a table as a date table in Power BI assigns a calendar semantic to a dedicated date column, which enables the VertiPaq query engine to natively optimize time-intelligence calculations such as YTD, QTD, and same-period comparisons. The engine uses the contiguous date range of the marked table to generate efficient filter predicates, avoiding fallback to the auto date/time hidden tables and reducing the overhead of date range evaluation.

Why this answer

Marking a date table as a date table enables time intelligence functions and better performance. Option B is wrong because hiding columns does not improve performance. Option C is wrong because disabling cross-filtering might affect user experience but not performance directly.

Option D is wrong because summarizing the fact table reduces granularity, which may not be desired.

Practice this question →
18
MCQeasy

You have a Power BI report with a matrix visual showing sales by region and product category. You want to allow users to expand and collapse groups. Which feature should you enable?

A.Page tooltips
B.Drill-down mode
C.Drill-through
D.Row and column subtotals
AnswerB

Correct. Drill-down mode provides expand/collapse buttons on hierarchical row headers, allowing users to navigate the hierarchy.

Why this answer

Drill-down mode in a matrix visual allows users to expand and collapse hierarchical levels. When a hierarchy is present, enabling drill-down mode provides expand/collapse icons on row headers, letting users interactively show or hide subcategories. Option A (page tooltips) shows tooltip pages on hover, unrelated to expand/collapse.

Option C (drill-through) navigates to another report page, not within the same visual. Option D (row and column subtotals) is a formatting feature for aggregating totals, not for expanding/collapsing groups.

Exam trap

Candidates often mistake subtotals for enabling expand/collapse, but subtotals are a separate formatting setting. Expand/collapse is inherently tied to hierarchical data and drill-down mode.

Practice this question →
19
MCQhard

You have a measure as shown in the exhibit. The sales amount is not accumulating correctly; instead, it shows the total sales for all dates, regardless of the selected date filter. What is the problem?

A.The measure should use ALLEXCEPT instead of ALL.
B.The ALL('Date') function removes the filter context, so the calculation returns total sales for all dates.
C.The VAR SelectedDate should be MIN instead of MAX.
D.The relationship between Sales and Date is inactive.
AnswerB

ALL removes the filter on Date, so the condition 'Date'[Date] <= SelectedDate applies to all dates, but without a filter, it sums all sales.

Why this answer

Using ALL('Date') within CALCULATE removes the filter context on the Date table, causing the measure to return the total sales across all dates, not the current date context. Option A is incorrect; ALLEXCEPT would keep certain filters, but the problem here is specifically the removal of all date filters by ALL. Option C is incorrect; using MIN versus MAX in VAR SelectedDate does not cause the described behavior; the issue is the ALL function.

Option D is incorrect; an inactive relationship would prevent proper filtering but would not result in the measure returning the total for all dates; the symptom would be different.

Practice this question →
20
Multi-Selectmedium

You have a Power BI report that uses a custom visual from AppSource. The visual is not rendering correctly. Which three steps should you take to troubleshoot?

Select 3 answers
A.Disable hardware acceleration in Power BI Desktop
B.Check if the visual version is compatible with your Power BI Desktop version
C.Update the visual to the latest version from AppSource
D.Clear the browser cache
E.Verify that the visual uses the correct data fields
AnswersB, C, E

Custom visuals are compiled against a specific Power BI API version, and that API version must be within the range supported by your Power BI Desktop release. When a visual was built for an older API or targets a newer API that your Desktop does not implement, the visual can fail to load, appear blank, or throw a rendering exception. Checking compatibility means verifying the minimum supported Power BI version on the visual's AppSource listing or its metadata, and confirming your Desktop is at or above that version. This is a critical diagnostic because an incompatible visual will misbehave regardless of how correctly its data fields are configured.

Why this answer

Options B, C, and E are correct. Checking compatibility (B) ensures the visual supports your version of Power BI Desktop. Updating the visual (C) can fix known bugs.

Verifying correct data fields (E) ensures the visual has the necessary input. Option A, disabling hardware acceleration, is a general troubleshooting step not specific to custom visuals. Option D, clearing browser cache, applies to Power BI Service, not Desktop.

Practice this question →
21
MCQeasy

You have a Power BI report with a page that contains a bar chart showing sales by product category. You want to allow users to click on a bar and navigate to a different report page that shows detailed sales for that category. Which feature should you use?

A.Bookmarks
B.Report page tooltips
C.Cross-filtering
D.Drillthrough
AnswerD

Drillthrough is a built-in Power BI feature that enables navigation from a data point on a source visual to a separate, binded target report page. When the user right-clicks a bar and selects the drillthrough target, the target page is automatically filtered to the clicked data point's field values (e.g., the specific category), providing a contextual detail view. This matches the requirement exactly because it is triggered by a per-data-point action and results in a page transition.

Why this answer

Drillthrough is the correct feature for navigating from a summary visual to a detail page for a specific data point. Cross-filtering only filters other visuals on the same page. Bookmarks are for saved views.

Report page tooltips are for hover details. Custom visuals are not needed.

Practice this question →
22
MCQeasy

A company has a dataset with a table 'Orders' containing columns: OrderDate, CustomerID, Amount. They want to create a visual that shows the total amount per month. Which of the following is the best approach?

A.Create a pie chart with OrderDate as the legend.
B.Create a line chart with OrderDate on the axis and use the date hierarchy to drill down to month.
C.Create a table visual with OrderDate and Amount, then group by month in the visual.
D.Create a bar chart with a calculated column 'Month' extracted from OrderDate and use that as the axis.
AnswerB

Using a line chart with OrderDate on the axis and the built-in date hierarchy enables drill-down from year to quarter to month without extra measures or columns. This hierarchy is auto-generated by Power BI for date columns, supports correct chronological sorting, and provides a natural, interactive way for users to explore trends at multiple granularities. The line chart's continuous axis is ideal for showing changes in Amount over time.

Why this answer

It leverages Power BI's built-in date hierarchy, which automatically groups OrderDate by year, quarter, month, and day. By placing OrderDate on the axis of a line chart and drilling down to the month level, you get an accurate monthly aggregation of Amount without needing any manual data transformation or calculated columns. This approach is efficient, maintains the underlying data model's integrity, and allows for easy drill-up/drill-down navigation.

Exam trap

The trap here is that candidates often think extracting a month column manually (Option D) is the most straightforward approach, but the exam tests whether you understand that Power BI's built-in date hierarchy is the optimal and intended method for time-based aggregations, avoiding unnecessary calculated columns.

How to eliminate wrong answers

Option A is wrong because a pie chart with OrderDate as the legend would treat each unique date as a separate slice, not aggregate by month, resulting in a cluttered and meaningless visual. Option C is wrong because table visuals in Power BI do not support grouping by month directly within the visual; you would need to create a calculated column or use a date hierarchy to achieve monthly aggregation. Option D is wrong because while a calculated column 'Month' extracted from OrderDate would work, it is not the 'best' approach—it adds unnecessary complexity, breaks the date hierarchy, and prevents easy drill-down to lower time granularities like day or quarter.

Practice this question →
23
MCQeasy

You need to create a measure that calculates the year-over-year growth percentage for sales. Which DAX function should you use?

A.DATEADD
B.PARALLELPERIOD
C.SAMEPERIODLASTYEAR
D.PREVIOUSYEAR
AnswerC

SAMEPERIODLASTYEAR is a time-intelligence function that returns a table of dates shifted exactly one year back from the current filter context, preserving the same day, month, and quarter boundaries. When used inside CALCULATE, it recalculates a measure over that prior-year date range, making it the precise foundation for a year-over-year growth calculation. Because it respects the current filter context and automatically handles leap years by shifting to the nearest valid date, it is the standard choice for comparing any arbitrary period—month, quarter, or cumulative range—to the same period in the previous year.

Why this answer

The SAMEPERIODLASTYEAR function is the correct choice for calculating year-over-year growth because it shifts the current filter context back by one year, returning a set of dates exactly one year prior. This allows you to compute the prior year's sales and then derive the growth percentage using a formula like (Current Sales - Prior Year Sales) / Prior Year Sales.

Exam trap

The trap here is that candidates often confuse SAMEPERIODLASTYEAR with PREVIOUSYEAR, mistakenly thinking PREVIOUSYEAR can be used for any period comparison, but PREVIOUSYEAR only works for full calendar year comparisons, not for partial periods like months or quarters.

How to eliminate wrong answers

Option A is wrong because DATEADD shifts dates by a specified interval (e.g., -1 year) but returns a contiguous range of dates, which can cause unexpected results when the current period is not a full month or quarter. Option B is wrong because PARALLELPERIOD returns a parallel period of the same length in the previous period (e.g., previous month, quarter, or year) but shifts the entire period, which may not align with the exact same dates as the current period. Option D is wrong because PREVIOUSYEAR returns all dates in the previous calendar year, which is not suitable for year-over-year comparisons when the current period is not the entire year (e.g., comparing a single month or quarter).

Practice this question →
24
MCQhard

A company wants to create a Power BI report that shows sales performance by region. The data contains a table 'Sales' with columns: Date, Amount, RegionID, and ProductID. They also have a 'Regions' table with RegionID and RegionName. They want to display a matrix visual with RegionName on rows and Year on columns, with the sum of Amount as values. However, the report displays only 'RegionID' instead of 'RegionName'. What is the most likely cause?

A.The relationship is configured as many-to-many.
B.The relationship direction is set to Both.
C.The RegionID column in the Sales table is hidden.
D.There is no active relationship between the Sales and Regions tables.
AnswerD

In Power BI, an active relationship is what enables automatic filter propagation between tables; without one, Power BI cannot traverse from the Sales table to the Regions table to retrieve RegionName. When a foreign key column like RegionID is placed in a visual and no active relationship links it to the Regions table, Power BI simply shows the raw ID value because it has no way to perform the lookup. The correct fix is to create or activate a relationship between Sales[RegionID] and Regions[RegionID] (typically with a single-direction filter), so that the relationship becomes active and the report can display the corresponding RegionName.

Why this answer

If there is no active relationship between the Sales and Regions tables, Power BI cannot use the RegionName from the Regions table to filter or group the Sales data. Instead, it defaults to displaying the RegionID from the Sales table, which is the only related field available in the visual. An active relationship must exist between the two tables on the RegionID columns for RegionName to appear in the matrix.

Exam trap

The trap here is that candidates often assume the RegionName column is missing due to a hidden column or relationship cardinality, but the core issue is the absence of an active relationship, which Power BI requires to combine data from different tables in a visual.

How to eliminate wrong answers

Option A is wrong because a many-to-many relationship would still allow RegionName to appear, though it might cause ambiguous aggregation; it does not cause the visual to show RegionID instead of RegionName. Option B is wrong because setting the relationship direction to Both (bidirectional cross-filtering) does not prevent RegionName from being used; it actually enables additional filtering but does not hide the RegionName column. Option C is wrong because hiding the RegionID column in the Sales table does not affect the display of RegionName from the Regions table; hiding a column only prevents it from appearing in the field list, not from being used in relationships or visuals.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Pl300 Visualize Analyze questions.

Start 20-question session