Courseiva

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

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

Take a mock examExam hub
Page 3

Page 4 of 13

Page 5
226
MCQhard

You are building a Power BI report for a multinational corporation. The data model includes a fact table named Orders with columns: OrderID, CustomerID, OrderDate, ProductID, Quantity, UnitPrice, and Discount. The Customer dimension contains columns: CustomerID, CustomerName, Country, and Segment. The Product dimension contains: ProductID, ProductName, Category, Subcategory, and Price. You need to create a calculated column in the Orders table that calculates the net amount after discount for each order line (Quantity * UnitPrice * (1 - Discount)). You also need to ensure that the column is stored in the model for high-performance filtering. Which DAX expression should you use?

A.NetAmount = SUMX(Orders, Orders[Quantity] * Orders[UnitPrice] * (1 - Orders[Discount]))
B.NetAmount = Orders[Quantity] * Orders[UnitPrice] * (1 - Orders[Discount])
C.NetAmount = CALCULATE(SUM(Orders[Quantity]) * SUM(Orders[UnitPrice]) * (1 - SUM(Orders[Discount])))
D.NetAmount = Orders[Quantity] * Orders[UnitPrice] - Orders[Discount]
AnswerB

This is a valid calculated column expression that multiplies columns and creates a new column.

Why this answer

Option A uses the correct syntax and creates a calculated column that will be materialized in the model. Option B is a measure, not a calculated column. Option C is a measure.

Option D uses SUMX, which is for measures and would not create a stored column.

Full explanation →
227
MCQmedium

Refer to the exhibit. You have a Power BI semantic model with a role 'Sales Manager'. The role is defined with read permission on the Sales table but only on the Amount column. When the user 'salesmgr@contoso.com' creates a report using this model, which of the following will they be able to see?

A.All columns in all tables in the model.
B.No data because the role is not assigned to the user.
C.Only the Amount column from the Sales table.
D.All columns in the Sales table.
AnswerC

The columnPermission explicitly allows only Amount.

Why this answer

Option A is correct because the role only grants read access to the Amount column. All other columns in the Sales table are not accessible. Option B is wrong because the role does not allow seeing the entire table.

Option C is wrong because the role does not include any other tables. Option D is wrong because the role does not block all data.

Full explanation →
228
MCQmedium

You are building a star schema model in Power BI. You have a fact table of sales transactions and dimension tables for Date, Customer, Product, and Store. The Date table contains a column 'FiscalYear' that you want to use for time intelligence calculations. What is the best practice for handling the Date relationship?

A.Create a separate fiscal date table and relate it to the fact table using the FiscalYear column.
B.Use the built-in DATESYTD function directly on the OrderDate column from the fact table.
C.Create a composite key using FiscalYear and Quarter columns in the Date table and relate to the fact table.
D.Mark the Date table as a date table using the Calendar icon in the Table tools ribbon and set a relationship on the Date column.
AnswerD

This enables time intelligence functions and ensures proper filtering.

Why this answer

Option D is correct because marking the Date table as a date table (via the Calendar icon in Table tools) and creating a relationship on the Date column is the best practice for time intelligence in Power BI. This ensures that DAX time intelligence functions (e.g., TOTALYTD, SAMEPERIODLASTYEAR) work correctly by using a single, continuous date column that aligns with the fact table's date column. It also avoids the need for composite keys or separate fiscal tables, maintaining a clean star schema.

Exam trap

The trap here is that candidates often think they need a separate fiscal table or composite keys to handle fiscal years, but Power BI's date table marking feature inherently supports fiscal calendars through the 'Mark as Date Table' option and the 'Start of Fiscal Year' setting, making those workarounds unnecessary and incorrect.

How to eliminate wrong answers

Option A is wrong because creating a separate fiscal date table related via FiscalYear would break the star schema's simplicity and prevent proper time intelligence, as DAX functions require a continuous date column, not a fiscal year column. Option B is wrong because DATESYTD requires a date column from a properly marked date table, not a direct call on a fact table column, and it would ignore the fiscal year context. Option C is wrong because a composite key using FiscalYear and Quarter would not provide a continuous date range for time intelligence, and Power BI relationships should be on a single, unique column (typically the date) to avoid ambiguity and support proper filtering.

Full explanation →
229
MCQmedium

You are building a Power BI semantic model that combines sales data from an on-premises SQL Server database and a cloud-based CRM system. The CRM system returns data in a de-normalized format with multiple fact tables. You need to design the model to minimize data duplication and improve query performance. What should you do?

A.Export the CRM data to Excel and import that Excel file along with the SQL Server data.
B.Create a SQL Server view that joins both sources and import the view.
C.Use DirectQuery for both sources to keep data in their original databases.
D.Import both sources into Power BI and create relationships.
AnswerD

Import mode stores data in-memory for fast queries and allows relationship creation.

Why this answer

Option B is correct because importing both sources into Power BI and creating relationships between tables allows the Power BI engine to optimize queries in-memory. Option A is wrong because DirectQuery would incur performance overhead with on-premises data. Option C is wrong because combining at the source doesn't reduce duplication and may be complex.

Option D is wrong because exporting the CRM data to a single Excel file introduces manual steps and data staleness.

Full explanation →
230
MCQeasy

You have a Power BI report that includes a line chart showing monthly sales. You want to add a trend line to help users identify the overall direction of sales over time. Which feature should you use?

A.Forecast option in the visual
B.Add a DAX measure for linear regression
C.Format pane to change line style
D.Analytics pane in the visual
AnswerD

The Analytics pane contains the Trend line option.

Why this answer

Option A is correct because the Analytics pane in line chart visuals provides the 'Trend line' option. Option B is wrong because a forecast is different from a trend line. Option C is wrong because the format pane deals with visual appearance, not analytics.

Option D is wrong because DAX is not required to add a trend line.

Full explanation →
231
Multi-Selecthard

You are importing data from a folder containing multiple Excel files with the same structure. You use Power Query's 'Combine Files' feature. Which TWO statements about this process are correct?

Select 2 answers
A.It automatically removes duplicate rows across files.
B.You can change the transformation order after combining.
C.It uses the first file as a template for transformation.
D.It automatically creates relationships between files.
E.It generates a sample file query to define transformations.
AnswersC, E

The first file's transformations are applied to others.

Why this answer

Option C is correct because when you use Power Query's 'Combine Files' feature, it uses the first file as a template to infer the schema and transformations. This sample file query defines how each subsequent file is processed, ensuring consistent column types and transformations across all files.

Exam trap

The trap here is that candidates often assume the 'Combine Files' feature automatically handles deduplication or relationship creation, when in fact it only standardizes transformations across files based on the first file's structure.

Full explanation →
232
MCQeasy

You need to create a Power BI report that uses data from Microsoft Excel files stored in SharePoint Online. The data should refresh automatically every hour. What is the recommended approach?

A.Use the SharePoint Online folder connector in Power Query and set up a scheduled refresh in the Power BI service.
B.Use the Excel Online connector in Power BI Desktop.
C.Manually upload the Excel files to the Power BI service each time.
D.Import the Excel files into Power Query and then publish.
AnswerA

This allows automatic refresh of Excel files from SharePoint.

Why this answer

Option A is correct because Power BI can connect to Excel files in SharePoint via the SharePoint Folder connector, and then schedule refresh. Option B is wrong because importing to Power Query is not a data source; it's a transformation step. Option C is wrong because manual uploads do not support scheduled refresh.

Option D is wrong because Excel Online is not a direct data source for Power BI refresh.

Full explanation →
233
MCQhard

You are creating a star schema in Power BI. You have a fact table named Sales with columns: Date, ProductID, CustomerID, Quantity, and UnitPrice. You need to create a relationship between Sales and a Date dimension. Which column in the Date dimension should be used as the key to relate to the Date column in Sales?

A.DateID
B.Date
C.FullDate
D.DateKey
AnswerD

DateKey is the standard unique identifier for a date dimension, matching the granularity of the Sales date column without time.

Why this answer

The correct answer is A: DateKey. In a star schema, the dimension table should have a unique key that matches the fact table's foreign key. The DateKey column is typically an integer or date without time, ensuring a one-to-many relationship.

Option B (FullDate) might include time, causing granularity mismatch. Option C (Date) could work if unique, but DateKey is standard. Option D (DateID) is also plausible but less common; DateKey is the best practice.

Full explanation →
234
Multi-Selecteasy

Which TWO of the following are valid data source types for Power BI?

Select 2 answers
A.Azure SQL Database
B.SharePoint Online List
C.JSON file
D.MongoDB
E.Oracle database
AnswersA, B

Power BI supports Azure SQL Database as a data source.

Why this answer

Azure SQL Database is a supported data source in Power BI, allowing direct import or DirectQuery connectivity via the SQL Server connector. This enables real-time or scheduled data refresh from a cloud-based relational database, leveraging T-SQL queries for data transformation.

Exam trap

The trap here is that candidates may confuse 'data source types' with 'data formats' or 'connectors,' leading them to select JSON file (a format) or MongoDB (a non-native connector) instead of recognizing that only officially listed connectors like Azure SQL Database and SharePoint Online List qualify as valid data source types in the Power BI interface.

Full explanation →
235
Matchingmedium

Match each data connectivity mode to its description.

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

Concepts
Matches

Data is copied into Power BI

Queries are sent to the source database

Connects to a published dataset or Analysis Services

Combines Import and DirectQuery sources

Acts as Import or DirectQuery depending on context

Why these pairings

These modes determine how data is accessed in Power BI.

Full explanation →
236
MCQeasy

You are a Power BI administrator. You need to prevent users from exporting underlying data from reports. Which tenant setting should you disable?

A.'Export data'
B.'Export reports as PowerPoint presentations'
C.'Export reports as PDF files'
D.'Export reports as MHTML files'
AnswerA

This setting controls exporting underlying data.

Why this answer

Option A is correct because 'Export data' controls the ability to export underlying data. Option B is wrong because 'Export reports as PowerPoint' is for exporting the report itself. Option C is wrong because 'Export reports as PDF' is for static exports.

Option D is wrong because 'Export reports as MHTML' is also for report export.

Full explanation →
237
MCQhard

You are designing a Power BI semantic model for a retail company. The model includes a Sales table (50 million rows) and a Product table (10,000 rows). You need to create a measure that calculates the average sales amount per product category. The Product table has a column 'Category' with 20 distinct values. To optimize performance, what should you do?

A.Add a calculated column to Sales that looks up the category using RELATED.
B.Summarize the Sales table to the category level in Power Query.
C.Create a separate calculated table for categories and link it to Sales.
D.Create a relationship between Sales and Product on ProductID, and use Product[Category] in the measure.
AnswerD

