Knowledge + Practice

Microsoft Power BI Data Analyst PL-300 (PL-300) — Questions 451–525

966 questions total · 13pages · All types, answers revealed

Take a mock exam Exam hub

Page 7 of 13

451

Multi-Selecteasy

Which TWO are valid reasons to use a star schema design in Power BI? (Select exactly 2.)

Select 2 answers

A.It improves query performance by reducing the number of joins needed

B.It allows many-to-many relationships between dimensions

C.It is required to use time intelligence functions

D.It reduces model size by storing dimension attributes in separate tables

E.It reduces the number of tables in the model

AnswersA, D

Star schema optimizes join paths and filter propagation.

Why this answer

Options B and D are correct. Option B: Star schema simplifies the model and improves query performance because of fewer joins and a clear structure. Option D: Star schema reduces model size by normalizing dimensions and avoiding duplication.

Option A is wrong because star schema does not inherently reduce the number of tables; it typically increases them compared to a flat table. Option C is wrong because star schema supports many-to-one relationships, not many-to-many directly. Option E is wrong because star schema is not specifically required for time intelligence; a date table is needed, but star schema is broader.

Full explanation →

452

MCQeasy

You are designing a Power BI data model for a retail company. The model must include a table with product prices that change over time. Which table design should you use to support historical price analysis?

A.Create a separate table for price changes without any relationship

B.Add a price column to the product dimension and update it when price changes

C.Create a separate dimension table for price with effective date ranges and relate it to the fact table

D.Store the current price in the fact table and overwrite when price changes

AnswerC

Enables historical analysis by joining on date.

Why this answer

Option A is correct: A role-playing dimension table for price with date ranges supports slowly changing dimension Type 2. Option B is wrong because replacing prices in the fact table loses history. Option C is wrong because a single column in the product dimension only stores current price.

Option D is wrong because a separate unrelated table cannot be used in relationships.

Full explanation →

453

MCQmedium

You are building a star schema in Power BI. Your fact table contains sales data at the transaction level. Which of the following is the best practice for modeling the date dimension to support time intelligence functions like year-to-date (YTD) calculations?

A.Use the fact table's date column directly in measures without a date table

B.Create a date table with only the dates that appear in the fact table

C.Use multiple date columns (e.g., OrderDate, ShipDate) in the fact table

D.Create a date table with a contiguous range of dates and mark it as a date table

AnswerD

This enables time intelligence functions and proper filtering.

Why this answer

In a star schema, a dedicated date dimension table with a contiguous range of dates is essential for proper time intelligence. A single date column in the fact table is not sufficient because it lacks attributes like year, month, and quarter. Option C is correct.

Option A is wrong because multiple date columns in the fact table would violate normalization. Option B is wrong because a date table covering only sales dates would miss dates with no sales, causing incorrect YTD totals. Option D is wrong because the date table should have a unique date key.

Full explanation →

454

MCQmedium

You have a Power BI report that uses a live connection to an Azure Analysis Services tabular model. Users report that the report is slow to load. You need to improve performance without changing the data model. What should you do?

A.Implement report-level measures to pre-calculate complex aggregations.

B.Enable 'Load to report' on the dataset to import data into Power BI.

C.Reduce the number of relationships in the data model.

D.Increase the number of visuals on each report page to reduce the number of pages.

AnswerA

Report-level measures reduce server queries and improve performance.

Why this answer

Option A is correct because implementing report-level measures can reduce the number of queries sent to the server, improving performance. Option B is wrong because enabling 'Load to report' would import data, breaking the live connection requirement. Option C is wrong because increasing the page's visual count could degrade performance.

Option D is wrong because reducing the number of relationships would alter the data model, which is not allowed.

Full explanation →

455

Multi-Selectmedium

Which TWO actions should you take when designing a data model that includes a fact table with a large number of rows and multiple dimension tables? (Select exactly 2.)

Select 2 answers

A.Use integer-based foreign keys in the fact table to link to dimension tables

B.Create calculated columns in the fact table for additional attributes

C.Enable the Auto Date/Time feature for date columns

D.Hide the fact table from the report view

E.Set default summarization to 'Sum' for all numeric columns in the fact table

AnswersA, D

Integer keys improve performance and reduce storage.

Why this answer

Options A and C are correct. Option A: Using integer foreign keys reduces storage and improves join performance. Option C: Hiding the fact table from report view prevents users from accidentally querying it directly, promoting use of measures.

Option B is wrong because creating calculated columns in the fact table can increase model size and degrade performance. Option D is wrong because default summarization is not recommended for fact tables; measures should be used instead. Option E is wrong because disabling auto date/time is a general best practice but not specific to large fact tables.

Full explanation →

456

Matchingmedium

Match each data source type to an example.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

SQL Server

CSV

Salesforce

Azure SQL Database

REST endpoint

Why these pairings

Power BI can connect to a wide variety of data sources.

Full explanation →

457

MCQeasy

You are using Power Query to transform a column of dates. The dates are in the format 'MM/dd/yyyy' but your system locale expects 'dd/MM/yyyy'. When you change the data type to Date, many values become errors. How should you fix this?

A.Change the regional settings of Power BI Desktop to match the source format.

B.Use 'Replace Values' to swap day and month.

C.Use the 'Transform > Date > Parse' option and specify the format 'MM/dd/yyyy'.

D.Split the column by delimiter and recombine.

AnswerC

This correctly interprets the text as a date with the given format.

Why this answer

Option C is correct because Power Query's 'Parse' function allows you to explicitly specify the date format ('MM/dd/yyyy') when converting text to a Date type, overriding the system locale. This ensures that the transformation interprets the month and day correctly, preventing errors caused by locale mismatch.

Exam trap

The trap here is that candidates often assume changing regional settings (Option A) is the simplest fix, but they overlook that this globally alters date parsing for all data, potentially breaking other transformations, while the 'Parse' option provides a precise, column-level solution.

How to eliminate wrong answers

Option A is wrong because changing regional settings in Power BI Desktop affects all date interpretations globally, which can introduce errors in other parts of the report and is not a targeted fix for a single column. Option B is wrong because 'Replace Values' performs a simple text substitution without understanding date components, so swapping day and month would require complex logic and could corrupt data if values are not consistently formatted. Option D is wrong because splitting the column by delimiter and recombining is a manual, error-prone workaround that does not leverage Power Query's built-in date parsing capabilities and can introduce formatting inconsistencies.

Full explanation →

458

MCQhard

You are combining CSV files from a folder. The code above returns an error because some CSV files have inconsistent column names and data types. You need to modify the solution to handle variations in column structure. What should you do?

A.Change the delimiter to a semicolon and reconfigure the CSV parser.

B.Use Table.RemoveRows to remove rows that cause errors.

C.Add a custom column to each file to standardize data types before combining.

D.Use the Folder connector's 'Combine Files' transform, which handles schema merging automatically.

AnswerD

The built-in Combine Files feature in Power Query automatically detects column names and data types from the first file and merges subsequent files accordingly, handling variations gracefully.

Why this answer

Option D is correct because the 'Combine Files' transform in Power Query (Folder connector) automatically detects and merges columns from multiple CSV files, even when column names or data types vary. It uses a sample file to infer the schema and then applies transformations to handle inconsistencies, such as promoting headers and aligning data types, which resolves the error without manual intervention.

Exam trap

The trap here is that candidates often think they need to manually fix data types or remove errors (Options B or C), but the 'Combine Files' transform is designed specifically to automate schema merging, which is the correct solution for inconsistent column structures.

How to eliminate wrong answers

Option A is wrong because changing the delimiter to a semicolon does not address inconsistent column names or data types; it only changes how columns are parsed, which is irrelevant to schema merging. Option B is wrong because Table.RemoveRows removes rows that cause errors, but it does not fix the underlying issue of mismatched column structures; it merely discards data, potentially losing valid rows. Option C is wrong because adding a custom column to each file standardizes data types only for that column, not for all columns, and it requires manual effort per file, which is inefficient and does not handle variations in column names.

Full explanation →

459

MCQmedium

You are building a report for a logistics company. The dataset includes a 'Shipments' table with columns: ShipmentID, ShipDate, OriginCity, DestinationCity, Weight, Revenue, and Carrier. The company wants to analyze revenue trends by carrier over time. They have a date table marked as a date table. You create a line chart with ShipDate on the axis and Revenue as the value, with Carrier as the legend. However, the line chart shows a single line for each carrier, but the revenue values are aggregated across all dates, showing a constant line. What is the most likely cause?

A.There are missing relationships between Shipments and the date table.

B.The ShipDate column is of type 'Text' instead of 'Date'.

C.The Revenue column is a measure that is not summing correctly.

D.The date table is marked as a date table but not related to Shipments.

AnswerB

If ShipDate is text, Power BI will treat each unique date as a separate category, but if the values are dates, it may still aggregate incorrectly if not recognized.

Why this answer

Option B is correct because if the ShipDate column is stored as text, Power BI cannot treat it as a continuous date hierarchy. Even though a separate date table is marked as a date table, the line chart uses the ShipDate column from the Shipments table. When ShipDate is text, Power BI treats each unique text value as a separate category, and since there is no time intelligence, the revenue is aggregated across all rows for each carrier, resulting in a flat line showing the total revenue for that carrier.

The chart does not break down revenue by actual dates, so it appears constant.

Exam trap

The trap here is that candidates often assume a separate date table automatically resolves date-related issues, but the root cause is the data type of the column used on the axis, not the presence or absence of a date table relationship.

How to eliminate wrong answers

Option A is wrong because missing relationships between Shipments and the date table would typically cause the chart to show no data or an error, not a constant line; the line chart is using ShipDate directly from the Shipments table, not the date table. Option C is wrong because if the Revenue column were a measure that is not summing correctly, the values would likely be blank or show an error, not a constant aggregated value across all dates. Option D is wrong because the date table being marked as a date table but not related to Shipments would not affect the line chart if the chart uses ShipDate from the Shipments table; the chart would still plot dates from Shipments, but if ShipDate is text, the issue remains the same.

