Courseiva

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

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

Take a mock examExam hub
Page 9

Page 10 of 13

Page 11
676
MCQhard

Your report contains a measure that calculates year-over-year growth. Users report that the measure returns blank for months where sales data exists in the current year but not in the previous year. How should you modify the measure to return 100% growth in such cases?

A.Use COALESCE(previous year sales, 1) in the denominator
B.Wrap the previous year sales in IF(ISBLANK(...), 0, ...)
C.Use DIVIDE(current, previous, 0)
D.Use SELECTEDVALUE to ignore blank years
AnswerA

COALESCE replaces blank with 1, so growth becomes (current-1)/1 = current-1, but if current>0, growth is positive; however, to get 100% growth when previous is blank, you need to handle logic: if previous is blank, result should be 1 (100%). Actually, the correct measure is: IF(ISBLANK(previous), 1, DIVIDE(current - previous, previous)). But among options, C is closest to best practice: COALESCE(previous,1) then DIVIDE(current - previous, previous) would yield (current-1)/1, which is not 100% unless current=2. So explanation may need nuance. However, the intended answer is C because COALESCE is the modern way to replace blanks.

Why this answer

Option C is correct because COALESCE replaces blank with a default value (1). Option A is wrong because IF(ISBLANK(...),0) would return 0 growth, not 100%. Option B is wrong because DIVIDE with 0 as alternate result would return 0.

Option D is wrong because SELECTEDVALUE is for single value selection, not for handling blanks.

Full explanation →
677
MCQeasy

You need to ensure that a Power BI report containing sensitive financial data is not accessible to users outside your organization. The report is published to a workspace in the Power BI service. What should you do?

A.Remove the report from the Power BI service and distribute it via email.
B.Apply a sensitivity label of 'Highly Confidential' to the report.
C.Disable 'Allow external sharing' in the Power BI admin portal.
D.Disable 'Publish to web' in the tenant settings.
AnswerC

This prevents any external user from accessing content.

Why this answer

Option C is correct. Disabling 'Allow external sharing' at the tenant level prevents sharing with external users. Option A is wrong because sensitivity labels classify data but do not block external access by default.

Option B is wrong because the report is already in the service. Option D is wrong because disabling 'Publish to web' prevents embedding, but external users could still be explicitly shared to.

Full explanation →
678
Multi-Selecthard

Which THREE considerations are important when designing a star schema for a Power BI semantic model? (Choose three.)

Select 3 answers
A.Dimension tables should use natural keys instead of surrogate keys for better performance.
B.Role-playing dimensions should be implemented by creating multiple dimension tables or using views.
C.Fact tables should contain numeric measures and foreign keys to dimension tables.
D.Date dimensions should be created to enable time intelligence calculations.
E.Dimensions should be normalized (snowflaked) to reduce data redundancy.
AnswersB, C, D

Role-playing dimensions (e.g., OrderDate, ShipDate) need separate tables or views to function correctly.

Why this answer

Option B is correct because role-playing dimensions, such as a Date dimension used for Order Date, Ship Date, and Due Date, require multiple references to the same dimension table. In Power BI, you implement this by creating multiple dimension tables (e.g., via calculated tables or referencing the same source table) or using database views to provide unique foreign key relationships, enabling correct time intelligence and filtering.

Exam trap

The trap here is that candidates often assume natural keys are better for readability or that snowflaking is acceptable for reducing redundancy, but the PL-300 exam emphasizes that star schemas with surrogate keys and denormalized dimensions are optimal for Power BI performance and DAX time intelligence.

Full explanation →
679
Multi-Selectmedium

Which THREE are best practices for managing relationships in Power BI? (Select exactly 3.)

Select 3 answers
A.Use many-to-many relationships whenever possible to simplify the model
B.Hide foreign key columns in dimension tables to prevent misuse
C.Use single-direction cross-filtering unless bidirectional is required
D.Always set cross-filter direction to both to allow full interactivity
E.Ensure that the data types of related columns match
AnswersB, C, E

Foreign keys are not needed in report visuals and can confuse users.

Why this answer

Options A, C, and D are correct. Option A: Using single-direction cross-filtering is generally recommended to avoid ambiguity and performance issues. Option C: Hiding foreign key columns in dimension tables prevents confusion and accidental use in visuals.

Option D: Ensuring data types match between related columns is essential for relationship creation. Option B is wrong because many-to-many relationships should be avoided when possible; they can be complex and impact performance. Option E is wrong because bidirectional filtering is not typically recommended; it can cause ambiguous filtering and performance degradation.

Full explanation →
680
MCQhard

You are a Power BI data analyst at a global retail company. Your organization uses a SQL Server data warehouse to store sales transactions, product inventory, and customer demographics. The data warehouse is updated nightly. You have been tasked with building a Power BI report to analyze sales performance across different regions and product categories. The report must meet the following requirements: - Allow users to filter data by date, region, and product category. - Provide drill-down from region to store level. - Display key metrics such as total sales, sales growth compared to the previous year, and profit margin. - Ensure that the report loads quickly even when users apply multiple filters. - Users must be able to export the underlying data to Excel for further analysis. - The report should be accessible on mobile devices with a responsive layout. - You need to implement row-level security so that regional managers can only see data for their own region. - The dataset must support scheduled refresh. You have imported the necessary tables from the data warehouse using Import mode. You created a date dimension table using DAX and marked it as a date table. You also created a separate table for regions with a column 'RegionManagerEmail' that maps each region to the manager's email address. You plan to use RLS by creating a role that filters the region table based on the user's email address. After publishing the report to the Power BI service, you notice that the report takes a long time to load when users select a large date range. Additionally, the profit margin measure, which is calculated as DIVIDE(SUM(Sales[Profit]), SUM(Sales[Revenue])), returns blank for some rows even though both Profit and Revenue have values. You also receive feedback that the mobile layout is not optimized; the visuals are too small and the slicers are not accessible. You need to address these issues. What should you do?

A.Implement incremental refresh on the fact table and create a separate measure for profit margin using COALESCE.
B.Change the storage mode to DirectQuery for the fact table and use the Power BI Desktop's 'Optimize for mobile' option.
C.Create aggregations on the fact table in the data source to reduce data volume, verify relationships for the profit margin measure, and use the Power BI mobile layout view to optimize visuals and slicers.
D.Increase the capacity of the Power BI service to Premium Per User and enable large dataset storage.
AnswerC

Aggregations improve performance, proper relationships fix profit margin, mobile layout view optimizes mobile experience.

Why this answer

Option C is correct because creating aggregations on the fact table in the data source (e.g., pre-aggregated daily sales) reduces the amount of data loaded into the model, improving load times. The profit margin issue is likely due to a missing relationship or filter context; verifying relationships and using DIVIDE with an alternate result will fix blanks. For mobile layout, using the mobile layout view to resize visuals and place slicers at the top improves accessibility.

Option A is wrong because increasing RAM is a temporary fix and does not address the root cause. Option B is wrong because incremental refresh can help with load times but does not fix the profit margin issue or mobile layout. Option D is wrong because changing to DirectQuery might introduce performance issues and does not address the profit margin or mobile layout.

Full explanation →
681
MCQmedium

You have a Power BI dataset that uses a live connection to an Analysis Services tabular model. The model contains a measure that uses the ALL function. You need to create a report page that shows sales by region, but you want to display the percentage of total sales regardless of region filter. How should you achieve this?

A.Modify the measure in the Analysis Services model to use ALLSELECTED instead of ALL.
B.Use the existing measure and add a visual-level filter to show percentage.
C.Change the connection to Import mode and then create the measure.
D.Create a new measure in the Power BI dataset using DAX that divides the region sales by total sales.
AnswerB

Visual-level filters can be applied, but for percentage of total, you need a measure that uses ALL; you must request the model owner to create a percentage measure.

Why this answer

Option B is correct because with a live connection to Analysis Services, you cannot modify the underlying measure in Power BI; you must work with the existing measures. By using the existing measure and adding a visual-level filter to show the percentage (e.g., by using the 'Show value as' option set to 'Percent of grand total'), you can display the percentage of total sales regardless of the region filter without altering the model.

Exam trap

The trap here is that candidates often think they need to modify the measure or change the connection mode to achieve percentage calculations, but Power BI's visual-level formatting options can handle this without altering the source model.

How to eliminate wrong answers

Option A is wrong because you cannot modify measures in the Analysis Services model from Power BI; the live connection is read-only, and changing the measure to use ALLSELECTED would require editing the source model, which is not possible from Power BI. Option C is wrong because changing the connection to Import mode would require redesigning the data model and is unnecessary; you can achieve the desired result without changing the connection type. Option D is wrong because you cannot create new measures in the Power BI dataset when using a live connection; the dataset is read-only, and all measures must be defined in the Analysis Services model.

Full explanation →
682
MCQeasy

Refer to the exhibit. You define an RLS role in Power BI Desktop as shown. You publish the dataset and assign the user 'user@contoso.com' to the role. When the user views a report that uses this dataset, they see no data. What is the most likely cause?

A.The role name is invalid; it must not contain spaces.
B.RLS is not applied in Power BI service for tables with less than 100 rows.
C.The user is not assigned to the role correctly.
D.The Region values in the data have leading spaces or are not exactly 'North' (e.g., 'North ').
AnswerD

Exact match fails if data differs.

Why this answer

The filter expression uses a string comparison that might not match due to case sensitivity or leading/trailing spaces. Option A is correct. Option B is wrong because the role name is valid.

Option C is wrong because the user is assigned to the role. Option D is wrong because RLS works in the service.

Full explanation →
683
MCQeasy

You are preparing data for a Power BI report. The source data contains a column with mixed data types: some values are numbers, others are text. When loading into Power Query, the entire column is typed as text. What is the likely cause?