This leverages the star schema and efficient query plans.

Why this answer

Option A is correct because marking the Product table as a dimension table with 'Category' as a column allows for efficient aggregations. Option B is wrong because a calculated column in Sales would increase model size. Option C is wrong because a calculated category table would be redundant.

Option D is wrong because summarizing the Sales table loses granularity.

Full explanation →
238
MCQhard

Refer to the exhibit. You have a DAX measure that calculates year-over-year sales growth. When you add this measure to a table visual with Year and Month, some rows show blank values. What is the most likely cause?

A.The measure cannot be used at the month level because SAMEPERIODLASTYEAR only works at year level
B.The measure is trying to divide by zero for months with no sales in the previous year
C.The relationship between Sales and Calendar is inactive
D.The Calendar table does not have a continuous date range, causing SAMEPERIODLASTYEAR to return blank for some months
AnswerD

SAMEPERIODLASTYEAR requires a contiguous set of dates; missing dates cause blank.

Why this answer

Option B is correct because SAMEPERIODLASTYEAR requires a contiguous date range; missing dates in the Calendar table cause blank returns. Option A is wrong because DIVIDE handles division by zero. Option C is wrong because the measure uses SUM, not a relationship issue.

Option D is wrong because the measure works at month granularity.

Full explanation →
239
MCQeasy

A company has a Power BI semantic model with a table named 'Sales' that contains columns: OrderDate, ShipDate, Quantity, and Revenue. The company wants to create a measure that calculates the total revenue for orders shipped within 7 days of the order date. Which DAX expression should be used?

A.CALCULATE(SUM(Sales[Revenue]), DATEDIFF(Sales[OrderDate], Sales[ShipDate], DAY) <= 7)
B.SUMX(FILTER(Sales, Sales[ShipDate] - Sales[OrderDate] <= 7), Sales[Revenue])
C.CALCULATE(SUM(Sales[Revenue]), DATEDIFF(Sales[OrderDate], Sales[ShipDate], DAY) <= 7)
D.CALCULATE(SUM(Sales[Revenue]), Sales[ShipDate] - Sales[OrderDate] <= 7)
AnswerA

This correctly uses CALCULATE with a filter that uses DATEDIFF to compare each row's dates.

Why this answer

Option A is correct because it uses CALCULATE to modify the filter context, applying a filter condition that uses DATEDIFF to compute the number of days between OrderDate and ShipDate. The condition `<= 7` correctly identifies orders shipped within 7 days, and SUM aggregates the Revenue column under that filtered context.

Exam trap

The trap here is that candidates often assume direct date subtraction works the same in DAX as in Excel or SQL, but DAX treats date subtraction as a datetime operation, not a simple day count, leading to incorrect results or errors.

How to eliminate wrong answers

Option B is wrong because it uses a direct subtraction `Sales[ShipDate] - Sales[OrderDate]`, which in DAX does not return a number of days but rather a date/time value (the difference in days as a decimal), leading to incorrect or unexpected results. Option C is wrong because it is syntactically identical to Option A but is listed as a separate answer; the question expects the correct expression, and Option C is a duplicate of A, not a distinct wrong answer. Option D is wrong because it uses direct subtraction `Sales[ShipDate] - Sales[OrderDate] <= 7`, which in DAX does not evaluate as a day count comparison; it compares a date/time value to the number 7, which is invalid and will cause an error or incorrect filtering.

Full explanation →
240
MCQmedium

You receive a Power Query error: 'Expression.Error: The key didn't match any rows in the table.' This occurs when merging two queries. What is the most likely cause?

A.The join columns have different data types.
B.The second table is empty due to a permission issue.
C.The join columns contain duplicate values.
D.The join column in the first table contains values that do not exist in the second table.
AnswerD

The error 'key didn't match any rows' means the merge operation found no matching rows for some keys.

Why this answer

Option D is correct because the error 'The key didn't match any rows in the table' occurs during a merge operation when Power Query attempts to find a matching value from the first table's join column in the second table's join column, but no match exists. This is a standard behavior for inner joins or left outer joins where the lookup fails, and it typically indicates that the first table contains values absent in the second table.

Exam trap

Microsoft often tests the misconception that this error is caused by data type mismatches or duplicate values, but the actual cause is a missing key in the lookup table, which is a fundamental concept in Power Query merge operations.

How to eliminate wrong answers

Option A is wrong because different data types in join columns would cause a type mismatch error (e.g., 'We cannot convert the value...'), not a key-matching error; Power Query automatically attempts type coercion during merge, but if it fails, it raises a different error. Option B is wrong because an empty second table due to permission issues would produce a different error, such as a data source access error or a 'Table is empty' warning, not a key-matching error; the merge operation would still attempt to match keys, but if the table is empty, no rows exist to match, leading to a different behavior (e.g., no rows returned) rather than this specific error. Option C is wrong because duplicate values in join columns are allowed in Power Query merges; they result in a many-to-many or one-to-many relationship, not a key-matching error, and the merge will still succeed by creating multiple matches.

Full explanation →
241
MCQmedium

You are a Power BI administrator. A user reports that they cannot see a specific dataset in the Power BI service, even though they have been assigned the 'Contributor' role on the workspace containing that dataset. The dataset was created by another user. What is most likely the cause?

A.The user needs 'Build' permission on the dataset.
B.The user's Power BI license is insufficient.
C.The dataset is published as an app and the user has not installed the app.
D.The user needs to be assigned the 'Viewer' role on the workspace.
AnswerA

Build permission allows users to view and use datasets created by others.

Why this answer

The Contributor role does not include the ability to view datasets created by others unless those datasets are shared or the user has Build permission. Option B is correct because Build permission is required to view datasets that are not owned by the user. Option A is wrong because Viewer role is not needed for viewing datasets; Contributor already has higher access.

Option C is wrong because the dataset was created in the same workspace, not in a separate app. Option D is wrong because the user is already a workspace member; no additional licensing is needed for viewing.

Full explanation →
242
MCQhard

Refer to the exhibit. An Azure Policy is applied to your subscription. What is the effect of this policy on Power BI workspaces?

A.It denies creation or update of workspaces assigned to Premium capacity.
B.It denies creation of any new Power BI workspace.
C.It denies creation of workspaces that are not Premium.
D.It allows workspaces with Premium per user (PPU) SKU.
AnswerA

The deny effect prevents actions on Premium workspaces.

Why this answer

Option C is correct because the policy denies creation or update of workspaces with SKU 'Premium'. Option A is wrong because it denies Premium, not non-Premium. Option B is wrong because it denies creation of Premium workspaces, not all.

Option D is wrong because it applies to Premium, not premium per user.

Full explanation →
243
MCQeasy

A company has a Power BI dataset that contains a date table with columns: Date, Year, Month, Quarter, Day. The data model also includes a sales fact table with a SalesDate column. To enable time intelligence functions like TOTALYTD, what is the minimum requirement for the relationship between these tables?

A.Create a calculated column in the sales table to extract the date part and relate it to the date table.
B.Create a one-to-many relationship from the date table to the sales table and mark the date table as a date table.
C.Create a many-to-many relationship between the date table and the sales table.
D.Create a one-to-many relationship from the sales table to the date table with bidirectional cross-filtering.
AnswerB

This is the standard requirement for time intelligence.

Why this answer

Option B is correct because time intelligence functions like TOTALYTD require a properly configured date table marked as a date table, with a one-to-many relationship from the date table to the sales fact table. This ensures that the date table provides a continuous, unique set of dates that Power BI can use for time-based calculations, and marking it as a date table enables the engine to recognize it as the primary date dimension for time intelligence.

Exam trap

The trap here is that candidates often think any relationship between a date table and a fact table is sufficient, but they overlook the critical step of marking the date table as a date table, which is mandatory for time intelligence functions to work correctly.

How to eliminate wrong answers

Option A is wrong because creating a calculated column in the sales table to extract the date part is unnecessary and does not establish the required relationship; time intelligence functions rely on a dedicated date table with a marked date column, not on derived columns in the fact table. Option C is wrong because a many-to-many relationship between the date table and sales table would violate the requirement that the date table must have unique dates (one side) to support time intelligence, and it would introduce ambiguity in filter propagation. Option D is wrong because a one-to-many relationship from the sales table to the date table reverses the correct direction; the date table must be on the one side and the sales table on the many side, and bidirectional cross-filtering is not required for time intelligence functions.

Full explanation →
244
Multi-Selectmedium

Which TWO actions can you take to improve the performance of a Power BI report that uses a large dataset?

Select 2 answers
A.Use multiple columns in slicers for more granular filtering.
B.Use aggregations to pre-summarize data at higher levels.
C.Create complex calculated measures that use many nested functions.
D.Reduce the number of visuals on a page.
E.Switch from Import mode to DirectQuery mode.
AnswersB, D

Aggregations reduce the data volume queried.

Why this answer

Options A and D are correct. A: Reducing the number of visuals lowers processing load. D: Using aggregations pre-summarizes data.

B is wrong because using multiple columns in slicers increases cardinality. C is wrong because DirectQuery may slow performance. E is wrong because complex measures can be resource-intensive.

Full explanation →
245
MCQmedium

You are designing a Power BI semantic model that uses a large fact table from Azure SQL Database. The table includes a date column. You need to ensure that the model supports time intelligence functions like TOTALYTD and SAMEPERIODLASTYEAR. What is the recommended approach?

A.Use the 'Add Calendar' function in Power Query and rely on auto-date/time.
B.Use DirectQuery mode and rely on the SQL Server date functions.
C.Use the built-in date hierarchy from the fact table's date column.
D.Create a separate date table and mark it as a date table in the model.
AnswerD

Time intelligence functions require a continuous date table marked as a date table to work correctly.

Why this answer

Option D is correct because time intelligence functions like TOTALYTD and SAMEPERIODLASTYEAR require a separate date table with a contiguous date range marked as the date table in the model. This ensures that DAX can correctly calculate time-based aggregations across all dates, even if the fact table has gaps or missing dates. Without a marked date table, these functions may return incorrect or blank results.

Exam trap

The trap here is that candidates often think auto-date/time or the built-in date hierarchy is sufficient, but Microsoft explicitly recommends creating and marking a separate date table for reliable time intelligence, especially when using large fact tables with non-contiguous dates.

How to eliminate wrong answers