Full explanation →

460

MCQmedium

You are preparing data from an Excel workbook that contains multiple sheets. Each sheet has a similar structure but different data. You need to combine all sheets into a single table in Power Query. What is the most efficient approach?

A.Load each sheet as a separate query and then use 'Append Queries' to combine them.

B.Use 'Merge Queries' to join the sheets based on a common column.

C.Use the 'Combine Files' approach with the workbook as a folder, then select all sheets.

D.Create a new query that references each sheet query and then merges them.

AnswerC

Power Query can treat a single workbook as a folder of sheets and combine them automatically.

Why this answer

Option C is correct because the 'Combine Files' approach in Power Query treats the workbook as a folder, allowing you to select all sheets and automatically combine them into a single table. This is the most efficient method when multiple sheets have a similar structure, as it uses a single transformation step and handles dynamic sheet names without manual query creation.

Exam trap

The trap here is that candidates often confuse 'Append Queries' (which stacks rows) with 'Merge Queries' (which joins columns), and overlook the 'Combine Files' approach because they think it only applies to multiple files, not multiple sheets within a single workbook.

How to eliminate wrong answers

Option A is wrong because loading each sheet as a separate query and then using 'Append Queries' requires manual effort for each sheet, which is inefficient and not scalable for many sheets. Option B is wrong because 'Merge Queries' is designed for joining tables based on a common column (like a SQL JOIN), not for stacking rows from multiple sheets; it would produce a wide table instead of a long one. Option D is wrong because creating a new query that references each sheet query and then merging them still involves manual referencing and is less efficient than the built-in 'Combine Files' functionality, which automates the process.

Full explanation →

461

MCQmedium

You are merging two queries in Power Query. Query 'Orders' contains columns: OrderID, CustomerID, OrderDate. Query 'Customers' contains columns: CustomerID, CustomerName, Segment. You need to add the CustomerName to the Orders query. The relationship between Orders and Customers is many-to-one. Which join kind should you use?

A.Inner

B.Left Outer

C.Right Outer

D.Full Outer

AnswerB

Left outer join retains all orders and adds customer name where a match exists; non-matching customers will have null.

Why this answer

The goal is to retain all rows from the Orders table while adding CustomerName from the Customers table. A Left Outer join returns all rows from the first (left) table and only matching rows from the second (right) table, filling non-matches with null. Since the relationship is many-to-one, each OrderID may have a matching CustomerID, and you want to keep every order even if a customer is missing — exactly what Left Outer does.

Exam trap

The trap here is that candidates often confuse Left Outer with Inner join, thinking they must discard non-matching rows to avoid nulls, but the requirement explicitly says to add CustomerName to the Orders query, which implies preserving all orders even if a customer record is missing.

How to eliminate wrong answers

Option A is wrong because an Inner join would only return orders that have a matching customer, discarding any orders with missing or unmatched CustomerID values, which does not satisfy the requirement to add CustomerName to all orders. Option C is wrong because a Right Outer join would return all rows from the Customers table, which is not the target table; it would keep all customers even if they have no orders, and orders without a matching customer would be lost. Option D is wrong because a Full Outer join returns all rows from both tables, creating nulls on both sides for non-matches, which is unnecessary and would introduce extra rows for customers with no orders, bloating the result.

Full explanation →

462

MCQhard

Your organization uses Microsoft Entra ID for identity management. You have a Power BI dataset that uses DirectQuery to an Azure Analysis Services (AAS) model. The AAS model is configured to use service principal authentication. Users report that when they open a report connected to this dataset, they see an error: 'Cannot connect to the data source. The credentials provided are invalid.' What is the most likely cause?

A.The service principal secret or certificate used for authentication has expired.

B.Row-level security (RLS) on the AAS model is not configured correctly.

C.The service principal does not have 'Read' permission on the AAS model.

D.The dataset is in Import mode and requires a scheduled refresh.

AnswerA

Expired credentials cause authentication failures.

Why this answer

Option A is correct. The service principal credentials may have expired or been revoked. Option B is wrong because the dataset uses DirectQuery, not Import mode.

Option C is wrong because RLS is configured on the Power BI dataset, not on AAS. Option D is wrong because the service principal is configured for authentication, but the error indicates invalid credentials, not lack of permissions.

Full explanation →

463

MCQhard

Refer to the exhibit. You are implementing row-level security (RLS) in Power BI. The JSON policy above is applied to the 'Sales' table. The user is in the 'SalesRegion' role. Which rows will the user see?

A.Rows where Region is 'North' and 'South'.

B.No rows, because there is a conflict.

C.Rows where Region is 'North' only.

D.Rows where Region is 'South' only.

AnswerC

The role filter '[Region] = "North"' applies, ignoring the table-level filter.

Why this answer

Option B is correct because the role filter overrides the table-level filter for users in that role. Option A is wrong because the role filter takes precedence. Option C is wrong because the role filter applies only to the role.

Option D is wrong because RLS filters rows, not columns.

Full explanation →

464

MCQeasy

You need to prepare data from a folder containing multiple CSV files with identical structure. What is the most efficient way to load all files into a single table?

A.Import each CSV file separately and then append them

B.Use the 'From Folder' data source and then click 'Combine & Transform Data'

C.Write a Python script in Power Query to read and combine files

D.Use a dataflow to connect to the folder and apply the 'Combine Files' transformation

AnswerB

This automatically combines all files into one table.

Why this answer

Option B is correct because the 'From Folder' data source in Power Query automatically detects multiple CSV files with identical structure and provides a 'Combine & Transform Data' button that merges them into a single table in one step. This is the most efficient method as it eliminates the need for manual imports or scripting, leveraging Power Query's built-in file combination logic.

Exam trap

The trap here is that candidates may think manual appending (Option A) is simpler or that Python scripting (Option C) is a valid Power Query feature, but the exam tests knowledge of Power Query's native 'Combine Files' functionality as the most efficient and integrated method.

How to eliminate wrong answers

Option A is wrong because importing each CSV file separately and then appending them is inefficient and error-prone, requiring manual steps for each file and breaking the automated refresh capability. Option C is wrong because writing a Python script in Power Query is not natively supported; Power Query uses M language, and Python integration requires additional configuration (e.g., Python in Power BI Desktop) and is not the most efficient or standard approach for this task. Option D is wrong because using a dataflow is an overkill for a simple folder import; dataflows are designed for complex ETL processes and cloud-based transformations, not for directly loading local CSV files into a single table in Power BI Desktop.

Full explanation →

465

Multi-Selectmedium

Which TWO of the following are valid reasons to use a calculated table instead of a calculated column in Power BI?

Select 2 answers

A.To create a summary table that is not present in the source.

B.To reduce model size by storing only aggregated data.

C.To create a date table with a continuous range of dates.

D.To create a column that depends on other columns in the same row.

AnswersA, C

Calculated tables can create new aggregations.

Why this answer

Options B and D are correct. Calculated tables are used to create new tables based on DAX expressions, useful for creating a date table (B) or a summary table (D). Calculated columns are row-level and cannot produce new tables.

Option A is not a reason; calculated columns can also use DAX. Option C is not a reason; both calculated tables and columns are recalculated on refresh.

Full explanation →

466

Multi-Selecteasy

Which THREE of the following are valid data types in Power BI?

Select 3 answers

A.Currency

B.Whole Number

C.Decimal Number

D.Time

E.Date/Time

AnswersB, C, E

Whole Number is a valid data type for integers.

Why this answer

