Free Microsoft PL-300 Practice Test Questions MCQs

Stop wondering if you're ready. Our Microsoft PL-300 practice test is designed to identify your exact knowledge gaps. Validate your skills with Microsoft Power BI Data Analyst questions that mirror the real exam's format and difficulty. Build a personalized study plan based on your free PL-300 exam questions mcqs performance, focusing your effort where it matters most.

Targeted practice like this helps candidates feel significantly more prepared for Microsoft Power BI Data Analyst exam day.

22900+ already prepared
Updated On : 25-May-2026
290 Questions
Microsoft Power BI Data Analyst
4.9/5.0

Page 1 out of 29 Pages

Topic 1, Litware, Inc. Case Study

   

This is a case study. Case studies are not timed separately. You can use as much exam
time as you would like to complete each case. However, there may be additional case
studies and sections on this exam. You must manage your time to ensure that you are able
to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information
that is provided in the case study. Case studies might contain exhibits and other resources
that provide more information about the scenario that is described in the case study. Each
question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review
your answers and to make changes before you move to the next section of the exam. After
you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the
left pane to explore the content of the case study before you answer the questions. Clicking
these buttons displays information such as business requirements, existing environment
and problem statements. If the case study has an All Information tab, note that the
information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the
question.
Overview
Litware, Inc. is an online retailer that uses Microsoft Power Bl dashboards and reports.
The company plans to leverage data from Microsoft SQL Server databases, Microsoft
Excel files, text files, and several other data sources.
Litware uses Azure Active Directory (Azure AD) to authenticate users.
- Existing Environment
Sales Data
Litware has online sales data that has the SQL schema shown in the following table.

In the Date table, the dateid column has a format of yyyymmdd and the month column has
a format of yyyymm. The week column in the Date table and the weekid column in the
Weekly_Returns table have a format of yyyyww. The regionid column can be managed by
only one sales manager.
Data Concerns
You are concerned with the quality and completeness of the sales data. You plan to verify
the sales data for negative sales amounts.
Reporting Requirements
Litware identifies the following technical requirements:
• Executives require a visual that shows sales by region.
• Regional managers require a visual to analyze weekly sales and returns.
• Sales managers must be able to see the sales data of their respective region only.
• The sales managers require a visual to analyze sales performance versus sales targets.
• The sale department requires reports that contain the number of sales transactions.
• Users must be able to see the month in reports as shown in the following example: Feb
2020.
• The customer service department requires a visual that can be filtered by both sales
month and ship month independently.

You have a Power BI data model that contains the following three tables:

Sales
Date
Product

The Sales table is related to the Date and Product tables by using many-to-one relationships. The Sales table contains a column named Total Sales Amount. You need to create a measure named Total Sales that can be used in visuals to aggregate Total Sales Amounts by product or by date. What should you use? (Select only one answer.)

A. Total Sales = ALL (‘Sales’[Total Sales Amount])

B. Total Sales = CALCULATE ([Total Sales])

C. Total Sales = MAX(‘Sales’[Total Sales Amount])

D. Total Sales = SUM(‘Sales’[Total Sales Amount])

D.   Total Sales = SUM(‘Sales’[Total Sales Amount])

Explanation:
The goal is to create a measure that correctly aggregates (sums up) the Total Sales Amount column, and whose result will change dynamically based on the filters and slicers coming from the related Date and Product tables.

Let's analyze each option:
A. Total Sales = ALL (‘Sales’[Total Sales Amount]):
This is incorrect. The ALL function is used to remove filters, not to perform an aggregation. This formula does not sum the values; it returns a table of all the values in the column, which is not a single numeric result suitable for a measure.

B. Total Sales = CALCULATE ([Total Sales]):
This is incorrect and creates a circular reference. The measure [Total Sales] is being defined in terms of itself, which will result in an error. CALCULATE is a powerful function for modifying filter context, but it needs a valid expression to evaluate, which is missing here.

C. Total Sales = MAX(‘Sales’[Total Sales Amount]):
This is incorrect. The MAX function returns the largest value in the Total Sales Amount column. While this is a valid aggregation, it does not fulfill the requirement to calculate the "total" (i.e., the sum) of the sales amounts. It would only ever show the single highest sale value.