Option A is wrong because the 'Add Calendar' function in Power Query creates a date table but does not automatically mark it as a date table in the model; you must still manually mark it, and relying on auto-date/time disables the use of explicit date tables, which is required for robust time intelligence. Option B is wrong because DirectQuery mode does not support DAX time intelligence functions like TOTALYTD and SAMEPERIODLASTYEAR; these functions require a local date table in the model, not SQL Server date functions. Option C is wrong because using the built-in date hierarchy from the fact table's date column relies on auto-date/time, which creates hidden date tables but does not allow you to mark a custom date table, leading to potential issues with non-contiguous dates and incorrect time intelligence calculations.

Full explanation →
246
MCQmedium

You have a Power BI report that uses a slicer to filter data by year. You want the slicer to show only years that have data, but currently it shows all years from 2000 to 2030. What is the most likely cause?

A.The slicer is using a calculated column.
B.The year field is from a disconnected table.
C.The slicer is set to 'Single select' mode.
D.The data model uses a star schema.
AnswerB

A disconnected table will show all values regardless of data.

Why this answer

If the slicer field is from a disconnected date table or the relationship is not filtering correctly, the slicer shows all values. The solution is to use a date table related to the fact table.

Full explanation →
247
MCQhard

You are a Power BI consultant for a logistics company. The company has a semantic model with a 'Shipments' fact table (containing 'ShipmentID', 'Date', 'OriginCity', 'DestinationCity', 'Weight', 'Cost') and 'City' dimension table (with 'City', 'Region', 'Country'). The company wants a report that displays a map visual with bubbles sized by total shipment weight, and a slicer to select a region. Additionally, they want to be able to click on a bubble (city) and see a table of shipments from that city. You have implemented a map visual using the 'City' field and a table visual. When you click on a bubble, the table does not filter to show only shipments from that city. You have confirmed that cross-filtering is enabled. What is the most likely cause?

A.The map visual does not have a legend field, so clicking does not generate a filter.
B.The table visual has a filter that prevents cross-filtering.
C.The relationship between Shipments and City is based on OriginCity, but the table shows DestinationCity, so the filter does not apply.
D.The region slicer is interfering with the cross-filtering.
AnswerC

The filter from the map applies to the City dimension, but the table uses a different field (DestinationCity) that is not related to the same City table.

Why this answer

The map visual uses the 'City' field from the City dimension table. When you click a bubble, it sends a filter on the City table. However, the table visual likely uses fields from the Shipments table (e.g., ShipmentID, DestinationCity).

If the relationship between Shipments and City is based on OriginCity, and the table is showing DestinationCity, the filter from the map (on City) may not propagate correctly because the relationship is on OriginCity, not DestinationCity. Option D is correct. Option A is incorrect because the slicer is not the issue.

Option B is incorrect because the map should have a legend if needed. Option C is incorrect because the table might have many rows but filtering should work.

Full explanation →
248
MCQeasy

You are importing data from a CSV file that contains a column 'OrderDate' with values in the format 'YYYY-MM-DD'. Power Query automatically detects the data type as Date. You need to ensure that the data type remains Date even if the source file later changes the date format to 'MM/DD/YYYY'. What should you do?

A.Split the column into year, month, day and then combine
B.Use the 'Using Locale' transformation
C.Set the data type to Date using the 'Change Type' step in Power Query
D.Change the regional settings of the Power Query editor
AnswerC

Explicit type conversion will handle different formats.

Why this answer

Option A is correct because setting the data type explicitly in Power Query forces conversion regardless of source format. Option B is wrong because changing source locale doesn't fix format changes. Option C is wrong because using sample file doesn't enforce type.

Option D is wrong because split column is unnecessary.

Full explanation →
249
MCQeasy

You have a Power BI report that includes a slicer for product category. Users want to select multiple categories and see the combined data. The slicer currently allows only single selection. What should you change?

A.Change the slicer style to dropdown.
B.Use the sync slicer pane to replicate the slicer on other pages.
C.Add a second slicer for product category.
D.Enable multi-select in the slicer formatting options.
AnswerD

Multi-select allows selection of multiple items.

Why this answer

Option B is correct because enabling multi-select on the slicer allows users to select multiple items. Option A is wrong because the sync slicer pane is for syncing slicers across pages. Option C is wrong because changing the slicer to dropdown does not enable multi-select by default.

Option D is wrong because adding a second slicer would not solve the single-select limitation.

Full explanation →
250
MCQeasy

When creating a many-to-many relationship between two tables, what is a common approach to model this in Power BI?

A.Use the CROSSJOIN DAX function in calculated tables.
B.Merge both tables into a single table.
C.Introduce a bridge table that contains the unique combinations.
D.Create a direct many-to-many relationship in the model.
AnswerC

Bridge table creates two one-to-many relationships.

Why this answer

Option B is correct because a bridge table resolves many-to-many relationships by creating two one-to-many relationships. Option A is wrong because a single many-to-many relationship without a bridge table is not supported directly. Option C is wrong because CROSSJOIN creates a Cartesian product, which is not correct.

Option D is wrong because merging tables into one removes the relationship structure.

Full explanation →
251
MCQeasy

Refer to the exhibit. You are reviewing a DAX expression used in a Power BI measure. You need to ensure that only users in the 'West' region see data for that region. Which approach should you use?

A.Implement row-level security (RLS) in the dataset with a role filter.
B.Use the CALCULATE function with a filter on the report page.
C.Modify the measure to include a conditional statement that checks the user's email.
D.Create a calculated column with the same logic.
AnswerA

Correct. RLS restricts data access at the row level.

Why this answer

Option C is correct because the DAX expression is a measure that calculates the sum for the 'West' region, but it does not restrict data for other users. To enforce security, you need to implement row-level security (RLS) by adding a filter in the dataset roles. Option A is wrong because you cannot restrict the measure to specific users directly.

Option B is wrong because the measure itself calculates for West only, but RLS is needed for security. Option D is wrong because the measure is already specific to West.

Full explanation →
252
Multi-Selectmedium

Which TWO options are valid methods to combine multiple tables in Power Query?

Select 2 answers
A.Join
B.Concatenate
C.Merge
D.Union
E.Append
AnswersC, E

Merge combines tables horizontally based on a key.

Why this answer

Option C (Merge) is correct because Merge in Power Query performs a join-like operation that combines columns from two tables based on a matching key, similar to SQL JOINs. Option E (Append) is correct because Append stacks rows from multiple tables with the same columns, akin to SQL UNION ALL. Both are native Power Query operations for combining tables.

Exam trap

The trap here is that candidates confuse SQL terminology (Join, Union) with Power Query's specific functions (Merge, Append), leading them to select the generic terms instead of the correct Power Query operations.

Full explanation →
253
Multi-Selecthard

Which THREE of the following are valid ways to model a many-to-many relationship between tables in Power BI? (Select three.)

Select 3 answers
A.Use the LOOKUPVALUE function in a measure.
B.Add a calculated column to one table to create a unique key.
C.Create two one-to-many relationships and use USERELATIONSHIP in measures.
D.Use a bridge table with a many-to-many cardinality.
E.Set the relationship cross filter direction to Both with Many-to-Many cardinality.
AnswersC, D, E

USERELATIONSHIP activates an inactive relationship for specific calculations.

Why this answer

Options A, B, and D are valid techniques. Using a bridge table (A) is common. Using CROSSFILTER with Many-to-Many cardinality (B) is a built-in feature.

Using the USERELATIONSHIP function (D) can handle multiple relationships. Option C is incorrect because calculated columns do not create relationships. Option E is incorrect because lookup functions are for one-to-many.

Full explanation →
254
Multi-Selecteasy

Which TWO of the following are valid DAX functions for modifying filter context within a measure? (Select two.)

Select 2 answers
A.FILTER
B.CALCULATE
C.VALUES
D.SUM
E.ALL
AnswersA, B

FILTER returns a table that can be used as a filter in CALCULATE.

Why this answer

Options A and D are correct. CALCULATE is the primary function to modify filter context (A). FILTER is used as a table function inside CALCULATE (D).

Option B is incorrect because SUM is an aggregation function, not filter modification. Option C is incorrect because ALL is a table function used to remove filters, but it is not a function that modifies filter context by itself; it is used inside CALCULATE. However, ALL is often used to clear filters, so it could be considered a filter modifier.

The question expects CALCULATE and FILTER as direct answers.

Full explanation →
255
MCQmedium

You publish a Power BI report to a workspace that uses an organizational app. After updating the report, you want users to see the changes immediately without having to reinstall the app. What should you do?

A.Delete and recreate the app from the workspace.
B.Republish the report from Power BI Desktop.
C.Ask users to refresh their browser cache.
D.Update the app in the workspace by selecting 'Update app'.
AnswerD

Updating the app publishes changes to all users.

Why this answer

Option D is correct because updating the app in the workspace by selecting 'Update app' publishes the latest version of the report (and any other content) to the existing app without requiring users to reinstall. The app is a container that points to the workspace content; updating it refreshes that pointer, making changes immediately available to users who already have the app installed.

Exam trap

The trap here is that candidates confuse updating the workspace content (e.g., republishing a report) with updating the app itself, assuming changes automatically propagate to the app without an explicit 'Update app' step.

How to eliminate wrong answers

Option A is wrong because deleting and recreating the app forces users to reinstall the app from AppSource, causing unnecessary disruption and potential loss of app permissions or custom settings. Option B is wrong because republishing the report from Power BI Desktop only updates the report in the workspace, not the app itself; users would still see the old version until the app is updated. Option C is wrong because refreshing the browser cache does not affect the app's published content; the app is a separate deployment artifact that must be explicitly updated to reflect workspace changes.

Full explanation →
256
MCQmedium

A company has a fact table 'Sales' with a column 'SalesAmount' and a dimension table 'Date'. They want to create a measure that calculates the running total of sales over time. The Date table is marked as a date table. Which DAX expression is correct?

A.Running Total = CALCULATE(SUM(Sales[SalesAmount]), FILTER(ALL(Date), Date[Date] <= EARLIER(Date[Date])))
B.Running Total = CALCULATE(SUM(Sales[SalesAmount]), DATESYTD(Date[Date]))
C.Running Total = TOTALYTD(SUM(Sales[SalesAmount]), Date[Date])
D.Running Total = SUMX(Sales, Sales[SalesAmount])
AnswerB

DATESYTD returns a set of dates from the start of the year to the current context date, which creates a running total within the year. For a full running total across years, one would use DATESBETWEEN or a filter.

Why this answer

Option B is correct because DATESYTD returns a set of dates from the start of the year to the latest date in the current filter context, and when wrapped in CALCULATE, it correctly computes a year-to-date running total. Since the Date table is marked as a date table, DATESYTD works seamlessly with the time intelligence functions in DAX.