A.The column was imported as text because the data source is a CSV file
B.Power Query detected that the column contains text values in some rows, so it set the data type to text
C.The 'Detect data type' option was disabled in Power Query settings
D.The source data is stored as text in the database
AnswerB

Power Query automatically detects the data type based on the values in the column; mixed types default to text.

Why this answer

Power Query's column type detection logic examines the entire column during import. If any row contains a non-numeric value (e.g., text), Power Query defaults the entire column to text to avoid data loss or conversion errors. This is the standard behavior when mixed data types are present, regardless of the source format.

Exam trap

The trap here is that candidates assume the data source format (e.g., CSV) is the cause, but Power Query's type detection logic—not the source—is what forces the column to text when mixed data types are present.

How to eliminate wrong answers

Option A is wrong because CSV files do not inherently force a column to text; Power Query still performs type detection on CSV data, and the mixed content triggers the text fallback. Option C is wrong because the 'Detect data type' option, when disabled, would leave all columns as 'Any' type, not specifically text. Option D is wrong because even if the source database stores the column as text, Power Query would still import it as text, but the question states the column has mixed data types, implying the source itself contains both numbers and text, which is the root cause.

Full explanation →
684
MCQmedium

You are designing a Power BI model that includes a fact table with sales data and a dimension table for customers. Each customer can have multiple addresses, but you only need the primary address for analysis. The source system has a 'CustomerAddress' table with a 'IsPrimary' flag. What is the best approach to bring this into the model?

A.Use a DAX measure to filter the address table dynamically.
B.Import the entire CustomerAddress table and create an active relationship on the CustomerID column.
C.In Power Query, filter the CustomerAddress table to only include rows where IsPrimary = True, then merge with Customer.
D.Create a calculated table using SUMMARIZE to get the primary address per customer.
AnswerC

This loads only the needed rows, reducing model size.

Why this answer

Option C is correct because it uses Power Query to filter the CustomerAddress table to only primary addresses before merging with the Customer dimension. This ensures that only the necessary rows are imported into the model, reducing data volume and avoiding complex DAX or relationship overhead. The result is a clean, single-row-per-customer dimension that directly supports analysis without runtime filtering.

Exam trap

The trap here is that candidates often choose Option B, thinking that importing the full table and using a relationship is simpler, but they overlook the need to enforce a single primary address per customer, which requires additional filtering logic that complicates the model and degrades performance.

How to eliminate wrong answers

Option A is wrong because a DAX measure cannot filter a table at the model level; it only applies dynamic filters at query time, which would not resolve the need for a single primary address per customer in the dimension table and would cause performance issues with repeated evaluation. Option B is wrong because importing the entire CustomerAddress table with an active relationship on CustomerID would create a one-to-many relationship from Customer to multiple addresses, requiring additional logic (e.g., a DAX filter or a calculated table) to isolate the primary address, which defeats the goal of a clean dimension. Option D is wrong because using SUMMARIZE to create a calculated table in DAX would work but is less efficient than Power Query filtering; it adds a calculated table to the model that is computed at refresh time and cannot leverage Power Query's native data transformation capabilities, and it may introduce subtle issues with blank rows or performance if the source table is large.

Full explanation →
685
MCQmedium

You have a report that uses a custom visual from AppSource. The visual is not rendering correctly after a Power BI Desktop update. What is the best course of action?

A.Enable compatibility mode for the visual.
B.Replace the custom visual with a built-in visual.
C.Check for an updated version of the custom visual from the developer.
D.Remove the visual and add it again from the marketplace.
AnswerC

Updates often fix compatibility issues with new Power BI versions.

Why this answer

Option D is correct because checking for an updated version from the developer is the best step. Option A is wrong because other visuals may not have the same functionality. Option B is wrong because compatibility mode is not a feature.

Option C is wrong because removing and adding may not help if the visual is incompatible.

Full explanation →
686
MCQeasy

You are cleaning data in Power Query. A column contains customer names with inconsistent capitalization (e.g., 'john smith', 'JANE DOE'). You need to standardize the names to proper case (first letter uppercase, rest lowercase). Which transformation should you use?

A.Use 'Format' > 'Trim'.
B.Use 'Format' > 'Capitalize Each Word'.
C.Use 'Format' > 'Lowercase'.
D.Use 'Format' > 'Uppercase'.
AnswerB

This converts the first letter of each word to uppercase and the rest to lowercase.

Why this answer

The 'Capitalize Each Word' transformation in Power Query converts the first letter of each word to uppercase and the rest to lowercase, which is exactly what proper case requires. This is the correct choice because it directly addresses the need to standardize inconsistent casing (e.g., 'john smith' becomes 'John Smith', 'JANE DOE' becomes 'Jane Doe').

Exam trap

The trap here is that candidates may confuse 'Capitalize Each Word' with 'Uppercase' or 'Lowercase', thinking any casing transformation will suffice, but only 'Capitalize Each Word' produces the specific proper case format required.

How to eliminate wrong answers

Option A is wrong because 'Trim' only removes leading and trailing whitespace from text, it does not alter character casing. Option C is wrong because 'Lowercase' converts all characters to lowercase (e.g., 'JANE DOE' becomes 'jane doe'), which does not achieve the required first-letter uppercase format. Option D is wrong because 'Uppercase' converts all characters to uppercase (e.g., 'john smith' becomes 'JOHN SMITH'), which does not produce proper case.

Full explanation →
687
MCQeasy

You are a Power BI administrator for a small business. The company uses Power BI Pro licenses for all users. You need to ensure that all data sources used in Power BI reports are documented and that sensitive data is classified. You have been asked to set up a process that automatically scans Power BI datasets for sensitive data and adds classification labels. You have the following options: A. Use Microsoft Purview to scan Power BI datasets and apply sensitivity labels. B. Use Power BI's built-in data classification feature to manually label datasets. C. Use Microsoft Sentinel to monitor data access and apply labels. D. Use Azure Policy to enforce labeling on Power BI datasets. Which option should you choose?

A.Use Microsoft Purview to scan Power BI datasets and apply sensitivity labels.
B.Use Power BI's built-in data classification feature to manually label datasets.
C.Use Azure Policy to enforce labeling on Power BI datasets.
D.Use Microsoft Sentinel to monitor data access and apply labels.
AnswerA

Purview provides automated scanning and labeling.

Why this answer

Option A is correct. Microsoft Purview can automatically scan Power BI datasets for sensitive data and apply sensitivity labels based on classification rules. Option B is wrong because manual labeling is not automatic.

Option C is wrong because Microsoft Sentinel is a SIEM, not a data classification tool. Option D is wrong because Azure Policy does not directly integrate with Power BI for labeling.

Full explanation →
688
MCQhard

You are building a report that uses AI visuals from Power BI. You want to automatically detect outliers in sales data. Which visual should you use?

A.Q&A visual
B.Key Influencers
C.Smart Narrative
D.Decomposition Tree
AnswerB

Can identify outliers and key drivers.

Why this answer

Option C is correct because the Key Influencers visual can detect outliers as part of its analysis. Option A is wrong because Decomposition Tree breaks down measures but does not specifically highlight outliers. Option B is wrong because Q&A is a natural language query tool, not an outlier detection visual.

Option D is wrong because Smart Narrative generates text summaries but does not identify outliers visually.

Full explanation →
689
MCQhard

A Power BI report uses a DirectQuery dataset connected to an Azure SQL Database. Users report that the report takes over 30 seconds to load. You need to improve performance without changing the data model. What should you recommend?

A.Increase the 'Maximum connections per user' setting in the Premium capacity.
B.Enable 'Reduce cardinality by using aggregation' in the dataset settings.
C.Convert the dataset to Import mode.
D.Disable 'Cross-report data binding' in the report settings.
AnswerB

Aggregations can improve DirectQuery performance.

Why this answer

Option B is correct. Enabling 'Reduce cardinality by using aggregation' can improve DirectQuery performance by pre-aggregating data. Option A is wrong because Import mode changes the data model approach.

Option C is wrong because disabling 'Cross-report data binding' affects report interactivity but not query performance. Option D is wrong because increasing the max connections per user might help concurrency but not single query latency.

Full explanation →
690
MCQeasy

A user reports that they cannot publish a Power BI Desktop file to the Power BI service. The error message indicates insufficient permissions. The user is a member of a workspace and has the Viewer role. What is the most likely cause?

A.The user has the Viewer role in the workspace
B.Row-level security (RLS) is preventing the user from seeing the data
C.The user does not have a Power BI Pro license
D.The .pbix file is stored on a network share that restricts write access
AnswerA

Viewers cannot publish; they need at least Contributor role.

Why this answer

Option B is correct because the Viewer role in a Power BI workspace does not allow publishing or editing. Option A is wrong because the Power BI license is required but the user has a license as a workspace member. Option C is wrong because the report may not be in a shared drive, but the core issue is role permissions.

Option D is wrong because RLS does not affect publishing permissions.

Full explanation →
691
Multi-Selecthard

You are preparing data from an Azure SQL Database. You need to ensure that sensitive columns (e.g., Social Security Numbers) are obfuscated in Power BI reports. Which TWO of the following approaches can you use? (Choose two.)

Select 2 answers
A.Configure dynamic data masking on the Azure SQL Database.
B.Use row-level security (RLS) in Power BI to hide sensitive columns.
C.Transform the data in Power Query by replacing sensitive values with a placeholder.
D.Use Microsoft Purview sensitivity labels to mask data.
E.Apply column-level security in Power BI Desktop.
AnswersA, C

Dynamic data masking obfuscates data at the database level for certain users, so Power BI will receive masked data.

Why this answer

Option A is correct because Azure SQL Database Dynamic Data Masking (DDM) obfuscates sensitive data at the database query level, so when Power BI connects to the database, the masked values are automatically returned for unauthorized users. This is a server-side approach that does not require changes to the Power BI report or data model.

Exam trap