D. Total Sales = SUM(‘Sales’[Total Sales Amount]):
This is correct. The SUM function adds up all the values in the Total Sales Amount column. When this measure is placed in a visual (e.g., a bar chart by product or a line chart by date), the built-in relationships in the data model automatically apply the correct filters. For example, when a specific product is selected, the SUM will only include sales records related to that product.

Reference:
Core Concept:
This question tests the fundamental understanding of measures and aggregation functions (like SUM, AVERAGE, COUNT) in DAX.
Model Behavior:
It also tests the understanding of how the filter context from relationships flows from the "one" side (Date, Product) to the "many" side (Sales) table. The SUM measure respects this filter context, making it dynamic.

You need to create a Power Bl theme that will be used in multiple reports. The theme will include corporate branding for font size, color, and bar chart formatting. What should you do?

A. Create a theme as a PBIVIZ file and import the theme into Power Bl Desktop.

B. Create a theme as a JSON file and import the theme into Power Bl Desktop.

C. From Power Bl Desktop, use a built-in report theme.

D. From Power Bl Desktop, customize the current theme.

B.   Create a theme as a JSON file and import the theme into Power Bl Desktop.

Explanation:
The core requirement is reusability across multiple reports with specific corporate branding that includes granular control over elements like bar chart formatting. The JSON file method is the only option designed by Microsoft to fulfill this exact purpose efficiently and consistently.
Here is a detailed analysis of why the other options are incorrect and why option B is the definitive solution:

A. Create a theme as a PBIVIZ file and import the theme into Power BI Desktop.
Why it is incorrect: A .pbiviz file is a Power BI Visual package file. It is the output of a custom visual development project and is used to import a single custom visual (like a unique chart type) into Power BI. It is not a container for theme information (colors, fonts, backgrounds). Using a PBIVIZ file to apply a theme is not a supported or functional procedure. This option confuses the file format for custom visuals with the file format for report themes.

C. From Power BI Desktop, use a built-in report theme.
Why it is incorrect:
Power BI Desktop includes several pre-defined, built-in themes (e.g., "Solarized," "Electric," "Modern"). While these are useful for quickly changing the look of a single report, they are fundamentally generic. They do not contain your organization's specific corporate color palette, font choices, or customized bar chart settings. This option offers no mechanism for defining or applying custom branding, making it unsuitable for enforcing corporate standards across multiple reports.

D. From Power BI Desktop, customize the current theme.
Why it is incorrect (for this scenario): This option is partially correct in its actions but fails the primary requirement of reusability. The "Customize current theme" feature in the Power BI Desktop UI is the perfect tool for creating a theme for the current, open report. You can define all the required corporate branding elements there. However, the critical next step for reuse is to export these settings as a JSON file. If you only customize the theme in one report, you would have to manually repeat every single customization (colors, fonts, etc.) in every new report. This is inefficient, prone to human error, and leads to branding inconsistencies. Option D describes a manual, one-off process, whereas the question demands a scalable, reusable solution.

Why Option B is Correct:
A JSON (JavaScript Object Notation) file is the standard, supported format for creating, saving, and sharing Power BI report themes. It is a text-based file that uses a specific schema to define properties for the entire report's appearance.

The process works as follows:
Creation:
You create a .json file that defines your corporate branding. This can be done by manually writing the JSON code using Microsoft's schema or, more practically, by using the "Customize current theme" UI (Option D) in a single report and then using the "Save current theme" option, which exports your settings to a JSON file.
Reusability:
This single JSON file becomes your corporate theme asset. It can be stored in a shared location.
Application:
Any report author can import this JSON file into any Power BI Desktop report via the "Browse for themes" option. This instantly applies all the corporate colors, fonts, and visual-specific formatting (like the bar chart colors mentioned in the question) to the new report.
This method guarantees visual consistency, streamlines the report creation process, and centrally manages corporate branding. If the brand guidelines change, you can update the master JSON file and redistribute it.

References
Microsoft Learn:
Create and use report themes in Power BI Desktop This is the primary official documentation. It explicitly explains how to create, export (save as a JSON file), and import JSON theme files.
Microsoft Learn:Report theme JSON file format
This document details the complete schema for the JSON file, showing how to define colors for specific visual types (like bar charts), data colors, font families, and font sizes.

You are modifying a Power Bi model by using Power Bl Desktop.
You have a table named Sales that contains the following fields.



Explanation:
This DAX formula creates a calculated column that classifies each transaction as Small, Medium, or Large by comparing the transaction’s Sales Amount with the Min and Max boundaries in the Transaction Size table.