Exam trap

The trap here is that candidates often confuse DATESYTD with a general running total function, but DATESYTD only works within a single year, so the question's wording 'running total over time' might mislead test-takers into thinking any time intelligence function will work, when in fact a proper running total requires a FILTER with ALL or ALLSELECTED.

How to eliminate wrong answers

Option A is wrong because EARLIER is used in calculated columns to reference an earlier row context, not in measures; in a measure, there is no row context, so EARLIER would cause an error or incorrect results. Option C is wrong because TOTALYTD is a time intelligence function that expects a date column reference as the second argument, but the syntax shown is correct; however, the question asks for a running total over time, not specifically year-to-date, and TOTALYTD would only compute YTD, not a general running total across all dates. Option D is wrong because SUMX(Sales, Sales[SalesAmount]) simply sums the SalesAmount column row by row, which is equivalent to SUM(Sales[SalesAmount]) and does not create any running total or time-based calculation.

Full explanation →
257
MCQhard

You are designing a Power BI data model for sales analysis. The source data includes a table with columns: OrderID, CustomerID, ProductID, OrderDate, Quantity, and UnitPrice. You need to support time intelligence calculations (e.g., year-to-date sales) and avoid creating a separate date table. What should you do?

A.Use the CALENDAR function in a calculated table to create a date table and mark it as a date table.
B.Enable the auto date/time option in Power BI Desktop settings.
C.Use the OrderDate column directly in time intelligence measures.
D.Create a calculated column for fiscal year using the OrderDate column.
AnswerA

A proper date table marked as a date table is required for time intelligence functions like TOTALYTD.

Why this answer

Option A is correct because time intelligence functions in Power BI (e.g., TOTALYTD, SAMEPERIODLASTYEAR) require a contiguous, continuous date table marked as a date table. Using the CALENDAR function creates a calculated date table that meets this requirement, enabling accurate year-to-date and other time-based calculations without relying on the auto date/time feature or direct column usage.

Exam trap

The trap here is that candidates often think the auto date/time option is sufficient for time intelligence, but it only creates hidden tables that cannot be marked as a date table, causing time intelligence functions to fail or return incorrect results.

How to eliminate wrong answers

Option B is wrong because enabling the auto date/time option creates hidden date tables that are not user-visible and cannot be marked as a date table, which prevents proper use of time intelligence functions like TOTALYTD. Option C is wrong because using the OrderDate column directly in time intelligence measures will fail or produce incorrect results, as these functions require a separate, continuous date table with no gaps. Option D is wrong because creating a calculated column for fiscal year does not provide the continuous date table needed for time intelligence; it only adds a column without enabling functions like TOTALYTD.

Full explanation →
258
Multi-Selecthard

Which THREE steps should you perform to deploy a Power BI solution from development to production using deployment pipelines?

Select 3 answers
A.Create a new workspace manually in production.
B.Set up deployment pipeline rules to modify parameters (e.g., database name).
C.Assign Power BI Pro licenses to all developers.
D.Deploy content from development to test, then to production.
E.Create a development workspace and add content.
AnswersB, D, E

Rules automate configuration changes.

Why this answer

Option B is correct because deployment pipeline rules allow you to modify dataset parameters (e.g., database server or database name) when content moves between pipeline stages, ensuring each stage connects to the appropriate data source without manual reconfiguration. This is a core feature of Power BI deployment pipelines to maintain environment-specific settings.

Exam trap

The trap here is that candidates confuse general prerequisites (like licensing or manual workspace creation) with the specific steps required to use deployment pipelines, leading them to select options that are necessary for Power BI overall but not part of the pipeline deployment workflow.

Full explanation →
259
MCQhard

You are a data analyst for a healthcare organization. You have a Power BI dataset that imports patient data from an on-premises SQL Server database. The database contains personally identifiable information (PII). You need to ensure that all PII columns are obfuscated when the data is loaded into Power BI. You have already masked the columns in the source database using dynamic data masking. However, when you refresh the dataset in Power BI, the masked values are not appearing. What should you do?

A.In Power BI Desktop, define row-level security roles to restrict PII columns.
B.Apply data masking in Power Query using Text.Start or Text.End functions.
C.Install the on-premises data gateway and configure it to use the service account.
D.In the data source settings, use a SQL Server account that has been granted the UNMASK permission to see masked data, but actually you need an account WITHOUT UNMASK to see masked data. Actually, correct: Configure the data source connection to use a user without the UNMASK permission so that dynamic data masking applies.
AnswerD

Correct. The account used by Power BI must not have UNMASK to see masked data.

Why this answer

Option D is correct because dynamic data masking (DDM) in SQL Server works by returning masked values to users who lack the UNMASK permission. When Power BI connects to the database using a SQL Server account without UNMASK, DDM automatically obfuscates the PII columns in the query results, so the masked data is loaded into Power BI. The current issue is that the connection account likely has UNMASK permission, which reveals the original unmasked data instead of the masked values.

Exam trap

The trap here is that candidates often assume dynamic data masking is automatically applied to all connections, but in reality it only applies when the connecting user does not have the UNMASK permission, so the correct fix is to use a user without UNMASK rather than one with it.

How to eliminate wrong answers

Option A is wrong because row-level security (RLS) in Power BI restricts which rows a user can see, not which columns are obfuscated; it cannot mask or hide specific column values. Option B is wrong because applying data masking in Power Query using Text.Start or Text.End functions would require manual transformation logic and would not leverage the existing SQL Server dynamic data masking, which is the intended and more secure approach. Option C is wrong because installing the on-premises data gateway is necessary for connecting to an on-premises SQL Server, but it does not affect whether dynamic data masking applies; the masking behavior depends solely on the database user's permissions, not the gateway configuration.

Full explanation →
260
MCQeasy

You have the above calculated column in a Power BI model. Some rows show blank values for Profit Margin even though Profit and SalesAmount are not blank. What is the most likely cause?

A.The calculated column syntax is incorrect
B.The columns are not numeric
C.The DIVIDE function cannot handle large numbers
D.SalesAmount is zero for those rows
AnswerD

DIVIDE returns blank when denominator is zero.

Why this answer

Option A is correct because DIVIDE returns blank if the denominator is zero or blank. If SalesAmount is zero, the division is undefined. Option B is wrong because DIVIDE handles division by zero gracefully.

Option C is wrong because data types are not an issue. Option D is wrong because the syntax is correct.

Full explanation →
261
MCQhard

A Power BI administrator reviews the JSON configuration for a dataset named SalesDataset. The dataset is deployed to a Premium capacity workspace. The data source is an on-premises SQL Server. The administrator notices that the dataset has never refreshed successfully. Based on the exhibit, what is the most likely cause of the refresh failure?

A.The refresh schedule specifies a frequency of Weekly, but the time is in UTC and not adjusted for the local time zone
B.The dataset uses Integrated Security in the connection string, which is not supported for scheduled refresh
C.The dataset's defaultMode is set to Push, which does not support scheduled refresh
D.The dataset is in a Premium capacity workspace, which does not support scheduled refresh for on-premises data sources
AnswerC

Push datasets cannot be refreshed; they must be updated via the Push API.

Why this answer

Option C is correct because when a dataset's defaultMode is set to 'Push', it is designed to receive data only via the Push API and does not support scheduled refresh. Since the dataset has never refreshed successfully and the JSON configuration shows defaultMode as Push, the scheduled refresh will always fail regardless of the gateway or data source configuration.

Exam trap

The trap here is that candidates often focus on connectivity issues like time zones or authentication, overlooking the fundamental dataset mode property that disables scheduled refresh entirely.

How to eliminate wrong answers

Option A is wrong because while UTC time zone differences can cause refresh timing issues, they would not prevent the refresh from ever succeeding; the refresh would still run at the scheduled UTC time. Option B is wrong because Integrated Security (Windows authentication) is supported for scheduled refresh when a proper on-premises data gateway is configured and the user's credentials are stored securely. Option D is wrong because Premium capacity workspaces fully support scheduled refresh for on-premises data sources via an on-premises data gateway; the capacity tier does not impose such a restriction.

Full explanation →
262
MCQhard

A Power BI admin receives a support ticket that a user cannot see any data in a report that uses row-level security (RLS). The report is based on a dataset with a single table 'Sales' and RLS roles defined. The user is assigned to the role 'SalesManager' which filters Sales[Region] = 'West'. The dataset uses Import mode. The user can see the report but all visuals show blank. What is the most likely cause?

A.The RLS filter removes all rows for the user's role.
B.The user does not have permission to view the report page.
C.The user is viewing a dashboard tile instead of the report.
D.The dataset was refreshed using an RLS bypass account.
AnswerA

If Sales[Region] = 'West' returns no rows, visuals will be blank.

Why this answer

Option D is correct because RLS in Import mode filters at the dataset level; if the user's role filters out all data (e.g., no rows match 'West'), visuals will appear blank. Option A is wrong because RLS does not affect the report page layout. Option B is wrong because RLS is applied regardless of dashboard tiles.

Option C is wrong because RLS is applied after data refresh, so the data load includes all rows but RLS filters query results.

Full explanation →
263
Multi-Selecthard

A Power BI administrator needs to prevent users from creating new workspaces, but allow existing workspaces to continue functioning. Which two settings should be configured? (Choose two.)

Select 2 answers
A.Set the 'Maximum number of workspaces a user can create' to 0 for all security groups.
B.In the Power BI admin portal, under 'Workspace settings', disable 'Create workspaces' for all users.
C.Remove the 'Create workspace' button from the Power BI navigation pane using custom branding.
D.Enable 'Block users from creating workspaces' in the Power BI admin portal.
E.In the Power BI admin portal, disable 'Use workspaces' for all users.
AnswersB, D

This setting prevents users from creating new workspaces.

Why this answer

Option A (disable 'Create workspaces' for all users) and Option D (enable 'Block users from creating workspaces' in the admin portal) are correct. Option A is a tenant setting to disable workspace creation. Option D is the actual admin portal setting.

Option B is wrong because disabling 'Use workspaces' would break existing workspaces. Option C is wrong because setting a group policy is not the correct approach. Option E is wrong because removing workspace creation from the admin portal is not a granular setting.

Full explanation →
264
MCQmedium

A company uses Power BI Premium per capacity. A report developer needs to share a report with external users who do not have Power BI licenses. The report uses a live connection to an Azure Analysis Services model. What should the admin configure to allow external access?