The trap here is that candidates confuse Row-Level Security (RLS) with column-level masking, not realizing that RLS only filters rows and cannot hide or obfuscate column values, while column-level security in Power BI requires Premium features and object-level security (OLS), not a standard Desktop capability.

Full explanation →
692
MCQmedium

You are a data analyst at a retail company. You are building a Power BI report to analyze sales performance across multiple stores. The source data comes from an Azure SQL Database that contains a table 'Sales' with columns: StoreID, ProductID, SaleDate, Quantity, and Amount. The database also has a 'Stores' table with StoreID and StoreName, and a 'Products' table with ProductID, ProductName, and Category. You need to create a data model that supports filtering by store, product category, and date, and also allows calculation of year-over-year sales growth. You want to minimize the model size and ensure optimal performance. The data volume is large (millions of rows). You must design the data model. What should you do?

A.Import all tables as they are and create a single flat table by merging Sales, Stores, and Products in Power Query.
B.Import Sales, Stores, and Products tables, create a separate date table using CALENDAR, and establish relationships between Sales and dimension tables.
C.Import Sales table only and create calculated columns for StoreName and ProductName using RELATED.
D.Import Sales table and use the auto date/time feature for time intelligence.
AnswerB

Star schema with date table improves performance and enables time intelligence.

Why this answer

Option B is correct because it follows the star schema best practice: importing dimension tables (Stores, Products, a dedicated Date table) and the fact table (Sales) separately, then creating relationships. This minimizes model size by avoiding data duplication and enables efficient filtering by store, product category, and date. The separate date table is essential for accurate year-over-year calculations using DAX time intelligence functions like SAMEPERIODLASTYEAR, which require a continuous date range.

Exam trap

The trap here is that candidates often choose Option A (flat table) thinking it simplifies the model, not realizing that star schema design is essential for performance and compression in large datasets, and that Power BI's query folding can handle joins efficiently without merging.

How to eliminate wrong answers

Option A is wrong because merging all tables into a single flat table in Power Query creates massive data duplication (repeating StoreName and ProductName for every sales row), drastically increasing model size and degrading performance with millions of rows. Option C is wrong because importing only the Sales table and using calculated columns with RELATED forces Power BI to store the dimension data within the fact table, bloating the model and losing the benefits of separate dimension tables for filtering and compression. Option D is wrong because relying on the auto date/time feature creates hidden, auto-generated date tables that are not customizable, cannot support proper year-over-year calculations with DAX time intelligence, and can increase model size unnecessarily for large datasets.

Full explanation →
693
MCQmedium

You have a Power BI report that uses a DirectQuery dataset. You need to ensure that users see only the data relevant to their department. What should you implement?

A.Q&A features to restrict natural language queries.
B.Row-level security (RLS) with DAX filter expressions.
C.Object-level security (OLS) to hide tables.
D.Data lineage view to control access.
AnswerB

RLS filters rows based on user identity.

Why this answer

Row-level security (RLS) is the correct approach because it filters data at the query level based on the user's identity. In a DirectQuery model, RLS translates DAX filter expressions into source queries, ensuring that each user only sees rows relevant to their department without duplicating reports or datasets.

Exam trap

The trap here is that candidates confuse row-level security (RLS) with object-level security (OLS), thinking OLS can filter rows when it only hides entire objects like tables or columns.

How to eliminate wrong answers

Option A is wrong because Q&A features allow natural language queries but do not restrict data visibility; they only control how users can phrase questions. Option C is wrong because object-level security (OLS) hides entire tables or columns, not rows, so it cannot filter data by department. Option D is wrong because data lineage view is a metadata visualization tool for impact analysis, not a security mechanism to control user access to data.

Full explanation →
694
MCQmedium

You manage a Power BI workspace used by the sales team. After updating a dataset with new columns, some users report that their reports show old data. You verify that the scheduled refresh completed successfully. What should you do first?

A.Open the report in Power BI Desktop, refresh the dataset, and republish.
B.Clear the users' browser cache.
C.Reconfigure the scheduled refresh to run more frequently.
D.Reset the on-premises data gateway.
AnswerA

Updating the dataset in Desktop and republishing ensures the report uses the new schema.

Why this answer

Option A is correct because when a dataset is updated with new columns in Power BI Desktop, the report's underlying data model must be refreshed and republished to the Power BI service. Even if the scheduled refresh completes successfully, it only refreshes the existing data structure; it does not automatically incorporate schema changes like new columns. Republishing the .pbix file ensures the service has the updated metadata and data.

Exam trap

The trap here is that candidates assume a successful scheduled refresh automatically propagates all changes, including schema modifications, when in fact it only refreshes data within the existing model structure.

How to eliminate wrong answers

Option B is wrong because clearing the users' browser cache would not resolve the issue of missing new columns; the report in the service still has the old schema. Option C is wrong because increasing the scheduled refresh frequency does not add new columns to the dataset; it only refreshes existing data. Option D is wrong because resetting the on-premises data gateway is unrelated to schema changes; the gateway handles data movement, not dataset structure updates.

Full explanation →
695
MCQmedium

You are importing data from an Excel workbook that has multiple worksheets. You only need data from the 'Sales' worksheet. When you connect via Power Query, all worksheets appear in the Navigator. What should you do to load only the 'Sales' worksheet?

A.Load all worksheets, then delete the unwanted ones
B.Select the 'Sales' worksheet in Navigator and click 'Load'
C.Select all worksheets and click 'Load'
D.Select the 'Sales' worksheet and click 'Transform Data'
AnswerB

Directly loads only that worksheet.

Why this answer

Option A is correct because selecting the worksheet and clicking Load loads it. Option B is incorrect because Transform Data opens Power Query for transformation. Option C is incorrect because that would load all.

Option D is incorrect because deleting steps is unnecessary.

Full explanation →
696
Multi-Selecthard

A Power BI administrator needs to enforce that all datasets published to the service use certified data sources only. Which two settings should be configured? (Choose two.)

Select 2 answers
A.Use Microsoft Sentinel to audit Power BI activity logs and flag non-certified data sources.
B.Enable 'Certification' for dataflows in the Power BI tenant settings.
C.Enable 'Certification' for data sources in the Power BI tenant settings.
D.Configure row-level security (RLS) on all datasets.
E.Set up B2B guest user permissions to restrict external data sources.
AnswersA, C

Sentinel can ingest audit logs to detect and alert on use of uncertified data sources.

Why this answer

Option A (tenant setting for 'Certification' of data sources) and Option C (admin monitoring with Microsoft Sentinel) are correct. Option A directly enforces certification. Option C allows detection of non-compliant datasets via logs.

Option B (Row-level security) does not enforce data source certification. Option D (B2B guest settings) is irrelevant. Option E (dataflow certification) certifies dataflows, not datasets.

Full explanation →
697
Matchingmedium

Match each visualization type to its typical use case.

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

Concepts
Matches

Show trends over time

Show proportions of a whole

Show relationship between two variables

Compare parts of a category

Show stages in a process

Why these pairings

Different visuals are suited for different analytical tasks.

Full explanation →
698
MCQmedium

A company has a large fact table with sales data. The Sales table contains columns: OrderDate, ShipDate, DueDate, LineTotal, ProductKey, CustomerKey, TerritoryKey. The company needs to analyze sales by fiscal year (April 1 to March 31) and by calendar year. What is the recommended approach to model the date dimension?

A.Use a single date dimension table and keep only one active relationship (e.g., to OrderDate). For other dates, create measures that filter the date table using CALCULATE and FILTER.
B.Create a separate date dimension table for each date column in the Sales table and relate each to the fact table.
C.Use a single date dimension table and create multiple active relationships using bridging tables or by duplicating the dimension table for each role.
D.Use a single date dimension table and create inactive relationships for ShipDate and DueDate. Use USERELATIONSHIP in DAX measures.
AnswerA

This is the recommended approach: keep one active relationship (e.g., to OrderDate) and use USERELATIONSHIP in DAX to activate the inactive relationships for ShipDate and DueDate when needed.

Why this answer

Option A is correct because it uses a single date dimension table with one active relationship (typically to OrderDate) and leverages CALCULATE with FILTER or USERELATIONSHIP for other date roles. This is the recommended star schema design in Power BI, as it avoids unnecessary table duplication and maintains model simplicity while supporting fiscal year analysis via a calculated column in the date table.

Exam trap

The trap here is that candidates often assume multiple date columns require multiple date tables (Option B) or that inactive relationships alone solve all date role needs (Option D), forgetting that fiscal year logic must be explicitly modeled in the date table.

How to eliminate wrong answers

Option B is wrong because creating separate date dimension tables for each date column violates star schema principles, leads to model bloat, and complicates cross-date analysis without any performance benefit. Option C is wrong because using bridging tables or duplicating the dimension table for each role is unnecessary and introduces redundancy; Power BI supports role-playing dimensions through inactive relationships and USERELATIONSHIP, not by duplicating tables. Option D is wrong because while it correctly uses inactive relationships and USERELATIONSHIP, it does not address the fiscal year requirement—a date table must include a fiscal year column (e.g., April 1 start) to enable fiscal year analysis, which is not mentioned in this option.

Full explanation →
699
MCQhard

You have a Power BI data model with a table named 'Sales' and a table named 'Targets'. The 'Sales' table contains daily sales data, and the 'Targets' table contains monthly sales targets for each product category. You need to create a measure that calculates the percentage of target achieved for the current month. The relationship between 'Sales' and 'Targets' is on CategoryID and Month. However, the 'Sales' table has a granularity of day, while 'Targets' has month. What issue might you encounter when creating this measure?

A.The relationship requires bidirectional cross-filtering to work correctly
B.The relationship may cause ambiguity because the granularity of the tables is different
C.The relationship will create a many-to-many cardinality that slows performance
D.The relationship will not work because the columns have different data types
AnswerB