Let’s break it down step-by-step:
VAR SalesTotal = 'Sales'[Sales]
Stores the current transaction’s sales value.
VAR FilterSegment = FILTER(...)
Filters the 'Transaction Size' table to return only the row(s) where the SalesTotal value falls between Min and Max.
The logical operator && ensures both conditions are true simultaneously.
VAR Result = CALCULATE(DISTINCT(...), FilterSegment)
Evaluates which segment name (Small, Medium, or Large) corresponds to the filtered segment.
CALCULATE changes the filter context to the one defined by FilterSegment.
DISTINCT returns the single matching Transaction Size value.
RETURN Result

Outputs the segment name as the classification.
Why Each DAX Function Fits Correctly: Placeholder Correct Value Purpose
1st blank FILTER Applies filtering logic on 'Transaction Size'
2nd blank AND (represented by &&) Ensures both min and max conditions are met
3rd blank CALCULATE Evaluates expression under filtered context

Final Matching Answer Sequence:
FILTER
AND
CALCULATE

Reference:
📘 Microsoft Learn – DAX CALCULATE function
📘 Microsoft Learn – DAX FILTER function

Summary:
To classify transactions by size in Power BI, use a FILTER function to find the correct range, the AND (&&) operator for conditional checks, and CALCULATE with DISTINCT to return the segment label.

You have a Power Bl report
You have a table named Dalai that contains 10 million rows. Data is used in the following visuals: • A card that shows the number of records
• A bar chart that snows total transaction amount by territory
• A scatter plot that shows transaction amount and profit amount on the axes and points colored by territory
You need to modify the scatter plot to make it easier for users to identify meaningful patterns. The solution must not affect the accuracy of the other visuals-What should you do?

A. Apply a row filter to the Dalai query in Power Query Editor.

B. Add a trend line to the scatter plot.

C. Enable high-density sampling on the scatter plot.

D. Add a count field of the transaction amount to the size bucket of the scatter plot.

B.   Add a trend line to the scatter plot.

📘 Explanation:
To help users identify meaningful patterns in a scatter plot—especially when visualizing relationships between two measures like transaction amount and profit—adding a trend line is the most effective solution. A trend line reveals correlation, direction, and strength of the relationship between variables, making patterns immediately visible without altering the underlying data. This approach is purely visual and does not affect the accuracy of other visuals like the card or bar chart. It enhances interpretability without filtering or sampling the dataset.
Reference:
🔗 Microsoft Learn – Add a trend line to a scatter chart

❌ Why other options are incorrect:
A. Apply a row filter to the Dalai query in Power Query Editor
This would reduce the dataset for all visuals, not just the scatter plot, violating the requirement to preserve accuracy elsewhere.


C. Enable high-density sampling on the scatter plot
High-density sampling improves performance for large datasets but may omit data points, potentially hiding patterns. It’s useful for rendering speed, not pattern detection. 🔗 Microsoft Learn – High-density sampling in scatter charts

D. Add a count field of the transaction amount to the size bucket of the scatter plot
This changes the size of data points, which may help with emphasis but does not reveal trends or relationships between measures.

📘 Summary:
Adding a trend line is the only option that enhances pattern recognition in the scatter plot without compromising the accuracy or integrity of other visuals. It’s a best-practice feature for analytical clarity in Power BI.

You are creating a Power BI model that contains a table named Store. Store contains the following fields. You plan to create a map visual that will show store locations and provide the ability to drill down from Country to State/Province to City. What should you do to ensure that the locations are mapped property?

A. Set the data category of City. State/Province, and Country.

B. Set Summarization for City. State/Province, and Country to Don't summarize.

C. Change the data type of City. State/Province, and Country.

D. Create a calculated column that concatenates the values it City, State/Province, and Country.

A.   Set the data category of City. State/Province, and Country.

Explanation:
The requirement is to create a map visual that supports a geographic hierarchy for drill-down (Country -> State/Province -> City). For Power BI to correctly interpret and plot these fields on a map, it must recognize them as geographic entities, not just simple text strings.
Let's analyze why setting the data category is the correct and essential step:

Why Option A is Correct:
Power BI uses two properties for a field: Data Type (e.g., Text, Whole Number) and Data Category. The Data Category provides the semantic meaning behind the data. By setting the Data Category:
Country field is categorized as Country/Region.
State/Province field is categorized as State or Province.
City field is categorized as City. This explicit categorization tells Power BI's mapping engine (powered by Bing) exactly how to interpret the text in these columns. Once these categories are set, you can easily build a drill-down hierarchy in a map visual by dragging these fields in the correct order (Country, then State/Province, then City) into the "Location" or "Drillthrough" well. The map will then automatically zoom and filter as users drill down.

Why the Other Options Are Incorrect:
B. Set Summarization for City, State/Province, and Country to Don't summarize.
This is good practice for non-numeric fields to prevent Power BI from accidentally trying to sum or average them, but it does not help the map visual recognize the geographic nature of the data. A field with "Don't summarize" is still treated as a simple text field by the map if its Data Category isn't set.

C. Change the data type of City, State/Province, and Country.
The data type for these fields should already be "Text", which is correct. Changing it to another type (like a number) would be meaningless and break the model. The core issue is not the data type but the semantic meaning, which is handled by the Data Category.

D. Create a calculated column that concatenates the values in City, State/Province, and Country.
This is an inefficient and often unreliable workaround. While you could create a single column like "City, State, Country" and set its Data Category to "Address", it is messy and does not natively support the drill-down hierarchy. You would lose the ability to seamlessly drill from a country view to a state view. The built-in hierarchy using individual, properly categorized fields is the cleanest and most functional approach.

Reference:
Core Concept: This question tests the understanding of Data Categories in Power BI, which are essential for correct visualization in maps, as well as with other intelligent features.

Official Documentation:
Microsoft documentation clearly states that to plot locations correctly on a map, you must assign the appropriate data categories.

Title:
Tips and tricks for color formatting in Power BI

Relevant Excerpt:
"To make sure maps, backgrounds, and other geographic features visualize correctly, assign a data category. The data category tells Power BI what kind of data is in the column, so it can display the data correctly on a map."

Exhibit:



Explanation:
The question asks for a report that:
Visualizes Sales value over years and months, and Adds Slicers for both Year and Month.
That means the data must be in a normalized/tabular format (i.e., “long format”) — not wide with separate columns for each year.

Step-by-Step Breakdown
Step 1: Select the 2019, 2020, and 2021 columns
These columns represent yearly sales values that need to be transformed.
Selecting them prepares Power Query to perform the next operation correctly.

Step 2: Unpivot other columns
Converts the wide dataset (where years are columns) into a long format, producing:
Attribute column (which will hold year values such as 2019, 2020, 2021)
Value column (which will hold the corresponding sales amounts)
This is essential so that you can slice by year and month.

Step 3: Rename columns
Rename Attribute → Year
Rename Value → Sales
After renaming, you’ll have fields Year, Month, and Sales, which can be used to:
Create a line or column chart for sales over time
Add slicers for both Month and Year

Why the Other Actions Are Not Used
Select Transpose: ❌
This would swap rows and columns entirely — not appropriate for time-series data.
Select the Month and MonthNumber columns: ❌
These columns are already fine as they are; you don’t need to unpivot them.

Final Answer Sequence
1.Select the 2019, 2020, and 2021 columns
2.Select Unpivot other columns
3.Rename the Attribute column as Year and the Value column as Sales

Reference:
📘 Microsoft Learn — Unpivot columns in Power Query

Summary:
Unpivoting the year columns and renaming them gives you the correct structure for building visuals and slicers for Year and Month in Power BI.

You are building a Power Bl report.
Users will view the report by using their mobile device.
You need to configure the report to display data based on each user s location.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

A. For the relevant columns, set synonyms to match common geographical terms.

B. From Power Query Editor, detect the data types of the relevant columns.

C. Use the columns of the geography data type in all visuals.

D. Create a hierarchy for columns of the geography data type.

E. In Data Category, set the geographic data category for the relevant columns.

C.   Use the columns of the geography data type in all visuals.
E.   In Data Category, set the geographic data category for the relevant columns.

📘 Explanation:
To enable location-based filtering in Power BI mobile reports, the report must include geographic data that Power BI can recognize and match to the user's device location. This requires:

✅ C. Use the columns of the geography data type in all visuals
Power BI mobile apps can apply geo-filters only when visuals use fields categorized as geographic (e.g., Country, State, City). These fields must be present in the visuals for location-based filtering to activate.