A.Enable Publish to web for the report.
B.Configure Bring Your Own Tenant (BYOT) with Azure B2B.
C.Configure Azure B2B guest users in the same tenant.
D.Share the report directly with external email addresses.
AnswerB

BYOT allows external users to access content using their own organization's Power BI licenses.

Why this answer

Option B is correct because Bring Your Own Tenant (BYOT) with Azure B2B allows external users to access content via their own organization's tenant. Option A is wrong because guest users in the same tenant require licenses. Option C is wrong because Publish to web makes data public.

Option D is wrong because sharing requires internal licenses.

Full explanation →
265
MCQmedium

You are modeling data from an Azure SQL Database into Power BI. The source table 'Sales' contains 10 million rows. You need to ensure that the data model supports fast query performance for a report that shows sales by month and product category. The report uses a slicer for year. What is the best practice for improving performance?

A.Disable the auto-date/time feature.
B.Increase the data load frequency to every 15 minutes.
C.Use DirectQuery mode to query the source database directly.
D.Create an aggregate table in Power BI that pre-aggregates sales by month and product category.
AnswerD

Aggregations improve query performance by reducing data volume.

Why this answer

Option D is correct because creating an aggregate table in Power BI that pre-aggregates sales by month and product category drastically reduces the number of rows the report must scan, from 10 million to a much smaller set of aggregated rows. This enables fast query performance for the slicer and visual-level filters, as Power BI can leverage the aggregate table via its aggregation feature, which automatically redirects queries to the pre-summarized data when possible.

Exam trap

The trap here is that candidates often confuse DirectQuery (option C) as a performance optimization for large data volumes, but in reality, DirectQuery offloads processing to the source and can be slower for aggregated reports, whereas pre-aggregating in Power BI (option D) is the correct approach for fast in-memory query performance.

How to eliminate wrong answers

Option A is wrong because disabling the auto-date/time feature reduces model size and improves load times, but it does not address the core performance bottleneck of scanning 10 million rows for every report interaction; it is a general best practice, not a solution for large-table aggregation. Option B is wrong because increasing data load frequency to every 15 minutes improves data freshness but has no impact on query performance against the existing 10 million rows; it may even degrade performance by causing more frequent refreshes. Option C is wrong because DirectQuery mode sends queries directly to the Azure SQL Database, which would still require scanning 10 million rows on each interaction, and it introduces network latency and dependency on source database performance, often resulting in slower report responsiveness compared to an in-memory aggregated model.

Full explanation →
266
Multi-Selectmedium

You are reviewing a Power Query query that combines data from multiple CSV files in a folder. The query uses the 'Combine Files' function. Which TWO actions can you take to improve the performance of this query?

Select 2 answers
A.Load all data to the data model without filtering.
B.Disable the 'Promote Headers' step if the headers are not needed.
C.Increase the scheduled refresh frequency.
D.Filter the folder to include only relevant files before combining.
E.Enable 'Fast Combine' in the Power Query options.
AnswersB, D

Avoids unnecessary processing.

Why this answer

Option B is correct because disabling the 'Promote Headers' step reduces the number of transformations applied to each file during the combine operation. When headers are not needed, skipping this step avoids an extra row promotion and type detection pass, which can significantly reduce query execution time, especially when combining many files.

Exam trap

Microsoft often tests the misconception that increasing refresh frequency or enabling privacy-level settings like 'Fast Combine' improves query performance, when in fact they address different concerns (scheduling and data privacy, respectively).

Full explanation →
267
MCQhard

You are reviewing a Power BI model definition with incremental refresh policy. The Sales table has an incremental refresh policy that refreshes the last 365 days. However, the report shows data for dates beyond 365 days ago. What is the most likely reason?

A.The incremental refresh policy is applied at the partition level instead of the table level
B.Incremental refresh only refreshes the data, it does not remove historical data
C.The incrementalPeriodsOffset should be set to a negative value to include historical data
D.The refresh policy automatically removes data older than the incremental period
AnswerB

Historical data persists unless the policy includes filtering or the data source is filtered.

Why this answer

Option B is correct because incremental refresh policy only affects refresh operations; it does not delete historical data from the model. Data older than 365 days remains in the model unless explicitly removed. Option A is wrong because the policy is defined for the table, not partitions.

Option C is wrong because the policy is set to refresh the last 365 days, not filter. Option D is wrong because incremental refresh does not automatically remove old data; it only refreshes recent data.

Full explanation →
268
MCQmedium

Refer to the exhibit. You are configuring a data source in Power BI Service using a JSON policy. The data source fails to refresh. What is the most likely issue?

A.The service principal does not have permission to the Azure SQL Database.
B.The version value should be "2.0".
C.The JSON is missing the 'dataSource' type.
D.The connection string is missing the database name.
AnswerA

Service principal must be granted access to the database.

Why this answer

Option A is correct because when using a JSON policy with a service principal in Power BI, the service principal must have the necessary permissions (e.g., db_datareader role) on the Azure SQL Database. Without these permissions, the data source will fail to refresh, as Power BI cannot authenticate or access the data. The JSON policy itself may be syntactically valid, but the underlying authentication fails due to insufficient database-level permissions.

Exam trap

The trap here is that candidates assume a syntactically correct JSON policy guarantees a successful connection, but Power BI's data source refresh depends on runtime authentication permissions, not just policy structure.

How to eliminate wrong answers

Option B is wrong because the 'version' value in a JSON policy for Power BI data sources is typically '1.0', not '2.0'; '2.0' is used for other policy types like data masking, not for connection policies. Option C is wrong because the JSON policy does not require a 'dataSource' type; the data source type is defined in the connection string or the gateway configuration, not as a separate JSON field. Option D is wrong because the connection string in the JSON policy already includes the database name (e.g., 'Initial Catalog=AdventureWorks'), so a missing database name is not the issue; the failure is due to authentication permissions, not connection string syntax.

Full explanation →
269
MCQmedium

You connect to a large Azure SQL Database table with over 100 million rows. You need to create a report that shows sales by month for the current year only. Which data reduction technique should you use in Power Query to minimize data load?

A.Import all data and then remove columns that are not needed.
B.In Power Query, apply a date filter on the source query so only current year data is imported.
C.Load all data and filter using a visual-level filter in the report.
D.Use a calculated table in DAX to filter the data.
AnswerB

Query Folding pushes the filter to the database.

Why this answer

Option B is correct because applying a date filter in Power Query at the source query level ensures that only rows from the current year are imported into the Power BI data model. This reduces the data volume from over 100 million rows to a fraction, minimizing memory usage and improving refresh performance. Power Query pushes the filter down to the Azure SQL Database using a WHERE clause in the SQL query, so only the filtered data is transferred over the network.

Exam trap

The trap here is that candidates often assume visual-level filters or DAX calculated tables are sufficient for performance, but they fail to realize that data reduction must occur at the data source or during import to minimize memory and refresh time.

How to eliminate wrong answers

Option A is wrong because importing all 100 million rows and then removing columns still loads the full row count into the data model, wasting memory and bandwidth; column removal does not reduce row volume. Option C is wrong because loading all data and applying a visual-level filter only hides rows in the report, but the entire dataset remains in the model, causing unnecessary memory consumption and slower performance. Option D is wrong because a calculated table in DAX still requires the full table to be loaded first before filtering, negating any data reduction at the import stage.

Full explanation →
270
MCQmedium

You need to create a calculated column that categorizes products based on price: 'Low' (<$10), 'Medium' ($10-$50), 'High' (>$50). Which DAX expression should you use?

A.SWITCH(Product[Price], <10, "Low", <=50, "Medium", "High")
B.LOOKUPVALUE(Category, Product[Price], Product[Price])
C.SWITCH(TRUE(), Product[Price] < 10, "Low", Product[Price] <= 50, "Medium", "High")
D.IF(Product[Price] < 10, "Low", Product[Price] <= 50, "Medium", "High")
AnswerC

Correct use of SWITCH with TRUE() for multiple conditions.

Why this answer

Option A is correct because SWITCH evaluates conditions in order and returns the first match, which is appropriate for this scenario. Option B is wrong because IF cannot handle three categories efficiently. Option C is wrong because the syntax is incorrect (no condition after SWITCH).

Option D is wrong because LOOKUPVALUE is for looking up values in another table, not for conditional logic.

Full explanation →
271
Multi-Selecteasy

You are creating a star schema in Power BI. Which TWO tables are typically dimension tables?

Select 2 answers
A.TransactionDetails
B.Product
C.Date
D.InventoryTransactions
E.Sales
AnswersB, C

Product is a dimension table.

Why this answer

Option B is correct: Date table is a classic dimension. Option D is correct: Product table is a dimension. Option A is wrong because Sales is a fact table.

Option C is wrong because TransactionDetails is typically a fact table. Option E is wrong because InventoryTransactions is a fact table.

Full explanation →
272
MCQmedium

You are building a report for executives to monitor key performance indicators (KPIs) against targets. You have a KPI visual for revenue. The target is stored in a separate table. Which approach should you use to configure the KPI visual correctly?

A.Create a calculated column in the sales table that references the target.
B.Merge the target table into the sales table in Power Query.
C.Use the target column directly from the related table in the KPI visual.
D.Create measures for actual and target, then assign them to the KPI visual.
AnswerD

Measures allow dynamic aggregation and are required for KPI visual.

Why this answer

Option D is correct because the KPI visual requires a single value for actual, a goal, and a trend axis. By creating measures that retrieve the target from the separate table, you can assign them to the KPI visual fields. Option A is wrong because merging tables would denormalize the model unnecessarily.

Option B is wrong because the KPI visual cannot directly use a column from a related table without measures. Option C is wrong because calculated columns are static and not suitable for dynamic targets.

Full explanation →
273
MCQeasy

You have a Power BI report that displays sales data by region. The report includes a map visual showing sales amount by state. You notice that some states are not displayed on the map because the state names in the data do not match the standard names used by Power BI's map visualization. For example, 'California' is correct but 'CA' is not recognized. You need to ensure all states appear correctly. Which action should you take? A. Create a calculated column that maps state abbreviations to full names using a SWITCH statement. B. Change the map visual to a filled map. C. Use the 'Data category' property to set the field to 'State or Province'. D. Add a custom map image. Which option is the best?

A.Use the 'Data category' property to set the field to 'State or Province'
B.Create a calculated column that maps state abbreviations to full names using a SWITCH statement
C.Add a custom map image
D.Change the map visual to a filled map
AnswerB

This corrects the values to be recognized by the map.

Why this answer