Option A, B, and D are valid data types in Power BI. Option C is not a standard data type; 'Currency' is not a separate type (it's Decimal). Option E is not a standard type; 'Time' is not separate from DateTime.

Full explanation →

467

MCQeasy

You have a Power BI report that includes a pie chart. Users complain that it is difficult to compare the sizes of slices. Which visual should you recommend instead to improve comparison?

A.A treemap.

B.A donut chart.

C.A bar chart.

D.A scatter plot.

AnswerC

Bar charts allow easy comparison.

Why this answer

Option A is correct because bar charts allow easy comparison of lengths. Option B is wrong because tree maps are also hard to compare. Option C is wrong because scatter plots are for correlation.

Option D is wrong because donut charts are similar to pie charts.

Full explanation →

468

MCQhard

Refer to the exhibit. You run this DAX query and receive an error. What is the most likely reason?

A.The column 'Category' does not exist

B.SUMMARIZECOLUMNS is deprecated

C.SUMMARIZECOLUMNS requires a measure, not an aggregation expression

D.EVALUATE cannot be used in DAX queries

AnswerC

SUMMARIZECOLUMNS expects a measure or a table expression.

Why this answer

SUMMARIZECOLUMNS cannot use SUM directly; it requires an explicit filter context or a measure. A measure should be defined first or use CALCULATE. The syntax is correct but the expression is invalid.

Full explanation →

469

MCQeasy

You need to create a visual that displays the sales trend over the last 12 complete months. Which approach should you use?

A.Create a calculated column that flags last 12 months.

B.Add a slicer for the last 12 months.

C.Write a measure that calculates sales for last 12 months and use it in a visual.

D.Use a relative date filter on the date field set to 'Last 12 months'.

AnswerD

Relative date filter automatically updates to the last 12 complete months.

Why this answer

Option C is correct because a relative date filter on a date hierarchy shows the last N periods. Option A is wrong because a slicer requires manual selection. Option B is wrong because a calculated column is static.

Option D is wrong because a measure alone does not filter visuals.

Full explanation →

470

MCQmedium

Refer to the exhibit. A user is a member of both 'Manager' and 'Executive' roles. Which rows will the user see?

A.Only rows where Department is 'Sales'.

B.Rows where Department is 'Sales' or 'Marketing'.

C.All rows, because role membership overrides filters.

D.Rows where Department is 'Sales' only, but with both role permissions.

AnswerB

Combined roles result in union of filters.

Why this answer

Option B is correct because when a user belongs to multiple roles, the filters are combined with OR. So the user sees rows where Department is 'Sales' (from Manager) OR Department is 'Sales' or 'Marketing' (from Executive). The union is Sales and Marketing rows.

Option A is wrong because it ignores the Executive role. Option C is wrong because it shows only Sales. Option D is wrong because it shows all departments.

Full explanation →

471

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

Query Editor can merge tables (like SQL joins).

Why this answer

Option B is correct because the Power BI Query Editor (Power Query) includes a 'Merge Queries' feature that allows you to join two tables based on matching values in a common column. This is a fundamental data transformation operation used to combine data from different sources or tables before loading into the data model.

Exam trap

The trap here is that candidates often confuse the Query Editor's data transformation capabilities with data modeling tasks (like creating relationships or measures) or security configurations, leading them to select options that belong to other Power BI Desktop views.

Full explanation →

472

MCQeasy

You have a dataset with a column 'FullName' containing values like 'John Doe'. You need to split this column into 'FirstName' and 'LastName' using the space delimiter. Which Power Query transformation should you use?

A.Split Column by Delimiter.

B.Merge Columns.

C.Extract Text.

D.Replace Values.

AnswerA

Splits a column into multiple columns based on a delimiter.

Why this answer

Option A is correct because the 'Split Column by Delimiter' transformation in Power Query is specifically designed to divide a single text column into multiple columns based on a specified delimiter, such as a space. In this scenario, selecting the column 'FullName' and using 'Split Column > By Delimiter' with a space delimiter will correctly separate 'John Doe' into 'FirstName' (John) and 'LastName' (Doe). This is the standard approach for parsing delimited text within Power Query.

Exam trap

The trap here is that candidates may confuse 'Extract Text' with splitting, thinking it can parse delimiters, but 'Extract Text' only extracts fixed-length or positional substrings, not delimiter-based splits.

How to eliminate wrong answers

Option B is wrong because 'Merge Columns' is used to combine multiple columns into one, not to split a single column. Option C is wrong because 'Extract Text' allows you to pull out substrings based on position or length (e.g., first N characters), but it cannot dynamically split on a delimiter like a space. Option D is wrong because 'Replace Values' is designed to substitute one text value with another, not to separate a column into multiple parts.

Full explanation →

473

MCQmedium

Your Power BI report includes a map visual showing store locations. However, some locations are not appearing correctly because of ambiguous place names. What should you do to ensure accurate geocoding?

A.Aggregate the data by country

B.Switch to a bubble chart

C.Use latitude and longitude fields instead of location names

D.Change the map visual to a filled map

AnswerC

Exact coordinates prevent geocoding errors.

Why this answer

Using latitude and longitude fields bypasses Bing's geocoding, ensuring accuracy. Changing the map style does not fix geocoding, using a filled map is for regions, and a bubble chart is not geographic.

Full explanation →

474

MCQhard

Refer to the exhibit. A user created this measure to calculate sales for the same period last year. However, the measure returns incorrect values when used in a matrix with month granularity. What is the most likely cause?

A.The DATE function is incorrectly specified

B.The 'Date' table is not marked as a date table

C.The VAR CurrentDate is not needed

D.CALCULATE should not be used with SAMEPERIODLASTYEAR

AnswerB

Time intelligence functions require a marked date table with continuous dates.

Why this answer

SAMEPERIODLASTYEAR relies on a contiguous date table; if the date table is not marked or has gaps, it may shift incorrectly. The DATE function is not the issue, and CALCULATE is used correctly. The time intelligence functions require a proper date table.

Full explanation →

475

Multi-Selecthard

Which THREE of the following are valid reasons to use a calculated column instead of a measure in Power BI?

Select 3 answers

A.The value is needed in a row-level security rule

B.The value is an aggregation (e.g., SUM) that changes with user interaction

C.The value must be used in a relationship between tables

D.The value is needed as a slicer or filter in a visual

E.The value is a time intelligence calculation that depends on the current filter context

AnswersA, C, D

RLS can use calculated columns.

Why this answer

Option A, B, and D are correct. Option A is correct because calculated columns are evaluated during data refresh and can be used as slicers. Option B is correct because calculated columns can be used in relationships.

Option D is correct because calculated columns are available in the data model for row-level security. Option C is wrong because measures are more efficient for dynamic aggregations. Option E is wrong because measures are better for time intelligence.

Full explanation →

476

MCQmedium

Refer to the exhibit. You write this Power Query M code to import data. What does the final step do?

A.Sorts rows by Amount descending

B.Groups rows by Amount

C.Removes the Amount column

D.Filters rows where Amount > 100

AnswerD

The condition filters rows.

Why this answer

The final step in the Power Query M code filters the table to keep only rows where the 'Amount' column value is greater than 100. This is achieved by the `Table.SelectRows` function with the condition `each [Amount] > 100`, which evaluates each row and retains those meeting the predicate. The result is a reduced dataset containing only transactions with an Amount exceeding 100.

Exam trap

The trap here is that candidates may confuse `Table.SelectRows` with sorting or grouping operations, or mistakenly think it removes a column, because the condition references a specific column name.

How to eliminate wrong answers

Option A is wrong because sorting rows by Amount descending would require `Table.Sort` with `Order.Descending`, not `Table.SelectRows`. Option B is wrong because grouping rows by Amount would use `Table.Group` with an aggregation, not a row-level filter. Option C is wrong because removing the Amount column would involve `Table.RemoveColumns`, which eliminates the column entirely rather than filtering rows based on its values.

Full explanation →

477

MCQmedium

You deploy a Power BI app to a workspace with an app-only license (Premium Per User). Users report that they can access the app but cannot see any visuals in the reports. The dataset uses Import mode. What is the most likely issue?

A.The report uses DirectQuery and the data source is offline.

B.The users do not have a Premium Per User license assigned.

C.The report is published to a shared dataset that has been deleted.

D.The dataset has row-level security (RLS) that filters all rows for these users.

AnswerB

PPU content requires PPU license to render.

Why this answer

The workspace uses a Premium Per User (PPU) license, which requires each user accessing content in that workspace to have a PPU license assigned. Without it, users can see the app in the list but cannot render visuals because the dataset (Import mode) is processed on PPU-capacity nodes that enforce license checks. This is the most likely cause given the symptom of empty visuals.

Exam trap

The trap here is that candidates may confuse 'app-only license' with 'shared capacity' or think that publishing an app grants access to all users, but PPU requires individual license assignment even for app viewers.

How to eliminate wrong answers

Option A is wrong because the dataset uses Import mode, not DirectQuery, so the data source being offline would not cause empty visuals (Import mode caches data in memory). Option C is wrong because if the shared dataset were deleted, the report would show a 'Could not load model' error or missing data source, not empty visuals. Option D is wrong because RLS filters rows but does not hide all visuals; users would still see the report layout with empty visuals if all rows are filtered, but the question states 'cannot see any visuals,' which implies the visuals fail to render entirely, not just show no data.

Full explanation →

478

MCQhard

You are troubleshooting a Power BI DirectQuery model connected to Azure Synapse Analytics. The report shows stale data even though the underlying database is updated hourly. What should you check first?

A.Whether the dataset is using Import mode instead of DirectQuery.

B.Whether the user has RLS permissions that filter data incorrectly.

C.Whether the report has 'Disable caching' enabled in the dataset settings.

D.Whether the dataset is configured for scheduled refresh.

AnswerC

Correct. DirectQuery still uses some caching; disabling it forces fresh queries.

Why this answer

Option A is correct because DirectQuery does not cache data; each query goes to the source. However, Power BI may cache query results at the report level. The 'Disable caching' option ensures fresh data.

Option B is wrong because scheduled refresh is for import models. Option C is wrong because RLS does not affect data freshness. Option D is wrong because storage mode is import; DirectQuery is a separate mode.

Full explanation →

479

Multi-Selecthard

Which THREE features are available in Power BI to support natural language queries?

Select 3 answers

A.Key Influencers visual

B.Suggested Questions

C.Q&A visual

D.Synonyms for tables and columns

E.Quick Measures

AnswersB, C, D

Provides prebuilt questions for users.

Why this answer

Options A, B, and C are correct. Q&A visual allows typing questions; Suggested Questions appear in the Q&A visual; Synonyms help Q&A understand business terms. Option D is wrong because Quick Measures create DAX, not natural language.

Option E is wrong because Key Influencers is an AI visual but not natural language.

Full explanation →

480

MCQmedium

You are building a report to analyze sales performance by region. You need to allow users to dynamically switch between viewing data as a bar chart and a line chart without modifying the report page. Which feature should you use?

A.Use bookmarks with buttons to toggle between charts.

B.Add a slicer that changes the chart type.

C.Use a custom visual with built-in toggle.

D.Create a drillthrough page for each chart type.

AnswerA

Bookmarks capture the state of visuals and can be toggled via buttons.

Why this answer

Option A is correct because bookmarks with buttons allow users to switch between visual states dynamically. Option B is wrong because a slicer filters data, not switches chart types. Option C is wrong because a drillthrough page navigates to a different page.

Option D is wrong because a custom visual would require additional development.

Full explanation →

481

Multi-Selecthard

Which TWO actions are valid for improving query performance in DirectQuery mode?

Select 2 answers

A.Disable relationship enforcement to speed up joins.

B.Convert the model to Import mode.

C.Create aggregated tables to pre-summarize data.

D.Use calculated columns in the fact table.

E.Reduce the number of columns in the table.

AnswersC, E

Reduces the amount of data queried.

Why this answer

Option A is correct because reducing columns in the table reduces the data retrieved. Option C is correct because creating summarized tables can reduce data volume. Option B is wrong because disabling relationship enforcement can lead to incorrect results.

Option D is wrong because calculated columns often degrade performance in DirectQuery. Option E is wrong because Import mode is not available in DirectQuery.

Full explanation →

482

MCQhard

You are a Power BI administrator at a large enterprise. You need to ensure that all Power BI datasets in your organization use certified data sources only, to maintain data quality. You have enabled data source certification in your Microsoft Purview governance portal. Which additional step must you take to enforce that only certified data sources are used in Power BI datasets?

A.In the Power BI admin portal, enable the 'Require certified data sources' tenant setting.

B.Create dataflows that use only certified data sources and require report creators to use those dataflows.

C.Apply sensitivity labels to all certified data sources in Purview.

D.Configure workspace security to restrict dataset creation to administrators only.

AnswerA

Correct. This setting enforces the requirement.

Why this answer

Option A is correct because the 'Require certified data sources' tenant setting in the Power BI admin portal is the specific control that enforces datasets to use only data sources that have been certified in Microsoft Purview. Without this setting enabled, certification is merely informational and not enforced, allowing uncertified sources to be used. This setting works in conjunction with Purview's data source certification to block dataset creation or refresh if any source lacks certification.

Exam trap

The trap here is that candidates confuse data source certification with other governance features like sensitivity labels or dataflows, assuming those can enforce certification, when only the dedicated tenant setting in the Power BI admin portal provides enforcement.

How to eliminate wrong answers

Option B is wrong because creating dataflows with certified sources does not enforce that all datasets across the organization use certified sources; it only provides a recommended approach but does not block uncertified sources. Option C is wrong because sensitivity labels in Purview control data classification and protection, not data source certification enforcement; they are unrelated to the requirement for certified sources. Option D is wrong because restricting dataset creation to administrators does not enforce the use of certified data sources; it only limits who can create datasets, not what sources they can use.

Full explanation →

483

MCQeasy

Your Power BI workspace contains a dataset that uses a DirectQuery connection to Azure SQL Database. You need to ensure that only users with the 'Viewer' role in the workspace can query the dataset, but they should not be able to see the underlying SQL credentials. What should you do?

A.Use Windows authentication with the user's own credentials.

B.Use row-level security (RLS) to restrict query access.

C.Configure the dataset to use a service principal with a credential stored in Power BI.

D.Use object-level security (OLS) to hide the credential columns.

AnswerC

Service principal credentials are not exposed to users.

Why this answer

Option A is correct because using a service principal with a credential stored in Power BI ensures users do not see credentials. Option B is wrong because stored credentials are not visible to users. Option C is wrong because RLS does not hide credentials.

Option D is wrong because OLS does not apply to credentials.

Full explanation →

484

MCQhard

You are a data analyst at a multinational retail company. The company uses Microsoft Power BI to analyze sales data from multiple regions. The source data is stored in Azure SQL Database and includes tables: Sales (OrderID, ProductID, Quantity, Amount, OrderDate, StoreID), Stores (StoreID, StoreName, Region, Country), Products (ProductID, ProductName, Category, Price). The model is imported daily. You need to design a semantic model that supports the following requirements: 1) Allow users to filter by year and month using a single slicer. 2) Ensure that time intelligence functions (e.g., TOTALYTD, SAMEPERIODLASTYEAR) work correctly. 3) Minimize model size. 4) Provide a consistent date dimension for all fact tables. The Sales table has orders from 2018-01-01 to 2025-12-31. You decide to create a date table. Which of the following approaches should you take?