✅ E. In Data Category, set the geographic data category for the relevant columns
You must explicitly set the Data Category for each geographic column (e.g., City, State, Country) in Power BI Desktop. This tells Power BI how to interpret the data and enables mobile geo-filtering.

Steps:
Select the column in Power BI Desktop
Go to “Column tools” > “Data Category”
Choose the appropriate geographic category (e.g., City, Country)

Reference :
🔗 Microsoft Learn – Filter report by geographic location in Power BI mobile app
🔗 DataFlair – Power BI Data Category and Geographic Filters

❌ Why other options are incorrect:
A. Set synonyms to match common geographical terms
Synonyms are used for Q&A natural language queries, not for enabling location-based filtering.

B. Detect data types in Power Query Editor
Detecting data types helps with modeling but does not assign geographic meaning required for mobile geo-filters.

D. Create a hierarchy for geography columns
Hierarchies improve drill-down navigation but are not required for enabling location-based filtering.

📘 Summary:
To support mobile geo-filtering, use geographic columns in visuals and assign proper Data Category settings. This ensures Power BI can match report data to the user's location and apply filters accordingly.

You are creating a query to be used as a Country dimension in a star schema.
A snapshot of the source data is shown in the following table.

You need to create the dimension. The dimension must contain a list of unique countries.
Which two actions should you perform? Each correct answer presents part of the solution.

A. Remove duplicates from the Country column.

B. Remove duplicates from the City column.

C. |Remove duplicates from the table.

D. Delete the City column.

E. Delete the Country column.

A.   Remove duplicates from the Country column.
D.   Delete the City column.

Explanation:
You’re creating a Country dimension table for a star schema in Power BI. A dimension table should contain unique keys or attributes—in this case, one record per country.
The source table includes repeated country names because multiple cities belong to each country. To make it a proper Country dimension, you must ensure that only unique countries remain.

Step-by-Step Solution
1️⃣ Delete the City column (Option D)
The City column is not needed in the Country dimension; it belongs to a City dimension or Fact table.
Keeping it would cause duplicate country entries.

2️⃣ Remove duplicates from the Country column (Option A)
Once the City column is deleted, multiple identical Country rows may still exist.
Use Remove Duplicates on the Country column in Power Query to keep only unique countries (USA, UK, Japan, Brazil).
After these two steps, the dimension table will look like:

Country
USA
UK
Japan
Brazil
This is a clean Country dimension suitable for star schema design.

Why the Other Options Are Incorrect
B. Remove duplicates from the City column: ❌
Cities are not unique globally (e.g., “London” can exist in multiple countries). Removing duplicates here does not help create a unique Country list.

C. Remove duplicates from the table: ⚠️
This could remove rows based on both columns together — you’d still have repeated countries because each country has multiple cities.

E. Delete the Country column: ❌
Deleting the key attribute (Country) defeats the purpose; you need it for the dimension table.

Reference:
📘 Microsoft Learn — Design a star schema in Power BI
📘 Microsoft Learn — Remove duplicates in Power Query

✅ Summary:
To create a Country dimension from the given table:
Delete the City column (D)
Remove duplicates from the Country column (A)

You have a Power Bl report that contains a page. The page contains the following:
• A shape named Shape 1
• A card named Sales Summary
• A clustered bar chart named Sales by Region
You need to ensure that Sales Summary renders on top of Shape 1. What should you modify?

A. Tab order in the Selection pane

B. Layer order in the Selection pane

C. Maintain layer order in the General visual settings

D. Vertical alignment in the Canvas settings

B.   Layer order in the Selection pane

You use Power Query Editor to preview the data shown in the following exhibit.
You confirm that the data will always start on row 3, and row 3 will always contain the column names. You use Power Query Editor to preview the data shown in the following exhibit.

A screenshot of a computer.
Description automatically generated with medium confidence


Explanation:
The requirement is to control which visual appears on top of another when they overlap on the report canvas. This is a classic design task related to the z-order (stacking order) of objects.
Let's analyze why adjusting the layer order is the correct solution and why the other options do not apply:

Why Option B is Correct:
In Power BI, the Selection pane (View > Selection pane) lists all the objects on the current report page. The order of the items in this pane directly defines their layer order. Objects at the top of the list are rendered "behind" objects lower down in the list. Objects at the bottom of the list appear "on top" of others.
To make the Sales Summary card render on top of Shape 1, you would simply drag the Sales Summary item to a position below the Shape 1 item in the Selection pane list. This action explicitly controls the visual hierarchy.