Option A is correct because you can create a calculated column that converts abbreviations to full names using a SWITCH or a mapping table. Option B is wrong because a filled map has the same recognition issue. Option C is wrong because setting data category does not change the values.

Option D is wrong because custom map images require additional setup and may not solve the recognition issue.

Full explanation →
274
Multi-Selectmedium

Which TWO of the following are valid ways to enforce row-level security (RLS) on a Power BI dataset? (Choose two.)

Select 2 answers
A.Use Power BI Report Builder to define RLS on paginated reports.
B.Create RLS rules directly in the Power BI service under dataset security.
C.Define roles and role members in Power BI Desktop using DAX filter expressions.
D.Assign users to security groups in Microsoft Entra ID and map those groups to RLS roles in the Power BI service.
E.Configure RLS in the source database when using DirectQuery with single sign-on (SSO).
AnswersC, E

This is the primary method to create RLS in Power BI Desktop.

Why this answer

Options A and C are correct. RLS can be defined in Power BI Desktop using static roles, and in DirectQuery with SSO, RLS can be enforced in the source database. Option B is wrong because RLS is not applied via the Power BI service interface for datasets; it's defined in Desktop.

Option D is wrong because RLS in Power BI is not based on Microsoft Entra ID groups; it's based on roles defined in the model. Option E is wrong because RLS is not configured in Excel.

Full explanation →
275
MCQmedium

You have a Power BI report that displays key performance indicators (KPIs) using a KPI visual. The visual shows a measure 'Current Sales' with a goal of 'Target Sales'. You want to show the status (on track, behind, etc.) based on the difference. You configure the KPI visual with the measure, goal, and trend axis. However, the status indicator does not appear. What should you do? A. Ensure the measure and goal are both numeric and have the same unit. B. Add a trend line to the visual. C. Set the 'Direction' property to 'High is good' or 'Low is good'. D. Use a different visual like a gauge. Which option is the best?

A.Add a trend line to the visual
B.Ensure the measure and goal are both numeric and have the same unit
C.Set the 'Direction' property to 'High is good' or 'Low is good'
D.Use a different visual like a gauge
AnswerC

Direction is required to compute status based on goal.

Why this answer

Option C is correct because the KPI visual requires setting the direction to calculate status. Option A is wrong because units don't need to be same. Option B is wrong because trend line is optional.

Option D is wrong because gauge is an alternative but not a fix for KPI.

Full explanation →
276
MCQmedium

Your Power BI report uses a calculated table to create a date dimension. You need to add a column that shows the fiscal quarter based on a fiscal year starting in July. What DAX expression should you use?

A.Fiscal Quarter = "Q" & FORMAT('Date'[Date], "\QQ")
B.Fiscal Quarter = "Q" & FORMAT('Date'[Date], "Q")
C.Fiscal Quarter = "Q" & FORMAT('Date'[Date], "Q", "en-US", 2025-07-01)
D.Fiscal Quarter = "Q" & QUARTER('Date'[Date])
AnswerC

FORMAT with a fiscal calendar start date returns the fiscal quarter.

Why this answer

Option A is correct because FORMAT with "Q" returns the quarter number, and the shift of 0 accounts for the fiscal year start in July (July=Q1). Option B is wrong because it returns the calendar quarter. Option C is wrong because it uses "\QQ" which is incorrect syntax.

Option D is wrong because it uses QUARTER function which returns calendar quarter.

Full explanation →
277
MCQhard

You are a Power BI administrator for a large enterprise. The company has a Power BI tenant with thousands of workspaces. You need to audit all shared links (shareable links) that have been created across the tenant to identify any that are shared with external users. You also need to revoke any links that were created more than 90 days ago. You want to use a PowerShell script to accomplish this efficiently. The script must output a CSV file with columns: LinkId, WorkspaceName, ReportName, CreatedDate, ExternalSharing. What should you do?

A.Enable Power BI activity logs and query Log Analytics for shareable links.
B.Use the Power BI REST API cmdlet Get-PowerBIShareableLink to retrieve and filter links by CreatedDate, then revoke with Remove-PowerBIShareableLink.
C.Use Microsoft Graph API to audit and manage Power BI shareable links.
D.Use the Power BI admin portal to manually export shareable links.
AnswerB

Power BI REST API provides programmatic access to shareable links.

Why this answer

Option B is correct because the Power BI REST API (via PowerShell) can retrieve shareable links and filter by creation date. Option A is wrong because the admin portal lacks automation. Option C is wrong because Microsoft Graph API does not directly manage Power BI shareable links.

Option D is wrong because Log Analytics does not provide shareable link metadata.

Full explanation →
278
MCQhard

You are preparing data from a CSV file that has inconsistent date formats. Some rows use 'MM/dd/yyyy' and others use 'dd/MM/yyyy'. You need to parse all dates correctly. What is the best approach in Power Query?

A.Use the 'Replace Values' to standardize the date format, then change data type.
B.Use the 'Parse' -> 'Date' transformation with a specific culture.
C.Use the 'Split Column' by delimiter to separate date parts.
D.Use the 'Detect Data Type' feature to automatically identify the format.
AnswerA

This approach can standardize formats before type conversion.

Why this answer

Option A is correct because 'Replace Values' allows you to standardize the inconsistent date strings (e.g., swapping day and month parts) before Power Query attempts to parse them as dates. After replacing the delimiters or reordering parts, you can change the column type to 'Date' using a consistent culture (e.g., 'en-US' for MM/dd/yyyy), ensuring all rows parse correctly regardless of original format.

Exam trap

The trap here is that candidates assume 'Parse' with a culture or 'Detect Data Type' can handle mixed formats, but Power Query requires explicit standardization before parsing when formats are inconsistent within a single column.

How to eliminate wrong answers

Option B is wrong because the 'Parse' -> 'Date' transformation with a specific culture assumes all dates in the column follow that single culture's format; it cannot handle mixed formats like MM/dd/yyyy and dd/MM/yyyy in the same column. Option C is wrong because 'Split Column' by delimiter separates date parts into individual columns (e.g., day, month, year), but it does not resolve which part is day vs. month when the order is inconsistent, requiring additional logic to recombine correctly. Option D is wrong because 'Detect Data Type' only identifies the overall data type (e.g., text or date) and cannot distinguish between multiple date formats within the same column; it would likely fail or produce errors for rows not matching the dominant format.

Full explanation →
279
MCQeasy

You have a Power BI model with a table 'Employees' that includes columns: 'EmployeeID', 'ManagerID', 'Name'. You need to create a hierarchy that shows the reporting structure. What should you do first?

A.Create a self-join relationship from Employees[EmployeeID] to Employees[ManagerID].
B.Merge the Employees table with itself using Merge Queries.
C.Add a calculated column that concatenates EmployeeID and ManagerID.
D.Create a many-to-many relationship between Employees and itself.
AnswerA

Self-join enables parent-child hierarchy.

Why this answer

To create a hierarchy that shows the reporting structure in Power BI, you first need to establish a self-join relationship between the Employees table and itself, linking EmployeeID to ManagerID. This allows Power BI to traverse the parent-child relationship and build a natural hierarchy (e.g., using Parent-Child functions like PATH). Without this relationship, the model cannot understand how employees relate to their managers.

Exam trap

The trap here is that candidates often confuse a self-join relationship (which is a logical model relationship) with a Merge Queries operation (which physically combines tables), leading them to choose Option B instead of A.

How to eliminate wrong answers

Option B is wrong because merging the Employees table with itself using Merge Queries would create a flat, denormalized table, which breaks the recursive nature needed for a hierarchy and is not the standard approach for parent-child structures in Power BI. Option C is wrong because concatenating EmployeeID and ManagerID into a single column does not create a relationship or hierarchy; it merely creates a string that cannot be used for traversal. Option D is wrong because a many-to-many relationship between Employees and itself would imply multiple managers per employee or multiple employees per manager, which is not the typical reporting structure and would violate the intended one-to-many parent-child relationship.

Full explanation →
280
MCQmedium

Your organization uses Power BI in a shared capacity model. A report developer complains that a new report published to a workspace does not appear in the 'My workspace' area. They have the Contributor role on the workspace. What is the most likely cause?

A.The Contributor role does not have permission to publish reports to the workspace.
B.The report was automatically added to 'My workspace' but was deleted by an administrator.
C.Reports published to a workspace do not appear in 'My workspace' unless the user manually saves a copy there.
D.The user does not have a Power BI Pro license.
AnswerC

Correct. Reports published to a workspace are stored in that workspace, not in 'My workspace'.

Why this answer

Option A is correct because reports published to a workspace are stored in that workspace, not in 'My workspace'. The Contributor role allows publishing to the workspace, but the report will appear in the workspace, not the user's personal workspace. Option B is wrong because the Contributor role can publish content.

Option C is wrong because there is no license issue. Option D is wrong because the report is not automatically added to 'My workspace'.

Full explanation →
281
Multi-Selecteasy

Which TWO of the following are true about calculated columns in Power BI?

Select 2 answers
A.Calculated columns cannot be used in relationships.
B.Calculated columns are evaluated at query time.
C.Calculated columns are computed using DAX formulas.
D.Calculated columns consume memory because they are stored as part of the model.
E.Calculated columns are stored on disk and loaded on demand.
AnswersC, D

DAX is used for calculated columns.

Why this answer

Option C is correct because calculated columns in Power BI are defined using Data Analysis Expressions (DAX), a formula language specifically designed for data modeling and analysis. These DAX formulas are evaluated row by row during the data refresh process, not at query time, and the results are physically stored in the model.

Exam trap

The trap here is that candidates often confuse calculated columns with measures, mistakenly thinking calculated columns are evaluated at query time (Option B) or that they are not stored in memory (Option E), when in fact calculated columns are materialized during refresh and consume RAM.

Full explanation →
282
MCQeasy

You have a Power BI data model with a table 'Orders' that has columns: 'OrderID', 'OrderDate', 'CustomerName', 'Region', 'Product', 'Quantity', 'UnitPrice'. You want to create a measure that calculates total sales amount. Which DAX expression should you use?

A.Total Sales = COUNTROWS(Orders)
B.Total Sales = AVERAGE(Orders[Quantity]) * AVERAGE(Orders[UnitPrice])
C.Total Sales = SUM(Orders[Quantity] * Orders[UnitPrice])
D.Total Sales = SUMX(Orders, Orders[Quantity] * Orders[UnitPrice])
AnswerD

SUMX iterates over rows, performing a row-by-row calculation before summing.

Why this answer

Option A is correct. The SUMX function iterates over each row and multiplies Quantity by UnitPrice, then sums the result. Option B is incorrect because SUM only works on a single column.