Daily sales data aggregates to month level; the relationship may need special handling.

Why this answer

Option A is correct because the different granularities can cause ambiguity in the relationship if not properly managed. When 'Sales' is filtered by a specific day, the relationship to 'Targets' may not filter correctly because 'Targets' is at month level. Option B is wrong because data type mismatch is not mentioned.

Option C is wrong because many-to-many is not the issue; the relationship is likely many-to-one. Option D is wrong because bidirectional filtering is not necessary and could cause issues.

Full explanation →
700
MCQhard

You receive the above JSON policy for a Power BI dataset. You need to add a relationship between the 'Sales' table and a 'Calendar' table in the same dataset. What must you modify in the JSON?

A.Add an object to the 'relationships' array.
B.Add a new table to the 'tables' array.
C.Change the 'version' field to '2.0'.
D.Add a measure that references the Calendar table.
AnswerA

Relationships are defined in the 'relationships' array.

Why this answer

Option B is correct because relationships are defined in the 'relationships' array within the dataset. Option A is wrong because the 'tables' array holds table definitions, not relationships. Option C is wrong because measures are separate.

Option D is wrong because the dataset version is metadata, not a place for relationships.

Full explanation →
701
MCQeasy

You are a Power BI administrator. A user reports that they receive an error 'You cannot view this report because it is not shared with you' when trying to open a report in a workspace where they are a Member. What is the most likely cause?

A.The report has restricted access set at the report level, and the user is not in the allowed list.
B.The report is stored in a different workspace.
C.The user's role is Viewer, not Member.
D.The user's Power BI license is expired.
AnswerA

Report owners can restrict access to specific users even within a workspace.

Why this answer

Option A is correct because report-level permissions are separate from workspace roles; the report owner may have restricted access to specific users. Option B is wrong because Member role allows viewing all content unless restricted. Option C is wrong because the report is in the workspace.

Option D is wrong because if the user is a Member, they should be able to view unless explicitly denied.

Full explanation →
702
MCQhard

You have a Power BI dataset with a many-to-many relationship between Sales and Product. You need to create a measure that sums sales amount by product category, but the relationship is causing incorrect totals. What is the best solution?

A.Use the USERELATIONSHIP function in the measure.
B.Use the CROSSFILTER function to set both directions.
C.Change the relationship to one-to-many using a calculated column.
D.Create a bridge table and set the relationship direction to single.
AnswerD

A bridge table resolves many-to-many; single direction prevents ambiguity.

Why this answer

Using a bridge table with a CROSSFILTER function or setting the relationship to single direction can resolve ambiguity. However, the recommended approach is to use a bridge table and set the relationship to single direction with 'Apply security filter in both directions' disabled.

Full explanation →
703
MCQhard

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

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

If the interaction is set to None, clicking the bar chart will not filter the line chart. It should be set to 'Filter' or 'Highlight'.

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
704
Multi-Selecteasy

Which TWO are valid ways to distribute a Power BI report to users who do not have Power BI Pro licenses?

Select 2 answers
A.Share the report via Power BI service sharing.
B.Embed the report in a Power BI app with Premium capacity.
C.Publish to a workspace on a Premium capacity.
D.Export the report as PDF and email it.
E.Publish to web (public).
AnswersB, C

Apps on Premium allow access to free users.

Why this answer

Options A and D are correct. A Power BI Premium capacity allows sharing with free users; a paginated report can be embedded in a Power BI app; B is wrong because sharing directly requires Pro or Premium per user; C is wrong because exporting to PDF requires the user to have access; E is wrong because publishing to web makes it public, not just for non-Pro users.

Full explanation →
705
MCQmedium

You are loading data from a folder containing multiple Excel files with identical structure. Some files have inconsistent column names due to manual edits. You need to ensure that all data is loaded correctly without errors. What should you do in Power Query?

A.Use the 'Combine Files' feature with a sample file, then in the transformation step, promote headers and rename columns using a mapping table.
B.Use 'Merge Queries' to join the files based on row position.
C.Change the data source to a SharePoint folder and use 'Load to Data Model' directly.
D.In Power Query, use 'Enter Data' to manually create the schema.
AnswerA

This approach handles variations by standardizing column names.

Why this answer

Option A is correct because the 'Combine Files' feature in Power Query uses a sample file to infer the schema, and then you can apply transformations like promoting headers and renaming columns using a mapping table to handle inconsistent column names across files. This ensures all data loads without errors by standardizing the column names before combining.

Exam trap

The trap here is that candidates assume 'Combine Files' works automatically without any transformation steps, overlooking the need to handle inconsistent column names, which leads to errors during data load.

How to eliminate wrong answers

Option B is wrong because 'Merge Queries' joins tables based on matching columns or row positions, but it does not resolve inconsistent column names across multiple files; it would fail or produce incorrect results if column names differ. Option C is wrong because changing the data source to a SharePoint folder and using 'Load to Data Model' directly does not address the column name inconsistency; Power Query would still encounter errors when combining files with mismatched headers. Option D is wrong because 'Enter Data' manually creates a static table schema, which cannot dynamically adapt to multiple Excel files with varying column names, and it does not automate the loading process.

Full explanation →
706
MCQhard

You are building a data model for a retail company. The 'Sales' fact table has a column 'Discount' that is a percentage (0 to 1). You create a measure 'Total Discount Amount' = SUM(Sales[Discount]) * SUM(Sales[Quantity]) * SUM(Sales[UnitPrice]). However, the measure returns incorrect results when multiple discount percentages exist in the same filter context. What is the issue?

A.The measure contains a circular dependency.
B.The measure is performing aggregations at the wrong granularity; it should use SUMX to iterate over each row.
C.The measure is referencing columns from different tables without proper relationships.
D.The Discount column should be of type Decimal instead of Percentage.
AnswerB

SUMX ensures row-by-row calculation before summing.

Why this answer

The measure uses SUM on each column individually, which aggregates all values in the filter context before multiplying. When multiple discount percentages exist, this incorrectly multiplies the total of all discounts by the total of all quantities and total of all unit prices, rather than computing discount per row. The correct approach is to use SUMX to iterate over each row of the Sales table, calculating Discount * Quantity * UnitPrice per row and then summing those row-level results, ensuring accurate granularity.

Exam trap

The trap here is that candidates often assume SUM works correctly for all multiplicative measures, overlooking that SUM aggregates before multiplication, while SUMX is required for row-by-row calculations in DAX.

How to eliminate wrong answers

Option A is wrong because a circular dependency occurs when a measure or column references itself directly or indirectly, which is not the case here; the measure simply uses SUM on three columns. Option C is wrong because the measure references columns only from the Sales table, so no cross-table relationship issue exists. Option D is wrong because the data type of Discount (Percentage vs Decimal) does not affect the aggregation logic; the core problem is the aggregation granularity, not the column type.

Full explanation →
707
MCQeasy

You are building a Power BI report that uses a DirectQuery connection to a SQL Server database. You need to reduce the amount of data transferred to Power BI when users interact with visuals. What should you do?

A.Increase the query timeout setting
B.Apply filters in Power Query to reduce rows
C.Disable query reductions
D.Load all data into the Power BI model
AnswerB

Filters in Power Query are pushed down to the source, reducing data transfer.

Why this answer

Option B is correct because applying filters in Power Query reduces the number of rows retrieved from the SQL Server database before the data is transferred to Power BI. With a DirectQuery connection, queries are sent to the source each time a visual is interacted with, so reducing the row count at the query level minimizes network traffic and improves report performance.

Exam trap

The trap here is that candidates often confuse increasing query timeouts or disabling query reductions as performance improvements, when in fact they either do not address data transfer or actively worsen it.

How to eliminate wrong answers

Option A is wrong because increasing the query timeout setting does not reduce data transfer; it only allows longer-running queries to complete without timing out, which can actually increase the amount of data transferred if queries take longer. Option C is wrong because disabling query reductions would remove Power BI's built-in optimizations (like query folding and aggregations) that help minimize data transfer, making the problem worse. Option D is wrong because loading all data into the Power BI model would defeat the purpose of using DirectQuery, which is designed to keep data in the source; importing all data would increase memory usage and initial load time, not reduce data transfer during user interactions.

Full explanation →
708
MCQeasy

Refer to the exhibit. You apply the row-level security (RLS) policy shown to the Sales table. Which rows will be visible to users?

A.Rows where Amount is not blank
B.All rows in the Sales table
C.Only rows where Amount <= 1000
D.Only rows where Amount > 1000
AnswerD

The filter defines this condition.

Why this answer

Option B is correct because the filter only includes rows where Amount > 1000. Option A is wrong because it includes all rows. Option C is wrong because it includes less.

Option D is wrong because it excludes the condition.

Full explanation →
709
Multi-Selecteasy

Which THREE data types are supported in Power Query for Power BI?

Select 3 answers
A.Array
B.Decimal Number
C.Object
D.Text
E.Boolean
AnswersB, D, E

Decimal Number is supported for fractional numbers.

Why this answer

Power Query supports a specific set of primitive data types for columns in Power BI, including Decimal Number, Text, and Boolean. These types are used to define the structure and behavior of data during transformation and loading, ensuring compatibility with the Power BI engine.

Exam trap

The trap here is that candidates often confuse general programming data types (like Array or Object) with Power Query's specific type system, leading them to select options that are not valid in the M language or Power BI's data model.

Full explanation →
710
MCQeasy

You are creating a calculated table in Power BI that contains a list of unique products from the 'Sales' table. Which DAX function should you use?

A.SUMMARIZE(Sales, Sales[Product])
B.VALUES(Sales[Product])
C.DISTINCT(Sales[Product])
D.ALL(Sales[Product])
AnswerC

DISTINCT returns a single column of unique values, ignoring blanks.

Why this answer