Why the Other Options Are Incorrect:
A. Tab order in the Selection pane:
This controls the sequence in which a user navigates through visuals using the Tab key on their keyboard, which is crucial for accessibility. It has absolutely no effect on the visual stacking order (z-index) of the objects.

C. Maintain layer order in the General visual settings:
This is a misleading option. There is no setting named "Maintain layer order" in the general format settings of a visual. The layer order is dynamically managed only within the Selection pane itself.

D. Vertical alignment in the Canvas settings:
This refers to the page-level settings for aligning the entire report page canvas within the browser or app window (e.g., aligning it to the top, center, or bottom of the viewport). It controls the position of the entire canvas, not the relative layering of individual objects placed upon it.

Reference:
Core Concept:
This question tests the knowledge of the Selection pane in Power BI Desktop, specifically its dual functionality for managing both Tab Order (for accessibility) and Layer Order (for visual design).
Official Documentation:
While basic, this functionality is covered in Microsoft's documentation on report authoring.
Title:
Tips for designing compelling Power BI reports
Relevant Concept:
Using the Selection pane to manage which visuals are in front of or behind others.

You have a Power BI workspace named BI Data that contains a dataset named BI Finance. You have the Build permission for the 81 Finance dataset but you do NOT have permissions for the workspace, You need to connect to BI Finance and create a report. Which actions should you perform? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

A. From the Power BI service, create a dataflow to the dataset by using DirectQuery.

B. From Power BI Desktop, connect to a Dataverse data source.

C. From the Power BI service, create a new report and select a published dataset

D. From Power Bl Desktop, connect to a shared dataset

C.   From the Power BI service, create a new report and select a published dataset
D.   From Power Bl Desktop, connect to a shared dataset

Explanation:
In Power BI, if you have Build permission on a dataset (even without workspace access), you can create reports using that dataset. The Build permission allows users to:
Create new reports in Power BI Service or Power BI Desktop
Access and analyze the dataset’s underlying data in supported tools (e.g., Excel or Power BI)

Answer Breakdown
✅ C. From the Power BI service, create a new report and select a published dataset
You can go to the Power BI Service → BI Data workspace → BI Finance dataset.
Even without workspace access, with Build permission, you can choose “Create → Report” and build a report directly from that published dataset in the browser.
Path:
Power BI Service → Dataset → “Create Report”

✅ D. From Power BI Desktop, connect to a shared dataset
In Power BI Desktop, you can connect to a dataset that has been shared with you via Build permissions.
Use the option:
Home → Get Data → Power BI datasets
Then select the BI Finance dataset and build your report.
This connection works in Live Connection mode, meaning:
Data modeling is not possible (you can’t add new calculated columns/tables)
You can only create visuals and measures in your report layer

Why the Other Options Are Incorrect
A. Create a dataflow to the dataset by using DirectQuery: ❌
Power BI dataflows are used to prepare and transform data, not connect to or query existing datasets. You can’t create a dataflow to a dataset.

B. Connect to a Dataverse data source: ❌
The dataset here is BI Finance, not Microsoft Dataverse. Dataverse connections are unrelated to this scenario.

Reference:
📘 Microsoft Learn — Dataset permissions in Power BI
📘 Microsoft Learn — Connect to Power BI datasets in Power BI Desktop

✅ Summary:
Since you have Build permission (but no workspace access), you can create reports by:
(C) Creating a new report from the dataset directly in Power BI Service, or
(D) Connecting to the shared dataset in Power BI Desktop.

Page 1 out of 29 Pages
Next
123456789

Microsoft Power BI Data Analyst Practice Exam Questions

These PL-300 practice questions with explanations help candidates learn how to analyze and visualize data using Power BI. Topics include data modeling, transformation, DAX, and report creation. Each question is followed by a clear explanation that helps learners understand analytical concepts and best practices. This approach improves both theoretical understanding and practical skills. By practicing consistently, candidates can strengthen their data analysis abilities and confidently prepare for the certification exam.

PL-300 - Microsoft Power BI Data Analyst Official Exam Blueprint and Weight:

1. Prepare the Data
Official Exam Weight: 25-30%
Subtopics: Identify and connect to data sources or shared semantic model, change data source settings including credentials and privacy levels, choose between DirectLake DirectQuery and Import, create and modify parameters, evaluate data including data statistics and column properties, resolve inconsistencies unexpected or null values and data quality issues, resolve data import errors, select appropriate column data types, create and transform columns, group and aggregate rows, pivot unpivot and transpose data, convert semi-structured data to table, create fact tables and dimension tables, identify when to use reference or duplicate queries and resulting impact, merge and append queries, identify and create appropriate keys for relationships, configure data loading for queries.

2. Model the Data
Official Exam Weight: 25-30%
Subtopics: Configure table and column properties, implement role-playing dimensions, define relationship cardinality and cross-filter direction, create common date table, identify use cases for calculated columns and calculated tables, create single aggregation measures, use CALCULATE function, implement time intelligence measures, use basic statistical functions, create semi-additive measures, create measure using quick measures, create calculated tables or columns, create calculation groups, improve performance by identifying and removing unnecessary rows and columns, identify poorly performing measures relationships and visuals using Performance Analyzer and DAX query view, improve performance by reducing granularity.

3. Visualize and Analyze the Data
Official Exam Weight: 25-30%
Subtopics: Select appropriate visual, format and configure visuals, create narrative visual with Copilot, apply and customize theme, apply conditional formatting, apply slicing and filtering, use Copilot to create new report page, use Copilot to suggest content for new report page, configure report page, choose when to use paginated report, create visual calculations using DAX, configure bookmarks, create custom tooltips, edit and configure interactions between visuals, configure navigation for report, apply sorting to visuals, configure sync slicers, group and layer visuals using Selection pane, configure drillthrough navigation including pages filters and buttons, configure export settings, design reports for mobile devices, enable personalization in report including personalized visuals, design and configure Power BI reports for accessibility, configure automatic page refresh, use Analyze feature in Power BI, use grouping binning and clustering, use AI visuals, use reference lines error bars and forecasting, detect outliers and anomalies, use Copilot to summarize underlying semantic model.

4. Manage and Secure Power BI
Official Exam Weight: 15-20%
Subtopics: Create and configure workspace, configure and update app, publish import or update items in workspace, create dashboards, choose distribution method, configure subscriptions and data alerts, promote or certify Power BI content, identify when gateway is required, configure semantic model scheduled refresh, assign workspace roles, configure item-level access, configure access to semantic models, implement row-level security roles, configure row-level security group membership, apply sensitivity labels.


Domain Title Exam Weight
1 Prepare the Data 25-30%
2 Model the Data 25-30%
3 Visualize and Analyze the Data 25-30%
4 Manage and Secure Power BI 15-20%

PL-300 Power BI Data Analyst: The Efficient Path to Pass


The PL-300 validates your ability to transform raw data into actionable insights using Power BI. Success hinges on mastering four core workflows that mirror real-world tasks.

1. Prepare Data (Power Query): You must expertly connect, clean, and shape data in the Power Query Editor. Proficiency in M code for complex transformations is a key advantage.
2. Model Data (DAX & Relationships): This is the analytical engine. Build efficient star-schema models and write accurate DAX calculations for measures and time intelligence.
3. Visualize & Analyze (Storytelling): Select the right visuals to create clear, interactive reports. Implement bookmarks, drill-throughs, and basic analytics features.
4. Deploy & Maintain (Service): Know how to publish to the Power BI Service, manage workspaces, configure dashboards, and implement row-level security (RLS).

Your 4-Week Action Plan:


Weeks 1-2: Learn by Doing. Immediately start building reports in Power BI Desktop with real data. Follow the end-to-end process while completing the official Microsoft Learn modules.

Week 3: Practice with Strategy. Use a platform like MSMCQ.com for scenario-based questions. Treat each as a mini-case study to understand the why behind answers, especially for DAX and modeling logic. This builds exam intuition.

Week 4: Final Polish. Focus on DAX fluency and Power BI Service navigation. Take a timed mock exam to build stamina.

Critical Insight: The exam tests the "Power BI Way." The correct answer is often the most efficient, native approach (e.g., using a quick measure vs. complex DAX). Your hands-on project experience and targeted practice with realistic questions are the direct drivers of success.

Our Happy Customers


Data visualization and modeling preparation improved greatly with MSmcqs PL-300 practice questions for Microsoft Certified: Power BI Data Analyst Associate. The mock exams felt very close to the real certification test.
Rafael Mendes | Brazil