A.Create a date table using DAX with CALENDAR and mark it as a date table.

B.Use the Sales[OrderDate] column directly and create a calculated column for year and month.

C.Use Power BI's auto-generated date hierarchy for each date column.

D.Import a date table from the source database that includes all dates and additional attributes.

AnswerA

This creates a minimal, efficient date table that supports all time intelligence.

Why this answer

Option B is correct because creating a date table in DAX using CALENDAR and marking it as a date table satisfies all requirements: it minimizes model size (no extra columns), enables time intelligence, and provides a consistent dimension. Option A is wrong because Power BI's auto-generated date hierarchy cannot be marked as a date table for time intelligence. Option C is wrong because importing a full date table from SQL adds overhead without benefit.

Option D is wrong because using the Sales[OrderDate] column directly does not provide a separate date dimension and may cause issues with time intelligence.

Full explanation →

485

MCQeasy

You are building a Power BI report for a sales team. You have a table named 'Sales' with columns: SalesDate, ProductID, Quantity, UnitPrice, Discount. You also have a 'Date' table with continuous date range. You create a relationship from Sales[SalesDate] to Date[Date]. You need to calculate the total sales amount (Quantity * UnitPrice - Discount). You write the following measure: TotalSales = SUMX(Sales, Sales[Quantity] * Sales[UnitPrice] - Sales[Discount]) The measure returns the correct total. However, when you slice by month from the Date table, the total does not change. What is the most likely cause?

A.The Discount column might have negative values causing the total to be incorrect.

B.The measure should use SUM instead of SUMX because there are no row-level calculations.

C.The Date table is not marked as a date table, and the relationship is not set to filter in both directions.

D.The measure does not use the Date table; it references only the Sales table, so it ignores filters from other tables.

AnswerC

If the Date table is not properly marked, the slicer may not filter the Sales table correctly. Also, the relationship direction should be single from Date to Sales.

Why this answer

Option C is correct because when a Date table is not marked as a date table, Power BI does not automatically enable bidirectional cross-filtering between the Date and Sales tables. Without this, slicers on the Date table (e.g., month) do not propagate filters to the Sales table, so the measure, which iterates over Sales rows, remains unaffected. Marking the Date table as a date table ensures that date hierarchies and slicers correctly filter related fact tables.

Exam trap

The trap here is that candidates often assume any relationship automatically allows filters to flow in both directions, but Power BI requires explicit configuration (marking as date table or setting bidirectional cross-filtering) for date-based slicers to affect measures that only reference the fact table.

How to eliminate wrong answers

Option A is wrong because negative discount values do not prevent the measure from responding to slicers; they would only affect the calculated total value, not filter propagation. Option B is wrong because SUMX is required here to perform row-by-row multiplication and subtraction; SUM cannot handle arithmetic across multiple columns. Option D is wrong because the measure does reference the Sales table, but the issue is not about the measure ignoring filters—it is about the Date table not being able to push filters to Sales due to missing bidirectional cross-filtering or date table marking.

Full explanation →

486

MCQmedium

You are designing a data model in Power BI that includes a fact table called 'Sales' and dimension tables 'Customer', 'Product', and 'Date'. The 'Sales' table contains columns: 'SalesID', 'CustomerID', 'ProductID', 'DateKey', 'Quantity', and 'Amount'. You need to ensure that the model follows star schema best practices and that filters from the 'Customer' table propagate correctly to the 'Sales' table. What should you do?

A.Merge the Customer and Sales tables into a single flat table.

B.Set the cross-filter direction to Both on the relationship between Customer and Sales.

C.Create a many-to-many relationship between Customer and Sales using SalesID.

D.Create a one-to-many relationship from Customer (one side) to Sales (many side) based on CustomerID.

AnswerD

This is the standard star schema pattern.

Why this answer

Option B is correct because a star schema requires a one-to-many relationship from dimension tables to fact tables, with the dimension table on the one side. Option A is wrong because many-to-many relationships would break star schema simplicity. Option C is wrong because bidirectional filtering can cause ambiguity and is not recommended by default.

Option D is wrong because merging tables into a single flat table is the opposite of star schema.

Full explanation →

487

MCQeasy

You are combining data from multiple Excel files stored in SharePoint Online. Each file has the same structure but different data. You need to create a solution that automatically includes new files added to the SharePoint folder without manual intervention. What should you use?

A.Use Power Automate to copy new files to a blob storage, then import from there.

B.Use 'Merge queries' to append each new file manually.

C.Use 'Get Data from SharePoint Online Folder' and then 'Combine files' transform.

D.Use 'Get Data from SharePoint Online List' and load each file separately.

AnswerC

The folder connector with combine files automatically processes all files in the folder, including new ones, on each refresh.

Why this answer

Option B is correct because the 'Combine files' transform in Power Query from a SharePoint folder automatically detects and combines all files in the folder, and when refreshed, it includes any new files. Option A is wrong because Get Data from SharePoint list does not combine files. Option C is wrong because Power Automate would require additional setup and is not native Power Query.

Option D is wrong because merging queries requires manual steps each time.

Full explanation →

488

MCQmedium

You need to ensure that only users with a specific security group in Microsoft Entra ID can access a Power BI dataset. The dataset is used in a shared workspace that also contains other datasets. What should you configure?

A.Move the dataset to a separate workspace and manage access via workspace roles.

B.Configure row-level security (RLS) on the dataset to filter data based on the security group.

C.Use the 'Share' feature on the dataset to grant access to the security group.

D.Configure the app permissions to restrict access to the dataset.

AnswerA

A separate workspace allows granular control via workspace roles, restricting dataset access to the assigned security group.

Why this answer

Option B is correct because in Power BI, workspace-level roles (Admin, Member, Contributor, Viewer) control access to the entire workspace. To restrict access to a specific dataset within a shared workspace, you must use row-level security (RLS) or a separate workspace. Option A is wrong because app permissions control the app, not the dataset directly.

Option C is wrong because sharing a report does not restrict dataset access. Option D is wrong because dataset-level permissions are not granularly configurable in the same way; RLS or separate workspace is required.

Full explanation →

489

MCQhard

You are analyzing a DAX query as shown in the exhibit. You need to determine the result set. The model contains tables: Date, Product, and Sales with relationships. Which statement accurately describes the output?

A.The query returns total sales per year and category for Amount > 100

B.The query returns total sales for each year, ignoring category

C.The query returns sales amounts only for products with Amount > 100

D.The query returns total sales for each category, ignoring year

AnswerA

SUMMARIZECOLUMNS groups by Year and Category, and the CALCULATE with FILTER sums only where Amount > 100.

Why this answer

Option A is correct because the DAX query uses SUMMARIZE to group sales by 'Year' from the Date table and 'Category' from the Product table, then filters the Sales table to include only rows where Amount > 100. The result is a table of total sales (sum of Amount) for each combination of year and category that meets the filter condition.