Option C is correct because DISTINCT returns a single column of unique values. Option A is wrong because VALUES returns unique values but includes blank if present. Option B is wrong because SUMMARIZE creates a table with multiple columns.

Option D is wrong because ALL returns all rows, ignoring filters.

Full explanation →
711
MCQmedium

You are building a Power BI report for a manufacturing company. You have a large fact table with 50 million rows in Azure SQL Database. You need to minimize the data refresh time and ensure that only new or changed rows are loaded. The source table has a LastModifiedDate column. What should you do?

A.Enable query folding in Power Query to push filters to the source.
B.Configure incremental refresh on the table using the LastModifiedDate column.
C.Schedule a full refresh every hour.
D.Create a Power BI dataflow that performs a full load and then use that dataflow as a source.
AnswerB

Correct. Incremental refresh loads only new/changed data.

Why this answer

Option B is correct because incremental refresh in Power BI allows you to load only new or changed rows from a large fact table by filtering on a date/time column such as LastModifiedDate. This minimizes data refresh time by avoiding a full reload of all 50 million rows, and it leverages the source system's ability to efficiently query only the modified data. Power Query pushes the filter logic to Azure SQL Database via query folding, ensuring optimal performance.

Exam trap

The trap here is that candidates often confuse query folding with incremental refresh, thinking that enabling query folding alone will automatically load only new rows, but query folding only optimizes the pushdown of existing filters—it does not create the filtering logic needed for incremental loading.

How to eliminate wrong answers

Option A is wrong because enabling query folding alone does not limit the data loaded to only new or changed rows; it only ensures that filters are pushed to the source, but without incremental refresh, Power Query would still attempt to load the entire table on each refresh. Option C is wrong because scheduling a full refresh every hour would reload all 50 million rows each time, which is inefficient and contradicts the requirement to minimize refresh time. Option D is wrong because creating a dataflow that performs a full load and then using that dataflow as a source does not reduce the initial data volume or refresh time; it simply adds an extra layer without addressing the need for incremental loading.

Full explanation →
712
Multi-Selectmedium

You are preparing data for a Power BI report that requires a date table with continuous dates from 2020 to 2025. Which TWO methods can you use to create this date table in Power Query?

Select 2 answers
A.Use the 'Enter Data' feature and manually type dates.
B.Use the CALENDAR DAX function in a calculated table.
C.Reference another query that already has dates.
D.Use the List.Dates function to generate a list of dates.
E.Create a blank query and use #date and List.Transform to generate dates.
AnswersD, E

List.Dates generates a date list that can be converted to a table.

Why this answer

Option D is correct because the List.Dates function in Power Query M generates a continuous list of dates by specifying a start date, a count of dates, and a step duration. This list can then be converted into a table, making it ideal for creating a date table directly in Power Query without leaving the data transformation environment.

Exam trap

The trap here is that candidates confuse DAX functions (like CALENDAR) with Power Query M functions (like List.Dates), leading them to select Option B even though the question explicitly restricts the scope to Power Query.

Full explanation →
713
Multi-Selectmedium

Which THREE are valid methods to handle null values in Power Query? (Choose three.)

Select 3 answers
A.Use the 'Fill Down' or 'Fill Up' option to propagate non-null values into null cells.
B.Remove rows that contain null values using the 'Remove Rows' > 'Remove Blank Rows' option.
C.Replace null values with a default value using the 'Replace Values' transform.
D.Merge the table with another table that has no nulls.
E.Change the data type of the column to a non-nullable type.
AnswersA, B, C

Fill Down/Fill Up replaces nulls with the nearest non-null value.

Why this answer

Option A is correct because the 'Fill Down' and 'Fill Up' transforms in Power Query propagate the last non-null value into adjacent null cells within a column. This is a common technique for cleaning data where nulls represent missing values that should inherit the previous or next valid entry, such as in hierarchical or grouped datasets.

Exam trap

The trap here is that candidates may confuse 'Remove Blank Rows' (which removes entire rows where all cells are null) with 'Remove Rows' > 'Remove Blank Rows' (which is actually a valid method to remove rows with nulls in any column, as option B states), but the real pitfall is assuming that changing a data type to non-nullable will automatically handle nulls, which Power Query does not support.

Full explanation →
714
MCQmedium

A company uses Power BI Premium with a capacity-based license. The capacity is frequently reaching its memory limit, causing reports to be evicted. You need to reduce memory pressure on the capacity. What should you do?

A.Enable the 'Large dataset storage format' for all datasets.
B.Move all datasets to a shared capacity.
C.Increase the scheduled refresh frequency to every hour.
D.Implement row-level security (RLS) to limit data loaded per user.
AnswerD

RLS can reduce memory footprint by loading only relevant data.

Why this answer

Option D is correct. Implementing RLS can reduce the amount of data loaded into memory for each user, thus reducing memory pressure. Option A is wrong because increasing the refresh frequency can increase memory usage.

Option B is wrong because enabling 'Large dataset storage format' increases memory usage. Option C is wrong because moving datasets to a shared capacity does not help if the problem is capacity overload.

Full explanation →
715
MCQhard

You are a Power BI developer for a financial services company. The company has a large transactional database in Azure Synapse Analytics. The database contains a table 'Transactions' with 2 billion rows. The table includes columns: TransactionID, AccountID, TransactionDate, Amount, Type (Deposit/Withdrawal), Status (Pending/Completed). You need to build a Power BI semantic model that allows executives to analyze monthly trends of completed deposit amounts by account type (e.g., Savings, Checking). The account type is in a separate 'Accounts' table (1 million rows) with columns: AccountID, AccountType, CustomerID. The model must refresh within 2 hours. Due to the large data volume, you cannot import the entire Transactions table. What should you do?

A.Use incremental refresh to import only recent data, and use DirectQuery for older data.
B.Import only the necessary columns and use Power BI aggregations to pre-aggregate.
C.Use DirectQuery on the full Transactions table and rely on the Synapse query optimizer.
D.Create an aggregated table in Synapse that pre-aggregates data at the month and account type level, then use DirectQuery on the aggregated table, and use a composite model with the detail table for drill-through.
AnswerD

This balances performance and granularity.

Why this answer

Option B is correct because creating an aggregate table in Synapse that pre-computes monthly completed deposit amounts by account type reduces the data volume significantly, and using DirectQuery on the aggregate with the ability to drill down to details via the original table (using composite model or dual storage) provides flexibility. Option A is wrong because DirectQuery on the full table would be slow. Option C is wrong because aggregations in Power BI still require importing the base data.

Option D is wrong because incremental refresh does not reduce the data volume for initial load.

Full explanation →
716
Multi-Selecteasy

Which TWO Power BI components can be used to restrict access to specific rows of data for different users? (Select exactly two.)

Select 2 answers
A.Column-level security (CLS)
B.Bookmark-based filtering
C.Object-level security (OLS)
D.Row-level security (RLS)
E.Dashboard-level permissions
AnswersC, D

OLS can restrict access to entire tables or columns, limiting row access.

Why this answer

Options A and B are correct. Row-level security (RLS) is the primary method to filter data rows by user. Object-level security (OLS) can also restrict access to specific tables or columns, which indirectly restricts rows if applied to tables.

Option C is wrong because column-level security is not a Power BI feature; it's a database concept. Option D is wrong because bookmark-based filtering is not a security feature. Option E is wrong because dashboard-level security controls access to the dashboard, not rows.

Full explanation →
717
Drag & Dropmedium

Drag and drop the steps to create a measure in Power BI Desktop into the correct order.

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

Steps
Order

Why this order

Measures are created in the Modeling tab, require a DAX formula that calculates aggregations, and are then used in visuals.

Full explanation →
718
Multi-Selecteasy

Which TWO data source types can be used with Power BI dataflows?

Select 2 answers
A.Exchange Online mailbox
B.PDF file
C.Power BI dataset
D.SharePoint Online list
E.Azure SQL Database
AnswersD, E

SharePoint lists are supported in dataflows.

Why this answer

SharePoint Online list (Option D) is a correct answer because Power BI dataflows can connect to SharePoint Online lists as a data source, allowing users to ingest list data directly into a dataflow for transformation and loading into the Power BI service. Azure SQL Database (Option E) is also correct because dataflows support Azure SQL Database as a data source, enabling direct extraction of relational data from Azure SQL databases into the dataflow engine for ETL processes.

Exam trap

The trap here is that candidates may confuse the connectors available in Power BI Desktop (which supports PDF and Exchange) with those supported in Power BI dataflows, leading them to select options that are valid in Desktop but not in dataflows.

Full explanation →
719
MCQmedium

Your organization has a Power BI Premium capacity. You need to ensure that data refresh operations for a specific dataset are not interrupted during peak hours. What should you configure?

A.Disable scheduled refresh for the dataset.
B.Set the dataset to 'Refresh now' manually during off-peak hours.
C.Increase the capacity size to a higher SKU.
D.Configure a 'priority' rule in the capacity workload settings for data refresh.
AnswerD

Priority rules allocate resources to high-priority datasets.

Why this answer

Option C is correct because configuring a priority rule for the dataset ensures it gets resources over others. Option A is wrong because it doesn't guarantee resources. Option B is wrong because it prevents refresh entirely.

Option D is wrong because capacity settings affect overall performance, not prioritization.

Full explanation →
720
MCQeasy

You need to audit which users have accessed a specific Power BI dashboard in the last 30 days. What should you use?

A.Microsoft Sentinel.
B.Power BI Activity Log (audit log) in the Microsoft 365 admin center.
C.Microsoft Purview compliance portal.
D.Power BI REST API 'Get Datasets' endpoint.
AnswerB

Activity logs track user access to dashboards.

Why this answer

Option A is correct. The Power BI Activity Log (available via the admin portal or PowerShell) records user access events. Option B is wrong because the Power BI REST API can retrieve activity logs but is not the primary tool.