Option C is incorrect because COUNTROWS counts rows, not amounts. Option D is incorrect because AVERAGE calculates average, not total.

Full explanation →
283
MCQeasy

You have a Power BI report that uses a date table with a continuous date range. You want to add a slicer that allows users to select a single month and then display data for that month only. You add a slicer visual with the Date field. However, the slicer shows individual dates instead of months. How should you configure the slicer to show months? A. Change the slicer type to 'Between' and then select a month range. B. Create a calculated column for Month and use that in the slicer. C. Use the 'Hierarchy' slicer with Date hierarchy. D. Set the slicer to 'List' and enable 'Show select all'. Which option is best?

A.Set the slicer to 'List' and enable 'Show select all'
B.Create a calculated column for Month and use that in the slicer
C.Use the 'Hierarchy' slicer with Date hierarchy
D.Change the slicer type to 'Between' and then select a month range
AnswerB

A Month column provides distinct month values for selection.

Why this answer

Option B is correct because creating a Month column (e.g., 'Month Year') allows users to select a month. Option A is wrong because 'Between' slicer still shows dates. Option C is wrong because hierarchy slicer shows drill-down, not single selection.

Option D is wrong because 'Select all' does not group by month.

Full explanation →
284
MCQmedium

You have a Power BI semantic model that imports data from a SQL Server view. The view is updated every hour, but the Power BI dataset is scheduled to refresh daily at 2:00 AM. Users report that reports show stale data. You need to ensure that the dataset reflects the latest data without changing the refresh schedule. What should you do?

A.Replace the view with a physical table in SQL Server.
B.Increase the scheduled refresh frequency to every 30 minutes.
C.Configure incremental refresh for the table.
D.Change the storage mode of the table to DirectQuery.
AnswerD

DirectQuery queries the source directly, providing up-to-date data on each report interaction.

Why this answer

Option D is correct because changing the storage mode to DirectQuery allows the Power BI dataset to query the SQL Server view directly at report render time, ensuring that users always see the latest data without altering the scheduled refresh frequency. DirectQuery bypasses the import process and retrieves data on demand, so the dataset reflects real-time changes from the source view.

Exam trap

The trap here is that candidates often assume incremental refresh (Option C) solves freshness issues, but it only optimizes data loading for large tables, not the refresh schedule, and still requires a scheduled refresh to update the dataset.

How to eliminate wrong answers

Option A is wrong because replacing the view with a physical table does not address the stale data issue; the dataset would still import data on the daily schedule, and the physical table would need its own refresh mechanism. Option B is wrong because increasing the scheduled refresh frequency to every 30 minutes changes the refresh schedule, which the question explicitly prohibits. Option C is wrong because incremental refresh still relies on the import storage mode and scheduled refresh; it only partitions data loading, not the refresh frequency, so the dataset would still only update at 2:00 AM daily.

Full explanation →
285
Multi-Selectmedium

You need to audit Power BI activities such as viewing reports, sharing dashboards, and exporting data. Which TWO actions should you take to enable and access audit logs? (Choose two.)

Select 2 answers
A.Configure Microsoft Defender for Cloud Apps to forward logs to Microsoft Sentinel.
B.Access the audit log from the Microsoft 365 compliance portal.
C.Enable the 'Create audit logs for Power BI activities' tenant setting in the admin portal.
D.Use the 'Export' feature in Power BI to export audit logs to a CSV file.
E.Set up a diagnostic setting in Azure Monitor to collect Power BI logs.
AnswersB, C

Audit logs are stored and accessible in the Microsoft 365 compliance portal.

Why this answer

Options A and C are correct. Enabling the audit log in the Power BI admin portal is the first step. Option C is correct because audit logs are stored in the Microsoft 365 compliance portal.

Option B is wrong because Microsoft Defender for Cloud Apps is not the primary storage for audit logs. Option D is wrong because Azure Monitor is not used for Power BI audit logs. Option E is wrong because Power BI itself does not store audit logs; it sends them to the Microsoft 365 audit log.

Full explanation →
286
Multi-Selectmedium

You are connecting to an on-premises Oracle database from Power BI Service. The gateway is installed and configured. However, the scheduled refresh fails with an error indicating that the data source credentials are invalid. Which TWO steps should you take to resolve the issue? (Choose two.)

Select 2 answers
A.Re-publish the Power BI report from Power BI Desktop.
B.Update the data source credentials in the gateway settings in Power BI Service.
C.Verify that the gateway machine can connect to the Oracle server and that the Oracle client is installed.
D.Edit the data source settings in Power BI Desktop and republish.
E.Reinstall the on-premises data gateway.
AnswersB, C

The stored credentials might be expired or incorrect; updating them in the service can resolve the issue.

Why this answer

Option B is correct because the scheduled refresh failure indicates that the stored credentials for the on-premises Oracle data source in Power BI Service are invalid. You must update the data source credentials in the gateway settings under 'Manage gateways' in Power BI Service to provide a valid username and password that the gateway can use to authenticate against the Oracle database. Option C is correct because the gateway machine requires the Oracle client software (e.g., Oracle Data Access Components or ODP.NET) to be installed and configured, and the gateway must have network connectivity to the Oracle server; verifying these ensures the gateway can reach and authenticate with the database.

Exam trap

The trap here is that candidates assume re-publishing or editing the report in Power BI Desktop will propagate credential changes to the gateway, but Power BI Service stores credentials independently for scheduled refresh, and only updating them in the gateway settings resolves the issue.

Full explanation →
287
Multi-Selecthard

You have a Power BI data model with a table named Employees that contains: EmployeeID, ManagerID, Department, and Salary. You need to create a parent-child hierarchy for the reporting structure. Which THREE actions should you perform?

Select 3 answers
A.Enable the 'Group on' feature in the visual to expand/collapse
B.Create calculated columns for the hierarchy path (e.g., PATH, PATHITEM)
C.Create a relationship between Employees[EmployeeID] and Employees[ManagerID]
D.Create a separate table for managers
E.Set cross filter direction to Both on the relationship
AnswersA, B, C

The hierarchy can be used in visuals with expand/collapse functionality.

Why this answer

Option A is correct because enabling the 'Group on' feature in a visual (such as a matrix or table) allows users to expand and collapse parent-child hierarchies, making the reporting structure interactive. This feature works with the hierarchy path created by calculated columns (Option B) and the self-referencing relationship (Option C) to display the drill-down behavior.

Exam trap

The trap here is that candidates often think a separate manager table is required (Option D) or that bidirectional filtering is needed (Option E), but Power BI handles parent-child hierarchies entirely within the same table using a self-referencing relationship and calculated columns.

Full explanation →
288
MCQeasy

You need to create a visual that shows the relationship between advertising spend and website traffic. Which type of visual is most appropriate?

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

Scatter charts show correlation between two measures.

Why this answer

Scatter charts are ideal for showing relationships between two numeric variables. A line chart shows trends over time, a bar chart compares categories, and a pie chart shows proportions.

Full explanation →
289
MCQeasy

You are designing a data model for a sales analysis. The 'Sales' fact table contains columns: OrderDate, ShipDate, Amount, Quantity. You need to analyze sales by both order date and ship date. What is the best practice to model the dates?

A.Create two date tables: one for OrderDate (active) and one for ShipDate (inactive), using USERELATIONSHIP as needed
B.Put the date keys in a separate table and relate to both
C.Create a single date table and merge both date columns into one
D.Use only one date table and create separate measures for each date
AnswerA

Allows analysis from both perspectives.

Why this answer

Option A is correct: Use two date dimensions with active/inactive relationships to support both analyses. Option B is wrong because merging dates loses distinction. Option C is wrong because a single date table can only be used for one role.

Option D is wrong because the fact table should not contain date dimension attributes.

Full explanation →
290
MCQhard

Refer to the exhibit. The DAX measure 'Sales YTD' is defined as shown. The model has a Date table marked as a date table and a relationship to Sales[OrderDate]. However, the measure returns BLANK for all months except December. What is the most likely cause?

A.The measure uses 'Date'[Date] but the fact table uses 'Sales'[OrderDate].
B.The Date table is not marked as a date table.
C.The Date table's year-end date is December 31, so YTD only shows data for December.
D.The relationship between the Date table and Sales table is inactive.
AnswerC

DATESYTD uses the year-end date from the date table; if the fiscal year ends in December, YTD for other months returns BLANK.

Why this answer

Option D is correct because DATESYTD uses the date table's year-end date, which by default is December 31. If the Date table's year ends in December, the YTD calculation only returns values for that month. Option A is wrong because the relationship is correctly configured.

Option B is wrong because the measure uses the Date table column. Option C is wrong because the Date table is marked as a date table.

Full explanation →
291
MCQmedium

You have a Power BI dataset that contains a table with sales data and a separate date table. You need to create a measure that calculates the total sales for the previous month relative to the selected date. Which DAX function should you use?

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

PREVIOUSMONTH returns the previous month in the current context.

Why this answer

Option B is correct because PREVIOUSMONTH returns the previous month based on the current filter context. Option A is wrong because DATEADD shifts dates by an interval but requires a number. Option C is wrong because PARALLELPERIOD returns a parallel period, not specifically previous month.

Option D is wrong because SAMEPERIODLASTYEAR returns the same period last year.

Full explanation →
292
MCQeasy

You want to allow users to highlight different product categories in a line chart by selecting from a list. Which feature should you add?

A.Slicer
B.Tooltip
C.Bookmarks
D.Drillthrough
AnswerA

A slicer allows users to filter or highlight categories.

Why this answer

A slicer filters or highlights data based on selection, making it ideal for category selection. Bookmarks save a state, drillthrough navigates to another page, and tooltips show details on hover.

Full explanation →
293
MCQhard

You are cleaning a column that contains numbers stored as text, with occasional leading/trailing spaces and currency symbols. You apply the function above to the column. However, some rows return null even though the original text appears to be a valid number, such as '$ 1,234.56'. What is the most likely cause?

A.The try...otherwise block is not catching parsing errors.
B.Text.Clean removes necessary decimal separators.
C.The function is applied to the wrong data type column.
D.The function does not remove commas and currency symbols before conversion.
AnswerD

The function only removes spaces and cleans non-printable characters. Commas and '$' remain, causing Number.From to fail.

Why this answer

Option D is correct because the function shown (likely a custom M function or Power Query transformation) does not strip commas and currency symbols before attempting conversion. When the input '$ 1,234.56' is passed directly to a number conversion like Number.From or Number.FromText, the presence of the dollar sign, spaces, and comma causes the conversion to fail, returning null. The try...otherwise block only catches errors but does not clean the text, so the conversion still fails silently.