Exam trap

The trap here is that candidates often misinterpret the SUMMARIZE function as returning individual rows rather than aggregated groups, or they overlook that the filter condition applies to the underlying Sales rows, not to the aggregated result.

How to eliminate wrong answers

Option B is wrong because the query includes 'Category' in the SUMMARIZE grouping columns, so it does not ignore category; it returns totals per year and category, not per year alone. Option C is wrong because the query returns total sales (sum of Amount) per group, not individual sales amounts for each product; it aggregates, not lists. Option D is wrong because the query includes 'Year' in the grouping, so it does not ignore year; it returns totals per year and category, not per category alone.

Full explanation →

490

MCQmedium

You have a Power BI dataset that uses a live connection to an Azure Analysis Services (AAS) model. The AAS model has object-level security (OLS) that hides certain measures. Your Power BI report users need to see those measures. What should you do?

A.Use Power BI Desktop object-level security to override AAS settings.

B.Configure row-level security (RLS) in Power BI to grant access.

C.Change the dataset to import mode and then apply OLS in Power BI.

D.Modify the object-level security roles in Azure Analysis Services to include the measures.

AnswerD

Access is controlled by AAS.

Why this answer

Option C is correct because Power BI live connection respects AAS security; to show hidden measures, you need to modify OLS in AAS. Option A is wrong because RLS is for rows, not measures. Option B is wrong because OLS in Power BI is only for import mode.

Option D is wrong because you cannot override AAS security from Power BI.

Full explanation →

491

Multi-Selectmedium

Which THREE of the following are benefits of using a calculated column over a measure in Power BI?

Select 3 answers

A.They can be referenced by other calculated columns.

B.They are computed once during data refresh and stored in memory.

C.They use less memory than measures.

D.They can be used in slicers and report filters.

E.They are more efficient for large datasets than measures.

AnswersA, B, D

Calculated columns can depend on each other.

Why this answer

Option A is correct: calculated columns are evaluated during data refresh. Option B is correct: they can be used as slicers. Option D is correct: they can be referenced in other calculated columns.

Option C is incorrect because measures are more efficient for aggregations. Option E is incorrect because measures are more memory efficient.

Full explanation →

492

MCQmedium

You have a Power BI dataset that uses DirectQuery mode. The underlying SQL view now includes a new column. What must you do to make the new column available in Power BI?

A.Schedule a daily refresh in the service

B.Create a new measure to reference the column

C.Publish the report again

D.Refresh the dataset in Power BI Desktop

AnswerD

Refreshing updates the schema from the source.

Why this answer

When a SQL view used in DirectQuery mode is updated with a new column, you must refresh the dataset in Power BI Desktop to pull the updated schema into the model. DirectQuery does not cache data, but the metadata (field list) is cached; refreshing the dataset in Power BI Desktop re-queries the source to discover the new column. Only then can you use the column in visuals or measures.

Exam trap

The trap here is that candidates confuse DirectQuery with Import mode and assume that a scheduled refresh in the service will automatically bring in new columns, when in fact DirectQuery requires a manual metadata refresh in Power BI Desktop before republishing.

How to eliminate wrong answers

Option A is wrong because scheduling a daily refresh in the Power BI service only applies to Import mode datasets; DirectQuery mode does not cache data, so scheduled refresh does not update the schema. Option B is wrong because creating a new measure referencing the column is impossible if the column is not yet recognized in the model; the column must first be available in the field list. Option C is wrong because publishing the report again merely uploads the current .pbix file; if the column was not added in Power BI Desktop before publishing, it will still be missing in the service.

Full explanation →

493

MCQeasy

You are developing a Power BI report for a sales team. The data source is an Excel file with a single sheet containing columns: Date, Salesperson, Product, Units Sold, Revenue. The file is updated weekly. You need to model the data to allow analysis of revenue by salesperson and product over time. What is the simplest and most effective approach?

A.Load the data into a SQL Server database first, then import from there.

B.Import the Excel file into Power BI and create a date table for time intelligence.

C.Use DirectQuery on the Excel file to avoid importing.

D.Split the Excel data into separate dimension and fact tables in Power Query.

AnswerB

This is straightforward and enables time-based analysis.

Why this answer

Option A is correct because importing the Excel file and creating a date table allows for time-based analysis with minimal effort. Option B is wrong because using DirectQuery on an Excel file is not supported. Option C is wrong because splitting into multiple tables is unnecessary for a single sheet.

Option D is wrong because Power BI can handle the data without an external database.

Full explanation →

494

MCQmedium

You are loading data from a SQL Server database into Power BI. The source table contains a column 'SalesAmount' with occasional NULL values. In the Power Query Editor, you need to replace NULLs with 0 before loading. What is the most efficient transformation?

A.Use 'Replace Errors' with value 0.

B.Use 'Fill Down' to fill nulls with the previous value.

C.Use 'Replace Values' to replace null with 0.

D.Use 'Change Type' to convert to a non-nullable type.

AnswerC

Directly replaces nulls with 0 in one step.

Why this answer

Option C is correct because 'Replace Values' in Power Query Editor is specifically designed to replace null values with a specified value, such as 0. This transformation is the most efficient and direct method for handling NULLs in a column, as it operates at the query level before data is loaded into the Power BI data model.

Exam trap

The trap here is that candidates may confuse 'Replace Errors' with 'Replace Values', mistakenly thinking NULLs are errors, or they may overcomplicate the solution by using 'Fill Down' or type changes instead of the direct replacement method.

How to eliminate wrong answers

Option A is wrong because 'Replace Errors' is used to replace error values (e.g., from data type conversion failures), not NULL values; NULLs are not errors. Option B is wrong because 'Fill Down' propagates the previous non-null value downward, which is not appropriate for replacing NULLs with a constant 0 and can introduce incorrect data patterns. Option D is wrong because 'Change Type' to a non-nullable type will cause the query to fail or produce errors when encountering NULLs, rather than replacing them with 0.

Full explanation →

495

MCQeasy

Your organization uses Microsoft Defender for Cloud Apps to monitor Power BI activity. You need to receive an alert when a user exports a report with a sensitivity label of 'Highly Confidential' from Power BI service. What should you configure?

A.Set up a Microsoft 365 compliance alert for data export events.

B.Enable audit logging in Power BI and configure alerts in Microsoft Sentinel.

C.Apply a protection policy in Microsoft Purview that blocks export for 'Highly Confidential' labels.

D.Create an activity policy in Microsoft Defender for Cloud Apps.

AnswerD

Defender for Cloud Apps activity policies can detect exports with specific sensitivity labels and trigger alerts.

Why this answer

Option A is correct because Microsoft Defender for Cloud Apps allows you to create an activity policy that triggers alerts based on specific activities, such as exporting reports with specific sensitivity labels. Option B is wrong because Power BI audit logs can be monitored but require custom alerts via Sentinel or other tools; Defender for Cloud Apps provides built-in alerting. Option C is wrong because sensitivity labels themselves do not generate alerts.

Option D is wrong because Microsoft 365 compliance alerts are separate and not focused on Power BI exports.

Full explanation →

496

Multi-Selecteasy

Which THREE are types of Power Query transforms that can be used to clean data? (Choose three.)

Select 3 answers

A.Remove duplicates

B.Group rows by a column

C.Replace values

D.Merge queries

E.Change data type

AnswersA, C, E

Removing duplicates cleans the data by eliminating redundant rows.

Why this answer

Option A is correct because the 'Remove duplicates' transform in Power Query identifies and eliminates rows with identical values across selected columns, which is a fundamental data cleaning operation to ensure data integrity and avoid skewed analysis.

Exam trap

The trap here is that candidates often confuse data preparation transforms (like merging or grouping) with data cleaning transforms, leading them to select options that are actually for data shaping or integration rather than direct data quality improvement.

Full explanation →

497

Multi-Selecthard

Which THREE of the following are best practices for data modeling in Power BI? (Select exactly three.)

Select 3 answers

A.Use bi-directional cross-filtering relationships for all tables.

B.Store calculated logic in calculated columns rather than measures when possible.

C.Create a separate date table for time intelligence functions.

D.Hide the primary key columns in dimension tables from report view.

E.Use a star schema design with fact and dimension tables.

AnswersC, D, E

Enables proper time-based calculations.

Why this answer

Option C is correct because Power BI's time intelligence functions (e.g., TOTALYTD, SAMEPERIODLASTYEAR) require a separate, continuous date table marked as a date table to work correctly. Without a dedicated date table, these functions may return incorrect results or fail due to missing contiguous dates. This table should have a single date column with no gaps and be related to the fact table's date column.

Exam trap

The trap here is that candidates often think bi-directional cross-filtering is a safe default (option A) or that calculated columns are always preferable for simplicity (option B), but the exam tests the understanding that these choices degrade performance and model clarity.

Full explanation →

498

MCQhard

Refer to the exhibit. You are reviewing a Power BI activity log entry. What action should you take to ensure compliance if the user who created the report should not have access to 'Confidential' data?

A.Delete the report immediately.

B.Change the sensitivity label on the report to 'General'.

C.Investigate the user's permissions on the dataset 'SalesDataset' to verify they are authorized to access confidential data.

D.Ignore the event because the report creation is logged but not necessarily a violation.

AnswerC

The user created a report labeled 'Confidential', so their access to the dataset should be reviewed.

Why this answer

Option B is correct because the activity log shows the user created a report with a 'Confidential' sensitivity label. The best action is to investigate the user's access permissions to the underlying dataset to ensure they are authorized. Option A is wrong because the report was already created.

Option C is wrong because removing the label does not address the root cause. Option D is wrong because the event indicates the report was created, not just an attempt.

Full explanation →

499

Multi-Selectmedium

Which TWO of the following are best practices when designing a Power BI data model?

Select 2 answers

A.Use calculated columns instead of measures

B.Use a star schema design