Option C is wrong because Microsoft Purview compliance portal provides broader auditing but requires integration. Option D is wrong because Microsoft Sentinel is a SIEM tool that can ingest logs but is not the direct source.

Full explanation →
721
MCQeasy

You are a Power BI administrator. A user reports that they are unable to share a dashboard with an external user from a partner organization. The external user has a Microsoft Entra ID account in their own tenant. What is the most likely reason?

A.External users cannot view Power BI content; they need a Power BI license.
B.The 'Share content with external users' tenant setting is disabled.
C.The dashboard is based on a dataset that uses RLS and the external user is not in the role.
D.External users must be added as members in the same tenant.
AnswerB

This setting must be enabled to share with external users.

Why this answer

Sharing with external users requires enabling B2B collaboration in Microsoft Entra ID and configuring Power BI tenant settings to allow sharing with external users. Option A is correct. Option B is wrong because guest user accounts are exactly for this.

Option C is wrong because Power BI guest users can view reports. Option D is wrong because licensing via viral trial is possible.

Full explanation →
722
MCQeasy

You need to create a calculated column in Power BI that categorizes sales amounts as 'Low', 'Medium', or 'High' based on the value. The column should be evaluated row by row. Which DAX function should you use?

A.SWITCH
B.IF
C.CALCULATE
D.FORMAT
AnswerA

Designed for multiple condition evaluation.

Why this answer

Option B is correct. SWITCH is the appropriate DAX function for multiple conditions based on a single expression. Option A (IF) can be nested but is less efficient.

Option C (CALCULATE) modifies filter context, not suitable for row-by-row categorization. Option D (FORMAT) changes data type, not categorization.

Full explanation →
723
MCQmedium

You are designing a Power BI report that will be viewed on mobile devices. The report includes many visuals. What is the best practice for optimizing the report layout for mobile?

A.Create a mobile-optimized layout using the Phone layout view.
B.Use a table visual to display all data.
C.Use bookmarks to navigate between different views.
D.Reduce the number of visuals to one per page.
AnswerA

The Phone layout view allows you to arrange visuals for mobile.

Why this answer

Option D is correct because Power BI Desktop allows you to create a specific mobile layout that adapts visuals for small screens. Option A is wrong because using a single visual may not convey all information. Option B is wrong because reducing visuals may hide important data.

Option C is wrong because bookmarks do not optimize layout.

Full explanation →
724
MCQmedium

You have a report that uses a live connection to a Power BI dataset. You want to add a table visual that shows sales by product, but you notice that you cannot add a calculated column. What is the reason?

A.Live connections require row-level security which prevents calculated columns.
B.Table visuals are not supported with live connections.
C.You need to enable 'Allow calculations' in the dataset settings.
D.Live connections do not support calculated columns; they must be created in the source dataset.
AnswerD

Live connection is read-only; no model changes allowed.

Why this answer

Option A is correct because live connections do not allow adding calculated columns; they must be created in the source dataset. Option B is wrong because table visuals are allowed. Option C is wrong because aggregations are possible.

Option D is wrong because RLS is supported.

Full explanation →
725
Multi-Selectmedium

You are designing a Power BI semantic model for a retail company. The model must support reporting on sales by product, store, and date. You need to decide on the modeling approach. Which TWO actions should you take? (Select exactly two.)

Select 2 answers
A.Create a separate date dimension table and mark it as a date table.
B.Connect the Sales table to Product and Store tables using relationships with many-to-one cardinality.
C.Add calculated columns for year, month, and quarter to the Sales table.
D.Create relationships between tables using the foreign key columns.
E.Combine all data into a single flat table to simplify the model.
AnswersA, B

A date table is required for proper time intelligence and filter context.

Why this answer

Option A is correct because creating a separate date dimension table and marking it as a date table enables time intelligence functions (e.g., TOTALYTD, SAMEPERIODLASTYEAR) to work correctly in DAX. This also ensures that the date column is recognized as a continuous date hierarchy, allowing proper filtering and slicing by year, month, and quarter across all fact tables.

Exam trap

The trap here is that candidates often think adding calculated columns for date parts directly to the fact table is acceptable, but Microsoft explicitly tests the requirement for a separate, marked date table to enable time intelligence and maintain a proper star schema.

Full explanation →
726
MCQhard

You have a Power BI report that uses DirectQuery to a SQL Server database. Users report that the report is slow when filtering by a slicer on a large dimension table. You need to improve performance without changing the data source. Which approach should you take?

A.Create an aggregation table on the dimension
B.Change the storage mode of the dimension table to Dual
C.Set 'Assume Referential Integrity' on the relationship between tables
D.Reduce the cardinality of the slicer field by grouping values
AnswerC

This enables optimized query execution in DirectQuery.

Why this answer

Option C is correct because setting 'Assume Referential Integrity' allows Power BI to use more efficient queries (INNER JOIN instead of OUTER JOIN) when filtering, which improves performance. Option A is wrong because aggregations are not supported in DirectQuery for this scenario. Option B is wrong because reducing cardinality may affect accuracy.

Option D is wrong because dual storage mode does not apply to DirectQuery sources.

Full explanation →
727
MCQeasy

You have a fact table 'Orders' with columns: OrderID, CustomerID, OrderDate, SalesAmount. You also have a 'Calendar' table with Date, Year, Month, Quarter. The Calendar table is marked as a date table. You want to calculate total sales for the current month. Which DAX measure should you use?

A.TOTALYTD(SUM(Orders[SalesAmount]), Calendar[Date])
B.SUM(Orders[SalesAmount])
C.CALCULATE(SUM(Orders[SalesAmount]), DATESMTD(Calendar[Date]))
D.TOTALMTD(SUM(Orders[SalesAmount]), Calendar[Date])
AnswerD

TOTALMTD is a time intelligence function that uses the date table.

Why this answer

Option B is correct because TOTALMTD calculates month-to-date using the date context. Option A is wrong because it's not a function. Option C is wrong because it ignores the date table.

Option D is wrong because it's for year-to-date.

Full explanation →
728
MCQeasy

You need to grant a user the ability to manage permissions on a Power BI workspace but not to view or edit the content. What minimum role should you assign?

A.Contributor
B.Viewer
C.Member
D.Admin
AnswerD

Admin can manage permissions without necessarily viewing content.

Why this answer

Option D is correct because the Admin role allows managing permissions and membership but does not require viewing content. Option A is incorrect because Member can edit content. Option B is incorrect because Contributor can edit content.

Option C is incorrect because Viewer can view content but cannot manage permissions.

Full explanation →
729
Multi-Selectmedium

Which TWO of the following are best practices for designing Power BI reports for accessibility? (Select TWO.)

Select 2 answers
A.Provide alternative text for visuals.
B.Use animations to draw attention.
C.Ensure sufficient color contrast between text and background.
D.Use a variety of colors to differentiate data points.
E.Use small font sizes to fit more data.
AnswersA, C

Alt text helps screen readers.

Why this answer

Option B and Option D are correct. Option A is wrong because using many colors can confuse color-blind users. Option C is wrong because small fonts reduce readability.

Option E is wrong because animations can be distracting.

Full explanation →
730
Multi-Selecthard

Which THREE of the following are required to configure Microsoft Purview Information Protection sensitivity labels for Power BI? (Choose three.)

Select 3 answers
A.Each user must have a Power BI Pro license.
B.Have a Power BI Premium capacity assigned to the workspace.
C.Users must have appropriate permissions (e.g., Azure Information Protection rights) to apply labels.
D.Sensitivity labels must be published in the Microsoft 365 Compliance Center.
E.Enable sensitivity labels in the Power BI admin tenant settings.
AnswersC, D, E

Users need permissions to apply labels, usually via Azure Information Protection.

Why this answer

Options A, C, and D are correct. Sensitivity labels in Power BI require enabling in the tenant settings, having the labels published in Microsoft 365 Compliance Center, and the user must have the appropriate permissions to apply the labels. Option B is wrong because Power BI Premium is not a requirement; labels work in shared capacity too.

Option E is wrong because a Power BI Pro license is required for the user to apply labels, but it's not a configuration step.

Full explanation →
731
Multi-Selectmedium

Which TWO measures will correctly calculate the total sales for the current year, ignoring any filters on the date column? (Assume a proper date table with relationship.)

Select 2 answers
A.CALCULATE(SUM(Sales[Amount]), FILTER(ALL('Date'), YEAR('Date'[Date]) = YEAR(TODAY())))
B.CALCULATE(SUM(Sales[Amount]), DATESYTD('Date'[Date]), ALL('Date'))
C.CALCULATE(SUM(Sales[Amount]), VALUES('Date'[Year]))
D.SUM(Sales[Amount])
E.CALCULATE(SUM(Sales[Amount]), ALL('Date'), 'Date'[Year] = YEAR(TODAY()))
AnswersB, E

DATESYTD with ALL returns YTD for all dates, but still respects year context of filter; with ALL it removes all date filters, but DATESYTD still uses the last date in the date table; this may not be perfect. Actually, correct answer is A and C.

Why this answer

Options A and C are correct. Option A uses DATESYTD with ALL to remove date filters and compute year-to-date. Option C uses CALCULATE with a filter expression that selects all dates in the current year (using YEAR function) and ALL to ignore other filters.

Option B is wrong because it uses VALUES which returns distinct years from the current filter context, not all. Option D is wrong because it sums all rows without year context. Option E is wrong because it uses FILTER incorrectly.

Full explanation →
732
MCQhard

You are a Power BI administrator at Contoso Ltd. The company has a Power BI tenant with Premium capacity. A data analyst has published a dataset that uses DirectQuery mode to a SQL Server database. Users report that the report is slow. You need to improve query performance without changing the data source. You decide to implement a composite model by adding an imported table for a frequently used dimension. After importing, you notice that the relationship between the imported table and the DirectQuery table is Many-to-Many, which causes ambiguity. What should you do to resolve the ambiguity and ensure correct filtering?