Exam trap

The trap here is that candidates assume the try...otherwise block will handle all conversion issues, but they overlook that the conversion itself must first succeed on a clean string—the error handling only catches failures, it does not fix malformed input.

How to eliminate wrong answers

Option A is wrong because the try...otherwise block does catch parsing errors; the issue is that the conversion itself fails, not that the error handling is faulty. Option B is wrong because Text.Clean removes non-printable characters (like line feeds), not decimal separators; decimal separators are preserved. Option C is wrong because the function is applied to a text column (as stated), and the data type mismatch is not the root cause—the problem is the uncleaned text content, not the column type.

Full explanation →
294
MCQmedium

You are preparing a Power BI report that uses data from Azure SQL Database. The data includes a date column that needs to be used in time intelligence calculations. You want to ensure that the date column is recognized as a date table in the data model. What should you do?

A.Set the data type of the date column to Date.
B.Use the DAX function DATEADD to create a date table.
C.In the model view, mark the table as a date table by selecting the date column.
D.Create a calculated column using DATEVALUE to convert the date.
AnswerC

Marking a table as a date table enables time intelligence functions.

Why this answer

Option C is correct because marking a table as a date table in the model view explicitly tells Power BI that the table contains a complete set of dates for time intelligence calculations. This ensures that DAX functions like TOTALYTD, SAMEPERIODLASTYEAR, and DATEADD work correctly by using the marked date column as the primary date reference for the model, rather than relying on auto-generated date hierarchies.

Exam trap

The trap here is that candidates often confuse setting a column's data type to Date with marking the table as a date table, assuming the data type alone is sufficient for time intelligence, but Power BI requires explicit table marking to enable proper date filtering and DAX time functions.

How to eliminate wrong answers

Option A is wrong because setting the data type to Date only ensures the column is recognized as a date value, but it does not designate the table as a date table; time intelligence functions require a marked date table with a continuous range of dates. Option B is wrong because DATEADD is a time intelligence function used to shift dates, not a function to create a date table; creating a date table requires CALENDAR or CALENDARAUTO, not DATEADD. Option D is wrong because DATEVALUE converts a text string to a date, but it does not mark the table as a date table; the table must be explicitly marked in the model view for time intelligence to function properly.

Full explanation →
295
MCQeasy

You have a Power BI dataset that uses DirectQuery to a Snowflake data warehouse. Users report that reports are slow. You need to improve query performance without changing the data source. What should you configure?

A.Enable Query Folding in Power Query
B.Change the dataset to Import mode
C.Increase the number of concurrent queries in Power BI Service
D.Create aggregations in the Power BI model
AnswerD

Aggregations can pre-cache summaries, reducing query volume to source.

Why this answer

Option D is correct because creating aggregations in the Power BI model allows pre-summarized data to be stored in memory, reducing the volume of queries sent to Snowflake via DirectQuery. This improves performance without altering the data source, as aggregations can serve high-level queries from cached data while falling back to DirectQuery for detailed queries.

Exam trap

The trap here is that candidates often confuse Query Folding (which is about transformation pushdown) with performance optimization for DirectQuery, or mistakenly think increasing concurrency or switching to Import mode are viable solutions when the constraint explicitly forbids changing the data source.

How to eliminate wrong answers

Option A is wrong because Query Folding is a Power Query optimization that pushes transformations back to the source, but it is already inherently enabled in DirectQuery mode (all transformations are folded to Snowflake); enabling it further does not improve performance. Option B is wrong because changing the dataset to Import mode would require modifying the data source (by storing data in Power BI), which violates the constraint of not changing the data source. Option C is wrong because increasing concurrent queries in Power BI Service does not improve individual query performance; it only allows more simultaneous users, potentially worsening contention and latency.

Full explanation →
296
Multi-Selecthard

Your organization uses Power BI Premium with a shared capacity. You need to ensure that a specific workspace's data stays in the European region. Which TWO actions should you take? (Choose two.)

Select 2 answers
A.Configure the default geographic region for the tenant to Europe.
B.Create a Power BI Premium capacity in the European region.
C.Set the data residency option in the dataset settings to Europe.
D.Move the workspace to the Premium capacity created in Europe.
E.Apply a Microsoft Purview sensitivity label with encryption to the datasets.
AnswersB, D

Premium capacities can be created in specific Azure regions to enforce data residency.

Why this answer

Options A and C are correct. Creating a Premium capacity assigned to a European region ensures data residency. Moving the workspace to that capacity ensures the data is stored in Europe.

Option B is wrong because sensitivity labels do not control data residency. Option D is wrong because the default region is set at the tenant level, not per workspace. Option E is wrong because Power BI does not allow per-dataset regional settings.

Full explanation →
297
MCQeasy

You are importing data from a CSV file into Power BI. The file contains a column 'Price' with values like '$1,234.56'. When you preview the data, the column is recognized as text. You need to convert it to a decimal number. What should you do in Power Query Editor?

A.Replace values: remove '$' and ',' then change type to Decimal Number.
B.Split the column by delimiter and keep the numeric part.
C.Change the data type to Decimal Number directly.
D.Remove commas using Replace Values, then change type.
AnswerA

This cleans the text before conversion.

Why this answer

Option A is correct because Power Query Editor cannot automatically parse currency-formatted text like '$1,234.56' into a decimal number due to the non-numeric characters. By first using Replace Values to remove the '$' and ',' symbols, you strip the text down to '1234.56', which Power Query can then successfully convert to a Decimal Number type using the Change Type step.

Exam trap

The trap here is that candidates assume Power Query's automatic type detection or a single Replace Values step (e.g., removing only commas) is sufficient, overlooking that both the currency symbol and thousands separator must be removed before the type change can succeed.

How to eliminate wrong answers

Option B is wrong because splitting the column by delimiter would separate the value into multiple columns (e.g., '$1' and '234.56'), losing the original numeric integrity and requiring additional merging steps, which is inefficient and error-prone. Option C is wrong because changing the data type directly to Decimal Number will cause an error or return null for rows containing non-numeric characters like '$' and ','; Power Query's type conversion expects a clean numeric string. Option D is wrong because removing only commas leaves the '$' symbol intact, which still prevents Power Query from interpreting the value as a number, resulting in a conversion error.

Full explanation →
298
MCQmedium

You are preparing a Power BI dataset from a SQL Server data source. The source table has a datetime column 'OrderDate' that you need to use for time intelligence calculations. However, you notice that the data contains dates in multiple formats (e.g., '2024-01-15 14:30:00' and '01/15/2024 2:30 PM'). What is the best practice to ensure consistent date handling in Power Query?

A.Load the column as text and ignore any conversion errors.
B.Use the 'Detect Data Type' function in Power Query to automatically identify and convert the column.
C.Change the column type to 'Date' in Power Query before loading.
D.Split the column into separate date and time columns and then combine them.
AnswerB

Detect Data Type analyzes the data and applies the appropriate type, handling inconsistent formats.

Why this answer

Option B is correct because the 'Detect Data Type' function in Power Query analyzes the column's values to infer the most appropriate data type, automatically handling mixed formats like '2024-01-15 14:30:00' and '01/15/2024 2:30 PM' by converting them to a consistent datetime type. This ensures that time intelligence calculations in Power BI can rely on a uniform date/time column without manual intervention or data loss.

Exam trap

The trap here is that candidates often choose Option C (changing to 'Date' type) thinking it simplifies the data, but they overlook that this discards the time component, which is essential for many time intelligence calculations and can cause unexpected aggregation errors.

How to eliminate wrong answers

Option A is wrong because loading the column as text and ignoring conversion errors would leave the data as strings, preventing any time intelligence functions (e.g., DATEADD, DATESYTD) from working correctly, as they require a date or datetime data type. Option C is wrong because changing the column type directly to 'Date' would truncate the time portion of the datetime values, losing granularity needed for time-based calculations like hour-level trends. Option D is wrong because splitting the column into separate date and time columns is unnecessary and adds complexity; Power Query can handle mixed datetime formats natively with type detection, and splitting would require recombining for time intelligence, which is inefficient.

Full explanation →
299
MCQeasy

You are importing data from a folder containing multiple CSV files with identical structure. You want to automatically combine all files into one table in Power Query. Which connector should you use?

A.Excel Workbook connector
B.CSV connector
C.Web connector
D.Folder connector
AnswerD

The Folder connector allows you to combine multiple files with the same structure.

Why this answer

The Folder connector is the correct choice because it is specifically designed to connect to a folder containing multiple files, and when combined with the 'Combine Files' transformation in Power Query, it automatically merges all CSV files with identical structures into a single table. This connector handles the iterative process of reading each file and appending rows without manual scripting.

Exam trap

The trap here is that candidates often choose the CSV connector because they think it can handle multiple files, but it only processes a single file per connection, while the Folder connector is the correct tool for batch combining.

How to eliminate wrong answers

Option A is wrong because the Excel Workbook connector is used for importing data from a single Excel file, not for combining multiple CSV files from a folder. Option B is wrong because the CSV connector imports only one CSV file at a time; it does not support batch processing or automatic combination of multiple files from a directory. Option C is wrong because the Web connector is designed to import data from web URLs or APIs, not from local or network folders containing CSV files.

Full explanation →
300
MCQmedium

You are a Power BI administrator. Your organization uses Microsoft Entra ID for identity management. You need to ensure that only users from specific security groups can access the Power BI service. What should you configure?

A.In the Power BI admin portal, configure the 'Allow users to access Power BI' setting to specify the security groups.
B.Create a conditional access policy in Microsoft Entra ID that grants access to Power BI only for members of the allowed security groups.
C.Configure the 'B2B guest user settings' to allow only specific domains.
D.Modify the workspace access permissions to include only the allowed security groups.
AnswerB

Conditional access policies can restrict access to cloud apps like Power BI based on group membership.

Why this answer

Option C is correct because conditional access policies in Microsoft Entra ID can restrict access to the Power BI service based on security group membership. Option A is wrong because the Power BI admin portal does not have a setting to restrict access to specific security groups. Option B is wrong because guest user settings control external access, not internal group restrictions.

Option D is wrong because workspace access settings control access to workspaces, not the service itself.

Full explanation →
Page 3

Page 4 of 13

Page 5

All pages

12345678910111213

Practice PL-300 by domain

Target a specific domain to shore up weak areas.

Prepare the dataDeploy and maintain assetsModel the dataVisualize and analyze the dataManage and secure Power BI
See all domains with question counts →