C.Denormalize all tables into a single flat table

D.Use bidirectional relationships as default

E.Hide foreign key columns from report view

AnswersB, E

Star schema is the recommended modeling approach.

Why this answer

Options A and D are correct. Option B is wrong because calculated columns should be avoided when possible; measures are preferred. Option C is wrong because bidirectional relationships can cause ambiguity and should be used sparingly.

Option E is wrong because star schema is the recommended approach.

Full explanation →

500

MCQmedium

You are the Power BI administrator for a large enterprise. The company has a Power BI Premium capacity with a single dataset that is used by multiple reports and dashboards. The dataset is refreshed daily at 3:00 AM, and the refresh typically completes within 2 hours. Recently, users have reported that the dataset is not showing the most recent data until after 6:00 AM. You investigate and find that the scheduled refresh is taking 4 hours to complete, and there are no errors in the refresh history. The dataset uses import mode and connects to an on-premises SQL Server data warehouse. The data model contains several large fact tables and multiple calculated tables and measures. What should you do to reduce the refresh time and ensure data is available by 5:00 AM?

A.Remove all calculated tables and measures and replace them with calculated columns in Power Query

B.Implement incremental refresh on the fact tables to refresh only new and changed data

C.Change the dataset storage mode to DirectQuery to avoid the import process

D.Install an additional on-premises data gateway and configure load balancing

AnswerB

Incremental refresh reduces the volume of data processed, speeding up refresh.

Why this answer