A.Remove the imported table and use only DirectQuery.
B.Create a bridge table with a calculated column to create a one-to-many relationship.
C.Use the CROSSFILTER function to ignore the relationship.
D.Change the relationship to One-to-Many (1:*).
AnswerB

This resolves the many-to-many by providing a unique key.

Why this answer

Option B is correct because a bridge table resolves the Many-to-Many ambiguity by creating a separate table that contains only the unique key values from both sides, enabling a star-like schema with one-to-many relationships. This ensures that filters from the imported dimension table propagate correctly to the DirectQuery fact table without ambiguity.

Exam trap

The trap here is that candidates mistakenly think changing the relationship cardinality or using CROSSFILTER can fix Many-to-Many ambiguity, but only a bridge table or a calculated table with unique keys can properly resolve it in a composite model.

How to eliminate wrong answers

Option A is wrong because removing the imported table abandons the performance improvement from caching the frequently used dimension, failing to address the slow report issue. Option C is wrong because the CROSSFILTER function modifies filter direction but does not resolve Many-to-Many ambiguity; it can cause incorrect or missing filtering. Option D is wrong because changing the relationship to One-to-Many (1:*) is impossible when the underlying data inherently has a Many-to-Many cardinality; Power BI will not allow this change without data transformation.

Full explanation →
733
MCQhard

You have a Power BI model with a fact table 'Sales' and dimensions 'Customer', 'Product', 'Date'. You need to enforce that every fact row has a valid CustomerKey. Which approach enforces referential integrity in Power BI?

A.Merge Sales and Customer tables into a single table
B.Hide CustomerKey columns in both tables
C.Assume all CustomerKey values are valid
D.Set the relationship between Sales and Customer to 'Enforce Referential Integrity'
AnswerD

This setting validates that every Sales.CustomerKey exists in Customer.

Why this answer

Option C is correct because marking the relationship as 'Enforce Referential Integrity' in Power BI ensures that only valid keys are used. Option A is wrong because combining tables changes the model structure. Option B is wrong because hiding columns does not enforce integrity.

Option D is wrong because the assumption is not enforced natively.

Full explanation →
734
MCQeasy

A company has a Power BI semantic model that uses DirectQuery to a SQL Server database. The model contains a large fact table with sales data. Users report that reports using this model are slow. Which design change would most improve query performance?

A.Remove all relationships between tables.
B.Switch the model to Import mode.
C.Remove unnecessary columns from the fact table.
D.Disable the 'Reduce queries' option in report settings.
AnswerC

Reducing columns minimizes data retrieved from source, improving query performance.

Why this answer

Option C is correct because removing unnecessary columns from the fact table reduces the amount of data that must be transferred from SQL Server to Power BI for each query. In DirectQuery mode, every report interaction sends a query to the source database, so fewer columns mean smaller result sets and faster query execution. This directly addresses the performance bottleneck caused by a large fact table without changing the underlying storage mode.

Exam trap

The trap here is that candidates often assume switching to Import mode is always the best performance fix, but the question specifically asks for a design change that improves query performance in DirectQuery mode, where reducing column count is a more targeted and less disruptive solution.

How to eliminate wrong answers

Option A is wrong because removing all relationships between tables would break the model's ability to filter and aggregate data across tables, making reports unusable and not improving query performance. Option B is wrong because switching to Import mode would require loading the entire large fact table into memory, which could cause memory pressure and long refresh times, and it does not address the root cause of slow queries in DirectQuery mode. Option D is wrong because disabling the 'Reduce queries' option in report settings would actually increase the number of queries sent to the source, making performance worse, not better.

Full explanation →
735
Multi-Selecteasy

Which TWO actions are required when configuring a Power BI dataset to use incremental refresh?

Select 2 answers
A.Set the dataset storage mode to DirectQuery.
B.Enable query caching on the dataset.
C.Create a calculated table to store the refresh history.
D.Set the incremental refresh policy in the dataset settings.
E.Define rangeStart and rangeEnd parameters in Power Query.
AnswersD, E

Correct. The policy defines the refresh window and detection.

Why this answer

Option D is correct because configuring an incremental refresh policy in the dataset settings is a required step to enable incremental refresh in Power BI. This policy defines how data is partitioned and refreshed incrementally based on date/time columns. Option E is correct because you must define `rangeStart` and `rangeEnd` parameters in Power Query to filter data into historical and incremental ranges, which Power BI uses to generate the refresh partitions.

Exam trap

The trap here is that candidates often confuse the required steps (defining parameters and setting the policy) with optional or unrelated features like query caching or storage mode changes, leading them to select options A or B.

Full explanation →
736
MCQmedium

A data model contains a table 'Sales' with columns: Date, ProductID, Quantity, Amount. There is a 'Products' table with columns: ProductID, ProductName, CategoryID. A measure 'Total Sales' = SUM(Sales[Amount]) returns correct values. However, when a user creates a visual with CategoryID from 'Products' and 'Total Sales', some categories show blank. What is the most likely cause?

A.There are ProductID values in Sales that do not exist in Products table.
B.The 'Total Sales' measure is not properly referencing the Sales table.
C.The relationship between Sales and Products is set to many-to-one, single direction.
D.The relationship is set to both directions (bidirectional).
AnswerA

This causes those rows to have no matching category, resulting in blank category in the visual.

Why this answer

Option A is correct because when ProductID values in the Sales table do not have matching entries in the Products table, the relationship between the two tables will result in blank CategoryID values for those unmatched rows. In Power BI, a many-to-one relationship (the default) filters from the 'one' side (Products) to the 'many' side (Sales), but if a Sales row has a ProductID not present in Products, it cannot be matched, and any column from Products (like CategoryID) will appear as blank in visuals. This is a classic data integrity issue where the fact table contains orphaned foreign keys.

Exam trap

The trap here is that candidates often assume the relationship direction or cross-filter setting is the culprit, but the real issue is data integrity—orphaned foreign keys in the fact table—which is a common data modeling pitfall tested in the PL-300 exam.

How to eliminate wrong answers

Option B is wrong because the measure 'Total Sales' = SUM(Sales[Amount]) explicitly references the Sales table, and the question states it returns correct values, so the measure definition is not the issue. Option C is wrong because a many-to-one, single-direction relationship is the default and correct configuration for this scenario; it does not cause blanks for unmatched rows—it simply means the filter context flows from Products to Sales, but orphaned Sales rows still produce blanks in Products columns. Option D is wrong because bidirectional cross-filtering would not fix the blank issue; it would allow filters to flow in both directions but still cannot match a Sales row with a ProductID that has no corresponding row in Products.

Full explanation →
737
MCQmedium

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

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

Date table marking optimizes time-based queries.

Why this answer

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

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

Full explanation →
738
MCQmedium

You are a data analyst at a retail company. You have a Power BI semantic model that imports sales data from an Azure SQL Database. The database uses a timestamp column to track transaction time. You need to reduce the data refresh time and ensure that only the last 30 days of data are refreshed during each scheduled refresh. You have already created the necessary parameters rangeStart and rangeEnd in Power Query. What should you do next to implement incremental refresh?

A.In the Power BI service, go to the dataset settings and configure the scheduled refresh.
B.In Power Query Editor, apply the rangeStart and rangeEnd filters to the data and then close and apply.
C.In the Power BI service, create a new refresh schedule and set the incremental refresh period.
D.In Power BI Desktop, on the model view, select the table and set the incremental refresh policy.
AnswerD

Correct. Incremental refresh policy is set in the model view table properties.

Why this answer

Option D is correct because incremental refresh policies are defined in Power BI Desktop on the model view, not in the service or by simply filtering in Power Query. After creating the rangeStart and rangeEnd parameters, you must select the table in the Model view, open the incremental refresh policy dialog, and configure the policy to filter data based on those parameters, ensuring only the last 30 days are refreshed.

Exam trap

The trap here is that candidates confuse filtering in Power Query Editor with setting an incremental refresh policy, not realizing that only the latter creates the partitioned refresh behavior required to reduce data refresh time.

How to eliminate wrong answers

Option A is wrong because configuring scheduled refresh in the Power BI service only sets the refresh frequency; it does not implement incremental refresh filtering. Option B is wrong because applying rangeStart and rangeEnd filters in Power Query Editor without setting an incremental refresh policy will still refresh the entire dataset, not just the last 30 days. Option C is wrong because creating a new refresh schedule in the Power BI service does not define incremental refresh; the policy must be set in Power BI Desktop before publishing.

Full explanation →
739
Multi-Selecthard

You are preparing data from a SQL Server database. The query includes a WHERE clause that filters rows based on a date column. You want to ensure that the filter is pushed back to the database (Query Folding). Which THREE conditions must be met?

Select 3 answers
A.The transformations applied must be supported for query folding.
B.All columns from the table must be loaded to the data model.
C.The query must use a DirectQuery connection.
D.The query must not combine data from multiple sources.
E.The source must be a relational database like SQL Server.
AnswersA, D, E

Not all transformations support folding.

Why this answer

Option A is correct because query folding in Power Query requires that all transformations applied to the source data are natively supported by the source database engine. If a transformation (e.g., certain date calculations or custom columns) cannot be translated into a SQL statement, Power Query will break folding and perform the operation locally, negating the performance benefit.

Exam trap

The trap here is that candidates often assume DirectQuery is required for query folding, but folding works in both Import and DirectQuery modes as long as the source and transformations support it.

Full explanation →
740
Multi-Selecteasy

You are importing data from an Excel workbook. The workbook has multiple sheets. You want to combine two sheets that have the same columns but different row data. Which TWO Power Query operations can you use?

Select 2 answers
A.Merge Queries
B.Group By
C.Append Queries
D.Pivot Column
E.Append Queries as New
AnswersC, E

Appends rows of one table to another.

Why this answer

Append Queries and Append Queries as New are both correct because they combine rows from two or more tables with identical columns into a single table. In Power Query, 'Append' is the operation designed for stacking rows vertically, which matches the requirement of combining sheets with the same columns but different row data.

Exam trap

The trap here is that candidates confuse 'Merge' (horizontal join) with 'Append' (vertical union), or think only one of the Append options is valid, but both 'Append Queries' and 'Append Queries as New' are correct operations for combining rows.

Full explanation →
741
MCQhard

Refer to the exhibit. You are implementing a sensitivity label policy in Microsoft Purview for Power BI. The policy shown is intended to block users in the SalesTeam group from exporting reports with the 'Confidential' label to PDF. However, users in SalesTeam can still export PDF. What is the most likely issue?

A.The sensitivity label 'Confidential' has not been applied to the reports.
B.The 'ExportReportToPDF' activity name is incorrect; it should be 'ExportToPDF'.
C.The SalesTeam group does not contain the users.
D.The 'Action' should be 'Deny' instead of 'Block'.
AnswerA

If label not applied, policy does not trigger.

Why this answer

The policy syntax is incorrect; the 'Action' should be 'Block' but the condition needs to be structured correctly. However, the likely issue is that the sensitivity label 'Confidential' is not applied to the reports, or the policy is not published. Option D is correct.

Option A is wrong because the condition is valid. Option B is wrong because 'ExportReportToPDF' is a valid activity. Option C is wrong because the group membership is not necessarily the issue.

Full explanation →
742
MCQeasy

You have a Power BI data model with a 'Sales' fact table and a 'Date' dimension. You need to create a calculated column in the 'Sales' table that shows the fiscal year based on a 'Date' column. The fiscal year starts on July 1. Which DAX expression should you use?

A.SWITCH(TRUE(), MONTH(Sales[Date]) >= 7, YEAR(Sales[Date]), YEAR(Sales[Date])-1)
B.YEAR(Sales[Date])
C.YEAR(Sales[Date]) + 1
D.FORMAT(Sales[Date], "YYYY")
AnswerA

Correctly calculates fiscal year starting July.

Why this answer

Option A is correct because it uses SWITCH with TRUE() to evaluate a logical condition: if the month of the date is July or later (MONTH >= 7), it returns the current year; otherwise, it returns the previous year. This correctly implements a fiscal year starting on July 1, as required.

Exam trap

The trap here is that candidates often assume YEAR() alone is sufficient for fiscal year calculations, overlooking the need to adjust for the fiscal year start month, or they incorrectly add 1 to all years instead of conditionally shifting only the first half of the calendar year.

How to eliminate wrong answers

Option B is wrong because YEAR(Sales[Date]) returns the calendar year, not the fiscal year, so dates from January to June would be assigned to the wrong fiscal year. Option C is wrong because YEAR(Sales[Date]) + 1 always adds one year, which would incorrectly shift all dates forward by one year, not handle the July 1 start. Option D is wrong because FORMAT(Sales[Date], 'YYYY') simply returns the calendar year as a text string, with no fiscal year logic applied.

Full explanation →
743
MCQhard

You are creating a Power BI report that uses a composite model (DirectQuery for large tables and Import for small dimension tables). You want to ensure that measures referencing the DirectQuery tables are responsive. Which of the following design choices should you avoid?

A.Use complex time intelligence measures that iterate over the fact table
B.Use measures that aggregate columns rather than rows
C.Create a date dimension table imported from the source
D.Create user-defined aggregations for the DirectQuery table
AnswerA

Iteration over large DirectQuery tables can be slow.

Why this answer

Using many DAX functions that require iteration over large tables can cause performance degradation in DirectQuery mode. Option D is correct. Option A is acceptable because dimension tables are small.

Option B is a best practice. Option C is acceptable because aggregations can improve performance.

Full explanation →
744
MCQmedium

You have a Power BI report that shows sales by region. The data model contains a 'Sales' fact table and a 'Region' dimension table. When you filter by a specific region, the total sales for that region is correct, but the grand total shows all sales. What is the likely cause?

A.The relationship is set to single cross-filter direction
B.The measure is using SUM instead of SUMX
C.The Region table is not marked as a dimension table
D.The relationship between Sales and Region is inactive
AnswerD

An inactive relationship does not propagate filters, so grand total ignores region filter.

Why this answer

Option A is correct because if the relationship is inactive, filters won't propagate. Option B is wrong because measure calculation is not the issue. Option C is wrong because bidirectional would actually propagate.

Option D is wrong because cross-filter direction is relevant.

Full explanation →
745
Multi-Selecthard

You are designing a Power BI report for the executive team. The report must meet the following requirements: - The report must be accessible to users with visual impairments. - Visuals must automatically adjust to display the most important data when viewed on mobile devices. - Users must be able to drill through from a summary page to a detail page by clicking on a data point. Which three features should you implement?

Select 3 answers
A.Enable 'Use high contrast colors' in the report theme.
B.Enable automatic page refresh for real-time data.
C.Create a drillthrough page with relevant fields.
D.Configure responsive visuals for mobile layout.
E.Use bookmarks to create a drillthrough experience.
AnswersA, C, D

This improves accessibility for users with visual impairments.

Why this answer

Correct: A (enable automatic page refresh ensures real-time data, but actually for accessibility, using high contrast and screen readers is key; however, automatic page refresh is not for accessibility. Wait, the correct answers are B, D, E. Actually, for accessibility, enable 'Use high contrast colors' helps.

For mobile responsiveness, 'Responsive visuals' is correct. For drill through, 'Create a drillthrough page' is correct. Option A (automatic page refresh) is not required for these requirements.

Option C (bookmarks) is for navigation, not drill through.

Full explanation →
746
Multi-Selecteasy

Which TWO of the following are valid methods to create a date table in Power BI?

Select 2 answers
A.Using the 'Create Date Table' button in the ribbon.
B.Using the 'Generate Date Table' option in Power Query.
C.Using the 'Mark as Date Table' feature on an existing table with dates.
D.Manually typing dates in Excel and importing.
E.Using DAX function CALENDARAUTO() in a calculated table.
AnswersC, E

This is a common method.

Why this answer

Option B is correct: using CALENDARAUTO auto-detects date range from model. Option D is correct: marking a table as date table is a standard method. Option A is incorrect because manual typing is not practical.

Option C is incorrect because there is no 'Create Date Table' button. Option E is incorrect because there is no 'Generate Date Table' in the modeling tab.

Full explanation →
747
MCQhard

You are building a Power BI semantic model that combines data from an on-premises SQL Server database and a SharePoint Online list. The SQL Server table contains 10 million rows and updates hourly. The SharePoint list contains 500 rows and updates daily. You need to minimize the data load time and ensure the model refreshes within the scheduled 30-minute window. What should you do?

A.Use DirectQuery for the SQL Server table and Import mode for the SharePoint list.
B.Set both tables to DirectQuery mode.
C.Set the SQL Server table to Dual mode and the SharePoint list to Import mode.
D.Import both tables into the model and disable incremental refresh.
AnswerA

DirectQuery avoids loading the large table into memory, reducing refresh time. Import is suitable for the small SharePoint list.

Why this answer

Option A is correct because using DirectQuery for the large SQL Server table (10M rows, hourly updates) avoids importing all rows into the model, significantly reducing data load time and memory usage. Import mode for the small SharePoint list (500 rows, daily updates) is appropriate since it loads quickly and supports full DAX functionality, while the combination keeps the total refresh within the 30-minute window.

Exam trap

The trap here is that candidates often assume Import mode is always best for performance, but for very large tables with frequent updates, DirectQuery avoids the bottleneck of importing millions of rows, while small tables are better imported to avoid live query overhead.

How to eliminate wrong answers

Option B is wrong because setting both tables to DirectQuery mode would force the SharePoint list to be queried live, which can introduce latency for each report interaction and may not support all DAX functions, plus it doesn't leverage the small size of the SharePoint data for fast import. Option C is wrong because Dual mode is designed for tables that need to serve both as a dimension table in Import mode and as a DirectQuery source, but it doesn't solve the load-time issue for the large SQL Server table—it still requires importing the data, which would exceed the 30-minute window. Option D is wrong because importing both tables, even with incremental refresh disabled, would require loading the full 10M rows from SQL Server on each refresh, which is likely to exceed the 30-minute window and consume excessive memory.

Full explanation →
748
MCQhard

You are designing a report for executives. The report contains a matrix visual with many rows and columns. Users complain that the visual is slow to render. Which design change would most improve performance?

A.Switch to a table visual.
B.Add more filters to the visual.
C.Use a drill-down hierarchy instead of expanding all levels.
D.Increase the number of measures in the matrix.
AnswerC

This reduces the initial data load and improves rendering time.

Why this answer

Aggregating data at a higher level reduces the number of data points, improving performance. Drilling down can still provide detail when needed.

Full explanation →
749
Multi-Selecteasy

Which TWO visuals are most suitable for showing the distribution of a single numeric variable? (Choose two.)

Select 2 answers
A.Pie chart
B.Scatter chart
C.Box and whisker plot
D.Histogram
E.Bar chart
AnswersC, D

Box plots show distribution and outliers.

Why this answer

A and D are correct for distribution. B is for correlation, C is for parts of a whole, and E is for comparing categories.

Full explanation →
750
MCQmedium

You create a report that uses an AI visual to find key influencers. Which type of field can the AI visual analyze as the 'analyze' field?

A.A date field
B.A binary Yes/No field
C.A numeric field such as sales amount
D.A categorical text field
AnswerC

Key influencers require a numeric field to analyze.

Why this answer

The Key Influencers visual analyzes a numeric field (measure or column) to determine what influences its value.

Full explanation →
Page 9

Page 10 of 13

Page 11

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 →