Implementing incremental refresh on the fact tables allows Power BI to refresh only new or changed data instead of the entire dataset each time. This significantly reduces the refresh window, especially for large fact tables, because only the latest partition (e.g., today's data) is processed. Since the scheduled refresh starts at 3:00 AM and must complete by 5:00 AM, incremental refresh can cut the refresh time from 4 hours to under 2 hours by avoiding reprocessing historical data.

Exam trap

The trap here is that candidates often choose Option C (DirectQuery) thinking it eliminates refresh time entirely, but they overlook that DirectQuery changes the entire query model and is not a direct fix for a scheduled import refresh that is simply taking too long due to data volume.

How to eliminate wrong answers

Option A is wrong because replacing calculated tables and measures with calculated columns in Power Query does not reduce refresh time; calculated columns are computed during data load and can actually increase memory and processing overhead, while measures are computed at query time and have no impact on refresh duration. Option C is wrong because changing the dataset storage mode to DirectQuery would bypass the import process entirely, but it would also eliminate the benefits of import mode (such as fast query performance) and would require the on-premises SQL Server to handle all query loads, potentially causing performance issues and breaking existing reports that rely on import-mode features like calculated tables. Option D is wrong because installing an additional on-premises data gateway and configuring load balancing improves gateway throughput and reliability but does not address the root cause of slow refresh—the full reload of large fact tables; the gateway is not the bottleneck here since there are no errors in refresh history and the issue is the volume of data being refreshed.

Full explanation →

501

MCQeasy

A data analyst needs to combine two queries in Power Query: 'Sales2023' and 'Sales2024', both with identical column structures. Which operation should the analyst use to append the rows from 'Sales2024' to 'Sales2023'?

A.Append Queries

B.Merge Queries

C.Group By

D.Pivot Column

AnswerA

Append stacks rows from multiple tables.

Why this answer

The Append Queries operation in Power Query is designed to combine rows from two or more tables with identical column structures, stacking the rows of 'Sales2024' beneath those of 'Sales2023'. This is the correct method because it preserves all columns and adds data vertically, which matches the requirement to append rows.

Exam trap

The trap here is that candidates often confuse Append Queries with Merge Queries, thinking both combine data, but Merge Queries joins columns horizontally (like a SQL JOIN) while Append Queries stacks rows vertically.

How to eliminate wrong answers

Option B is wrong because Merge Queries performs a join based on matching columns (like SQL JOINs), which combines columns horizontally rather than appending rows vertically, and would require a key column to match records. Option C is wrong because Group By aggregates data by grouping rows based on a column and calculating summaries (e.g., sum, count), which does not add rows from another table. Option D is wrong because Pivot Column transforms unique values from a column into new columns, reshaping data from rows to columns, which is the opposite of appending rows.

Full explanation →

502

MCQeasy

You are a business analyst at a marketing agency. You receive a weekly export from a web analytics platform as a CSV file. The file contains columns: Date, Campaign, Impressions, Clicks, Conversions. You need to create a Power BI report that shows trends over time, with the ability to filter by campaign. The CSV file is updated weekly and you want to automate the refresh. You also want to ensure that any new campaigns are automatically included in the report. You have limited experience with Power BI. What should you do?

A.Use Power Query to read the CSV from a local folder, but schedule the refresh using a personal gateway.

B.Import the CSV file directly into Power BI Desktop, create the report, and publish to Power BI Service. Manually re-import the CSV each week.

C.Enable incremental refresh on the dataset to only load new data each week.

D.Create a Power BI dataflow that reads the CSV file from a SharePoint folder, transforms the data (e.g., change data types), and then load the dataflow as a dataset into Power BI. Schedule the dataflow to refresh weekly.

AnswerD

Dataflows provide easy automated refresh and transformation.

Why this answer

Option D is correct because it uses a Power BI dataflow to read the CSV from a SharePoint folder, which supports scheduled refresh without a personal gateway. The dataflow can automatically include new campaigns as they appear in the folder, and the scheduled weekly refresh ensures the report stays up to date. This approach is ideal for users with limited Power BI experience because dataflows handle transformation and refresh centrally in the Power BI Service.

Exam trap

The trap here is that candidates often choose incremental refresh (Option C) thinking it automates new data loading, but they overlook that incremental refresh requires a properly configured date column and does not inherently handle new campaigns unless the source folder structure supports it, whereas a dataflow with a SharePoint folder is the simpler and correct solution for this scenario.

How to eliminate wrong answers

Option A is wrong because using a local folder with a personal gateway requires the gateway to be running on a machine with access to the folder, which adds complexity and is not fully automated for a weekly export; also, new campaigns would be included only if the folder path is dynamic, but the personal gateway introduces a dependency. Option B is wrong because manually re-importing the CSV each week defeats the automation requirement and is not scalable for weekly updates. Option C is wrong because incremental refresh requires a date/time field with a defined range and a supporting policy in Power BI Service, and it does not automatically handle new campaigns unless the data source itself supports partitioning; it also requires a more advanced setup than a simple CSV import.

Full explanation →

503

Drag & Dropmedium

Drag and drop the steps to import data from a SQL Server database into Power BI Desktop into the correct order.

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

Steps

Order

Why this order

Importing from SQL Server involves selecting the source, connecting to the server and database, choosing tables or queries, and loading or transforming data.

Full explanation →

504

MCQhard

You have a Power BI data model with a table named 'Sales' that has a many-to-many relationship with 'Product' through a bridge table. When creating a measure to calculate total sales by product, you notice the totals are double-counting. What is the most likely cause?

A.The model lacks a date dimension

B.The Product table has incorrect data types

C.The bridge table has duplicate rows

D.The cross-filter direction is set to single instead of both

AnswerD

In many-to-many relationships, bidirectional cross-filtering ensures proper aggregation and prevents double-counting.

Why this answer

Option A is correct because many-to-many relationships often require a bidirectional cross-filter direction to avoid double-counting. Option B is wrong because the bridge table is necessary. Option C is wrong because a calendar table would not solve double-counting.

Option D is wrong because data types are not the issue.

Full explanation →

505

Multi-Selecteasy

Which THREE data sources can be used with Power BI Dataflows? (Choose three.)

Select 3 answers

A.Power BI dataset

B.Excel file stored on local drive

C.OData feed

D.Azure SQL Database

E.SharePoint Online list

AnswersC, D, E

Correct. OData feeds are supported.

Why this answer

OData feeds are supported as a data source in Power BI Dataflows because Dataflows use the Power Query engine, which can connect to OData endpoints to import data. This allows you to pull data from RESTful APIs that expose OData services, making it a valid and common source for cloud-based data ingestion.

Exam trap

The trap here is that candidates often confuse Power BI Dataflows with Power Query in Power BI Desktop, where local file sources like Excel are allowed, but Dataflows in the service strictly require cloud-accessible sources.

Full explanation →

506

MCQhard

You are reviewing a Power Query M expression that transforms column types. The 'SalesAmount' column contains values like '1,234.56' (with a comma as thousands separator). After applying this transformation, what is the likely result?

A.The transformation will result in errors for rows containing commas.

B.The column will be converted to text automatically.

C.The column will be successfully converted to numbers.

D.The transformation will ignore the comma and convert the number correctly.

AnswerA

The comma causes the conversion to fail, resulting in errors.

Why this answer

Option A is correct because Power Query's default type conversion for numeric columns expects a period as the decimal separator and no thousands separator. When the 'SalesAmount' column contains values like '1,234.56' with a comma as a thousands separator, attempting to convert the column directly to a number type (e.g., using 'Change Type' or 'Table.TransformColumnTypes') will cause errors for rows containing commas, as Power Query cannot parse the comma as part of a valid number. The comma is not a recognized numeric character in the default locale, so the conversion fails.

Exam trap

The trap here is that candidates assume Power Query will automatically handle locale-specific formatting (like commas as thousands separators) during type conversion, but in reality, it fails with errors unless the data is preprocessed or the correct culture is specified.

How to eliminate wrong answers

Option B is wrong because Power Query does not automatically convert the column to text; the transformation explicitly changes the column type to a number, and if it fails, it produces errors, not a text conversion. Option C is wrong because the comma acts as a non-numeric character in the default locale, preventing successful conversion to numbers without prior data cleaning (e.g., replacing commas with empty strings). Option D is wrong because Power Query does not ignore the comma; it strictly parses the value and fails when encountering an unrecognized character, unlike some other tools that might auto-detect locale settings.

Full explanation →

507

Multi-Selectmedium

Which TWO actions can improve data refresh performance in Power BI?

Select 2 answers

A.Merge all queries into a single query.

B.Add calculated columns in Power Query instead of DAX.

C.Disable load for intermediate queries used only for reference.

D.Filter rows at the source to reduce data volume.

E.Keep all columns from the source data to avoid re-importing.

AnswersC, D

Prevents unnecessary data loading.

Why this answer

Option C is correct because disabling load for intermediate queries used only as reference steps prevents Power BI from materializing those tables in the data model. This reduces memory consumption and refresh time, as the engine skips loading data that isn't needed for reports or further transformations.

Exam trap

The trap here is that candidates may confuse 'disable load' with 'disable refresh' or think that merging queries (Option A) is always beneficial, when in fact it can reduce parallelism and hurt performance.

Full explanation →

508

MCQmedium

You are modeling a many-to-many relationship between 'Students' and 'Courses' via a junction table 'Enrollments'. You need to create a measure that counts the number of students enrolled in at least one course. The relationship between Students and Enrollments is one-to-many, and between Courses and Enrollments is one-to-many. What DAX measure should you use?

A.COUNTROWS(Enrollments)

B.COUNT(Courses[CourseID])

C.COUNTA(Students[StudentID])

D.DISTINCTCOUNT(Students[StudentID])

AnswerD

Counts unique students, works with many-to-many.

Why this answer

Option B is correct. DISTINCTCOUNT on Students[StudentID] counts unique students, which works correctly with many-to-many because the filter from Courses propagates to Enrollments and then to Students. Option A counts rows in Enrollments, which could be multiple per student.

Option C counts courses, not students. Option D counts students but only those with enrollments; however, the filter context may cause blanks. DISTINCTCOUNT is safer.

Full explanation →

509

MCQhard

You have a Power BI data model with a table 'Orders' containing columns: OrderID, CustomerID, OrderDate, Amount. You want to create a measure that calculates the running total of sales over time, ordered by OrderDate. Which DAX expression should you use?

A.CALCULATE(SUM(Orders[Amount]), FILTER(ALLSELECTED(Orders), Orders[OrderDate] <= MAX(Orders[OrderDate])))

B.SUMX(Orders, RANKX(ALL(Orders), Orders[OrderDate], , ASC) * Orders[Amount])

C.TOTALYTD(SUM(Orders[Amount]), Orders[OrderDate])

D.CALCULATE(SUM(Orders[Amount]), FILTER(ALL(Orders), Orders[OrderDate] <= EARLIER(Orders[OrderDate])))

AnswerD

EARLIER refers to the current row in the filter context, creating a running total.

Why this answer

CALCULATE with FILTER and EARLIER is a common pattern for running totals. Option D is correct. Option A is wrong because TOTALYTD is for year-to-date, not running total across all dates.

Option B is wrong because SUM with FILTER and ALLSELECTED may not preserve order correctly. Option C is wrong because RANKX is not needed.

Full explanation →

510

MCQmedium

A Power BI dataset is configured to use Import storage mode. The dataset includes a fact table with 100 million rows and several dimension tables. The report is slow when users interact with visuals. You need to improve query performance without changing the storage mode. Which action should you take?

A.Create aggregations on the fact table.

B.Increase the scheduled refresh frequency.

C.Reduce the number of dimension tables.

D.Enable 'Load to report' for all tables.

AnswerA

Aggregations pre-summarize data, improving query speed.

Why this answer

Creating aggregations on the fact table allows Power BI to pre-summarize data at higher granularity levels, reducing the amount of data scanned during query execution. Since the dataset uses Import mode, aggregations leverage the in-memory columnar storage to serve queries from pre-computed tables, significantly improving visual response times without altering the storage mode.

Exam trap

The trap here is that candidates often confuse data refresh frequency (Option B) with query performance, or mistakenly think reducing dimensions (Option C) is a valid optimization, when in fact aggregations are the correct technique for speeding up Import mode queries.

How to eliminate wrong answers

Option B is wrong because increasing the scheduled refresh frequency only updates the data more often; it does not improve query performance against the existing imported data. Option C is wrong because reducing the number of dimension tables would break the star schema design, potentially causing data redundancy and incorrect relationships, and it does not directly address query speed. Option D is wrong because enabling 'Load to report' for all tables simply makes them available in the Power BI model; it has no impact on query performance and may even increase memory usage.

Full explanation →

511

MCQeasy

You are creating a Power BI report and need to visualize the relationship between two numerical variables, such as sales amount and profit. Which visual type is most appropriate?

A.Line chart

B.Stacked bar chart

C.Pie chart

D.Scatter chart

AnswerD

Scatter chart shows correlation between two numerical variables.

Why this answer

Option A is correct because a scatter chart is designed to show the relationship between two numerical variables. Option B is wrong because a pie chart shows proportions of a whole. Option C is wrong because a stacked bar chart compares parts of a whole across categories.

Option D is wrong because a line chart shows trends over time.

Full explanation →

512

Multi-Selecthard

Which THREE of the following are best practices for designing Power BI reports for mobile devices?

Select 3 answers

A.Use a single column of visuals

B.Include many small text tables

C.Place visuals side by side to maximize space

D.Use large, easy-to-tap slicers

E.Group related measures into a single visual

AnswersA, D, E

Single column works best on mobile screens.

Why this answer

Option A is correct because mobile screens have limited width, so a single-column layout ensures visuals scale properly without horizontal scrolling, which is a core recommendation in Microsoft's mobile report design guidelines. This approach maintains readability and touch interaction by stacking visuals vertically, avoiding the need for users to pinch or zoom.

Exam trap

The trap here is that candidates confuse maximizing screen space (side-by-side visuals) with mobile optimization, but Microsoft's guidance explicitly prioritizes touch-friendly, single-column layouts over density.

Full explanation →

513

MCQhard

You are working with a large dataset in Power BI that contains sales transactions. You need to create a measure that calculates the running total of sales over time. However, the data model does not include a separate date table, and you want to minimize the model size. What is the most efficient approach?

A.Create a separate date table and use the TOTALYTD function in a measure.

B.Write a measure using VAR and FILTER with ALL to compute running total.

C.Create calculated columns for Year and Month, then use SUMX with FILTER.

D.Use the EARLIER function in a calculated column to compute running total.

AnswerA

Best practice for performance and time intelligence.

Why this answer

Option A is correct because creating a separate date table and using TOTALYTD leverages Power BI's time intelligence functions, which require a continuous date table marked as a date table. This approach is efficient because time intelligence functions are optimized for performance and minimize model size by avoiding calculated columns or complex row-context iterations. Without a date table, TOTALYTD cannot function correctly, as it relies on a proper date hierarchy.

Exam trap

Microsoft often tests the misconception that time intelligence functions like TOTALYTD can work without a separate date table, or that calculated columns are more efficient than measures for running totals, leading candidates to choose options that increase model size or degrade performance.

How to eliminate wrong answers

Option B is wrong because using VAR and FILTER with ALL to compute a running total is less efficient than time intelligence functions, as it requires scanning the entire table in row context and can degrade performance on large datasets, and it does not leverage Power BI's optimized time intelligence engine. Option C is wrong because creating calculated columns for Year and Month increases model size and storage overhead, and using SUMX with FILTER in a measure is less efficient than a dedicated time intelligence function like TOTALYTD. Option D is wrong because using EARLIER in a calculated column to compute a running total is highly inefficient, as it iterates over rows in a nested context, leading to poor performance and larger model size due to materialized columns.

Full explanation →

514

Multi-Selecthard

You are modeling data with a many-to-many relationship between 'Student' and 'Class' tables. Which THREE configurations can handle this scenario?

Select 3 answers

A.Use CROSSFILTER function to enable many-to-many filtering

B.Remove duplicate rows from both tables

C.Create a bridge table with StudentID and ClassID

D.Change relationship to one-to-many by creating a unique key

E.Use a calculated column to concatenate Class names in the Student table

AnswersA, C, E

Allows filtering across both tables.

Why this answer

Options A, B, and C are correct. Option A uses a bridge table which is the standard approach. Option B uses a calculated column concatenation for limited scenarios.

Option C uses CROSSFILTER to enable many-to-many filtering. Option D is wrong because removing duplicates loses information. Option E is wrong because changing to one-to-many incorrectly assumes uniqueness.

Full explanation →

515

Multi-Selectmedium

Which TWO data sources can you connect to from Power BI Desktop using a native connector? (Select two.)

Select 2 answers

A.Azure Blob Storage

B.Dataverse

C.MySQL database (on-premises)

D.Oracle database (on-premises)

E.MongoDB

AnswersA, B

Native connector available.

Why this answer

Azure Blob Storage is a correct answer because Power BI Desktop includes a native connector for Azure Blob Storage, allowing direct connection to blob containers without needing a gateway or custom script. This connector uses the Azure storage REST API to access data stored in blobs, enabling import of CSV, JSON, and Parquet files directly.

Exam trap

The trap here is that candidates often assume any popular database (like MySQL, Oracle, or MongoDB) has a native connector, but Power BI Desktop only provides native connectors for cloud-based services and specific Microsoft platforms, while on-premises databases require gateways or generic connectors like ODBC.

Full explanation →

516

MCQmedium

You have a Power BI dataset that contains a table with sales data and a separate date table. You create a measure that uses CALCULATE and DATESYTD to show year-to-date sales. The measure returns incorrect values for the first month of the year. What is the most likely cause?

A.The relationship between tables is single-directional.

B.The date table does not contain a continuous range of dates for the entire year.

C.The date table uses month granularity instead of day.

D.The date table is not marked as a date table.

AnswerB

Correct. DATESYTD needs continuous dates.

Why this answer

Option D is correct because DATESYTD requires a continuous date range; if the date table does not include all dates, the YTD calculation may be incomplete. Option A is wrong because DATESYTD does not require marking as date table. Option B is wrong because relationship direction is not the issue.

Option C is wrong because month granularity is not the problem.

Full explanation →

517

MCQhard

You have a Power BI dataset that is refreshed every hour from an on-premises data source using an enterprise gateway. The refresh consistently fails at 2:00 AM. What is the most likely cause?

A.The on-premises data gateway is scheduled to reboot at 2:00 AM.

B.The refresh is failing due to a transient network error.

C.The data source is undergoing maintenance in the cloud.

D.The scheduled refresh time conflicts with another refresh.

AnswerA

A reboot would cause the gateway to be unavailable.

Why this answer

The consistent failure at exactly 2:00 AM strongly points to a scheduled event on the on-premises data gateway, such as a reboot or maintenance window. Enterprise gateways can be configured to reboot periodically for updates or health reasons, and if this coincides with the refresh schedule, the gateway will be unavailable, causing the refresh to fail. Transient errors or cloud maintenance would not produce a perfectly consistent daily failure at the same time.

Exam trap

Microsoft often tests the concept that consistent, time-specific failures are almost always due to a scheduled event on the gateway or data source, not random network issues or cloud-side problems, which candidates might incorrectly assume due to lack of familiarity with gateway maintenance windows.

How to eliminate wrong answers

Option B is wrong because transient network errors are intermittent and unpredictable, not consistently occurring at the exact same time daily. Option C is wrong because the data source is on-premises, not in the cloud, so cloud maintenance is irrelevant to the refresh failure. Option D is wrong because a refresh time conflict would cause a different error (e.g., 'Refresh is already in progress') and would not be tied to a specific time like 2:00 AM unless another refresh is also scheduled at that exact time, which is less likely than a gateway reboot.

Full explanation →

518

Multi-Selectmedium

Which TWO features can be used to implement row-level security (RLS) in Power BI? (Select TWO.)

Select 2 answers

A.Bookmarks that hide rows

B.Report-level filters

C.Slicer with user principal name

D.Static row-level security in Power BI Desktop

E.DAX filter expressions in roles

AnswersD, E

RLS is configured in Power BI Desktop using roles and DAX.

Why this answer

Options B and D are correct. Option A is wrong because report page filters apply to all users. Option C is wrong because a slicer does not enforce security.

Option E is wrong because a bookmark does not enforce security.

Full explanation →

519

MCQhard

You are troubleshooting a Power BI DirectQuery model that connects to a SQL Server database. A slicer on 'Region' is slow to respond. The region column has 50 distinct values. What is the best optimization?

A.Create an index on the Region column in the source database

B.Increase the cache size in Power BI Desktop

C.Switch the model to Import mode

D.Reduce the number of distinct values in Region

AnswerA

Indexing the column used in slicers improves query performance in DirectQuery.

Why this answer

Option D is correct because in DirectQuery mode, queries are sent to the source; creating an index on the region column will speed up filtering. Option A is wrong because Import mode is not always feasible or desired. Option B is wrong because increasing cache size does not help DirectQuery.

Option C is wrong because reducing cardinality would lose information.

Full explanation →

520

MCQeasy

You have a Power BI model with a table named Sales that includes columns: OrderDate, Amount, and CustomerID. You need to create a measure that returns the total sales amount for the previous month based on the current filter context. Which DAX expression should you use?

A.CALCULATE(SUM(Sales[Amount]), PARALLELPERIOD('Date'[Date], -1, MONTH))

B.CALCULATE(SUM(Sales[Amount]), PREVIOUSMONTH('Date'[Date]))

C.CALCULATE(SUM(Sales[Amount]), DATEADD('Date'[Date], -1, MONTH))

D.CALCULATE(SUM(Sales[Amount]), NEXTMONTH('Date'[Date]))

AnswerB

PREVIOUSMONTH returns a set of dates for the previous month, and CALCULATE adjusts context.

Why this answer

Option B is correct because PREVIOUSMONTH returns a single month period shifted back by one month from the last date in the current filter context, which directly gives the total sales for the previous month. This measure respects the current filter context and works correctly when a proper date table is used.

Exam trap

The trap here is that candidates often confuse PREVIOUSMONTH with DATEADD or PARALLELPERIOD, not realizing that PREVIOUSMONTH is specifically designed to return a single full previous month based on the last date in context, while DATEADD shifts dates individually and PARALLELPERIOD can return multiple periods.

How to eliminate wrong answers

Option A is wrong because PARALLELPERIOD returns a set of parallel periods (e.g., entire months) but does not guarantee a single previous month; it can return multiple months if the current period spans multiple months, leading to incorrect totals. Option C is wrong because DATEADD with -1 month shifts each date by one month but does not restrict to a full previous month; it can return partial month data or overlapping periods depending on the granularity. Option D is wrong because NEXTMONTH returns the next month, not the previous month, which is the opposite of what is required.

Full explanation →

521

MCQmedium

You are importing data from a REST API that returns JSON. The JSON structure includes nested arrays. You need to transform the data into a flat table structure in Power Query. Which transform should you apply?

A.Use 'Expand to New Rows' on the list columns

B.Use 'Merge Queries' to combine the nested data

C.Use 'Pivot Column' on the nested columns

D.Use 'Unpivot Columns' on the record columns

AnswerA

Expanding list columns creates new rows for each element, flattening the structure.

Why this answer

Option A is correct because the 'Expand to New Rows' transform (found under the 'Transform' tab in Power Query) is specifically designed to flatten nested list columns—such as arrays within JSON—by creating a new row for each element in the list. This converts the hierarchical JSON structure into a flat table, which is the required outcome for further analysis in Power BI.

Exam trap

The trap here is that candidates often confuse 'Expand to New Rows' (for lists) with 'Expand to New Columns' (for records), or mistakenly think 'Unpivot Columns' can flatten arrays, when in fact 'Unpivot' only works on record-type columns, not list-type columns.

How to eliminate wrong answers

Option B is wrong because 'Merge Queries' is used to combine two separate tables based on matching keys, not to flatten nested arrays within a single JSON structure. Option C is wrong because 'Pivot Column' transforms unique values from a column into new columns, which would not flatten nested arrays but rather spread data horizontally, creating a wider table. Option D is wrong because 'Unpivot Columns' is used to convert columns into rows (e.g., for normalization), but it operates on record columns, not list columns, and cannot directly expand nested JSON arrays.

Full explanation →

522

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 with sales, a visual-level filter should be applied on the Amount field to exclude blanks.

Why this answer

Option D is correct because 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.

Full explanation →

523

MCQmedium

You need to create a Power BI data model that includes a date dimension. The source data contains a table with a Date column covering 2015-2025. You want to ensure that all dates in the model have a contiguous range for time intelligence. What should you do?

A.Hide the existing Date column and rely on auto date/time.

B.Add a calculated column for year and month from the existing Date column.

C.Create a calculated column using CALENDAR to generate a continuous date range and use that.

D.Use the existing Date column as the date table and mark it as a date table.

AnswerC

A calculated table using CALENDAR creates a contiguous date range. Then mark it as a date table.

Why this answer

Option C is correct because the CALENDAR function generates a contiguous range of dates, which is essential for accurate time intelligence calculations (e.g., YTD, QoQ). By creating a calculated column with CALENDAR, you ensure no gaps exist in the date dimension, even if the source data has missing dates. This approach allows you to mark the table as a date table and enable DAX time intelligence functions like TOTALYTD or SAMEPERIODLASTYEAR.

Exam trap

The trap here is that candidates often think marking an existing date column as a date table (Option D) is sufficient, but they overlook the requirement for a contiguous range, which is critical for time intelligence to work correctly.

How to eliminate wrong answers

Option A is wrong because relying on auto date/time creates hidden date tables that are not user-defined, cannot be marked as a date table, and may not cover the full contiguous range needed for custom time intelligence. Option B is wrong because adding calculated columns for year and month does not address gaps in the date range; it only extracts parts from existing dates, leaving missing dates unhandled. Option D is wrong because using the existing Date column as the date table without ensuring contiguity can lead to gaps in the date dimension, causing time intelligence functions to return incorrect results or errors.

Full explanation →

524

Multi-Selecthard

Which THREE factors should you consider when designing a Power BI data model for a star schema? (Select three.)

Select 3 answers

A.Use many-to-many relationships between dimensions

B.Fact tables should contain numeric measures and foreign keys

C.Dimension tables should be normalized to reduce redundancy

D.Dimension tables should contain descriptive attributes

E.Relationships should be one-to-many from dimension to fact

AnswersB, D, E

Fact tables store quantitative data and relationships to dimensions.

Why this answer

Option B is correct because fact tables in a star schema store numeric, aggregatable measures (e.g., sales amount, quantity) and foreign keys that reference dimension tables. This structure enables efficient summarization and slicing by dimensions, which is a core requirement for Power BI performance and DAX calculations.

Exam trap

Microsoft often tests the misconception that normalization (Option C) is beneficial for star schemas, when in fact denormalization is preferred to avoid performance penalties from extra join hops in Power BI's query engine.

Full explanation →

525

MCQmedium

You are connecting to a SQL Server database using Import mode. The source table contains a column 'SalesAmount' with a few null values. You need to replace nulls with 0 before loading. What is the most efficient step to achieve this in Power Query Editor?

A.Use 'Replace Values' to replace null with 0

B.Use 'Replace Errors' with value 0

C.Use 'Fill Down' to propagate previous values

D.Add a custom column with an if statement

AnswerA

Directly replaces nulls with 0.

Why this answer

Option A is correct because 'Replace Values' can replace null with 0. Option B is incorrect because 'Fill Down' fills with previous non-null value, not 0. Option C is incorrect because 'Transform > Replace Errors' replaces errors, not nulls.

Option D is incorrect because adding a custom column is less efficient.

Full explanation →

Page 7 of 13

All pages

1 2 3 4 5 6 7 8 9 10 11 12 13

Practice PL-300 by domain

Target a specific domain to shore up weak areas.

Prepare the data Deploy and maintain assets Model the data Visualize and analyze the data Manage and secure Power BI

See all domains with question counts →