These ten original practice scenarios are designed to help aspiring Power BI data analysts reason through realistic reporting decisions. They are not recalled Microsoft examination questions and do not promise to reproduce the live test. Each item has four choices, one best answer under the stated assumptions, an explanation of the alternatives, and a small hands-on exercise. Read the situation first, choose your answer before viewing the explanation, and then test the underlying principle in your own permitted Power BI environment.
The Microsoft PL-300 skills measured as of April 20, 2026 span data preparation (25–30%), data modeling (25–30%), visualizing and analyzing data (25–30%), and managing and securing Power BI (15–20%). The cases below cover all four areas rather than claiming to predict the exact mix you will receive. Review the current PL-300 exam scope and the official Microsoft Learn study guide when scheduling, because product features and assessed details can change.
Question 1: Choosing a sensible storage mode
A retail team stores two years of transactions in Azure SQL Database. Business users need a consolidated sales report updated every morning, not second-by-second results. The model fits comfortably in the available capacity. Which starting design best meets the requirement without causing unnecessary queries against the source?
- Use DirectQuery for every visual because it is always faster than Import.
- Use Import storage and configure an appropriate scheduled semantic-model refresh.
- Export a separate Power BI report for each trading day and combine them manually.
- Keep the report disconnected from the source and ask users to type daily totals.
Correct answer: B. Import is a sensible default when the dataset is manageable and a daily refresh meets the freshness requirement. Vertipaq can serve interactive queries from the imported model, while an appropriately scheduled refresh updates it from Azure SQL. DirectQuery is useful in some low-latency or data-volume scenarios, but it adds dependency on source response times and can change modeling or performance characteristics; it is not an automatic upgrade. A current requirement should drive the storage decision rather than a slogan about ‘live’ data.
Before deciding, confirm the source connector, capacity, expected concurrent usage, and permitted refresh frequency. If requirements later change to near-real-time visibility, reconsider DirectQuery or another suitable architecture after measuring query performance.
Skill check: Create a small Import model, refresh it after adding one source row, and verify when the new transaction becomes visible.
Question 2: Combining monthly extracts without losing records
An analyst receives January, February, and March CSV files containing the same sales columns and compatible data types. Management wants a single table with rows from all three months. Which Power Query operation addresses this requirement most directly?
- Merge the files by matching customer IDs, which joins columns horizontally.
- Create an inactive relationship between all three files and leave them as separate fact tables.
- Append the queries after aligning column names and data types.
- Replace the January file with March so that the model remains small.
Correct answer: C. Append stacks records from tables with comparable schemas; Merge joins columns from different sources on matching keys. The distinction matters because joining three monthly transaction exports by customer would produce a different shape and could duplicate rows. Inspect column names and data types before appending, add a source-month column when provenance matters, and verify record counts after combination. These are practical Power Query transformations, not simply two interchangeable toolbar commands.
A reusable transformation that ingests files from a controlled folder may be preferable when this process repeats. Check column drift and malformed dates before treating a successful append as evidence of correct data.
Skill check: Append two sample exports, reconcile their combined row count, and deliberately add a mismatched column to see how Power Query handles it.
Question 3: Recognizing query-folding opportunities
A Power Query pipeline retrieves millions of rows from a supported relational database. The report requires only a few columns and the previous twelve months of data. Which action is the most useful first optimization to investigate?
- Apply supported column-selection and filtering transformations, and verify whether they fold to the source.
- Add a nonfoldable custom transformation first, then assume all later filtering executes in SQL.
- Import every column and all history before discarding unnecessary rows in the final visual.
- Disable the source connector’s ability to translate transformations and rely only on local processing.
Correct answer: A. Query folding can push supported Power Query transformations to a source capable of executing them. Filtering rows and selecting required fields are strong candidates for reduction in data transfer, but folding is not guaranteed merely by their placement: connector capability and the complete query expression matter. Inspect the native-query or folding indicators where available and validate the generated workload. Large extracts should not be optimized by assuming an entire transformation chain always folds.
Power Query can reorder some steps, and a partial-folding outcome is possible. Compare the amount of source data transferred and the refresh behavior before and after a change, rather than claiming that every early filter is faster.
Skill check: Use a supported SQL source, keep only relevant columns and dates, and inspect which steps remain eligible for folding.
Question 4: Building a star-schema relationship
A Sales fact table contains millions of transaction lines and repeats ProductKey. A Products dimension contains one row for each ProductKey, with category and brand attributes. Analysts want category slicers to filter sales without ambiguous paths. Which relationship is the best starting point?
- Create a many-to-many relationship that filters both directions because the fact table has repeated keys.
- Put product names in every transaction and avoid a separate product dimension.
- Connect Products to Sales with an inactive relationship and use text matching in every measure.
- Use an active one-to-many relationship from unique Products to repeated Sales, normally with single-direction filtering.
Correct answer: D. A conventional star schema uses a unique dimension key on the one side and corresponding foreign keys in the fact table on the many side. Filters flow from descriptive dimensions to measurements, making behavior easier to reason about and generally reducing ambiguity. The recommended starting relationship is one-to-many with single-direction filtering from Products to Sales. For a fuller treatment of data modeling in Power BI, the important issue is how keys and filter paths represent the business entities, not whether a relationship looks convenient in the diagram.
Confirm uniqueness and referential integrity before creating the relationship. Bidirectional or many-to-many designs have legitimate advanced uses, but should not be chosen casually to fix a model with poorly defined grain.
Skill check: Build the two tables, add a category slicer, and explain why an unmatched product key can produce unexpected blank categories.
Question 5: Writing a total that responds to slicers
A report has an active relationship from a Date table to Sales, and users slice by year and product category. The measure should calculate the revenue for the visible subset of Sales rows. Which implementation is most appropriate?
- Create a measure using Total Revenue = SUM(Sales[Revenue]).
- Create a calculated column in Sales containing the sum of the entire table for every transaction.
- Precompute one all-time revenue value in Power Query and repeat it for every year.
- Wrap every revenue expression in ALL(Sales), removing the filters that users expect to apply.
Correct answer: A. A measure is evaluated at query time in the filter context established by the visual, slicers, and active model relationships. A straightforward SUM over the revenue column can therefore return a different result for each period or product category. A calculated column is stored at refresh time and is not an equivalent response to interactive filter context. In practical DAX measures and calculations, the correctness of the relationship graph matters just as much as the expression itself.
If the report includes tax, refunds, or multiple currencies, define the business measure explicitly instead of assuming a raw sum always means net revenue. Here, the question deliberately specifies a simple revenue field and valid relationships.
Skill check: Create the measure, move a product-category slicer, and compare the filtered result with the underlying fact rows.
Question 6: Changing filter context with CALCULATE
The model has a valid one-to-many relationship from Geography to Sales, and [Total Revenue] is already defined. A report needs a measure that always calculates revenue for the West region when no other regional logic must be preserved. Which DAX pattern directly expresses that requirement?
- Use RELATED(Geography[Region]) alone as a measure; it automatically aggregates revenue.
- Use SUMX without specifying a table or expression because it implicitly filters the West region.
- Use CALCULATE([Total Revenue], Geography[Region] = “West”).
- Use IF(Geography[Region] = “West”, [Total Revenue]) without establishing a single row context.
Correct answer: C. CALCULATE evaluates an expression under a modified filter context. With an active relationship from Geography to Sales, the specified region filter influences which sales contribute to [Total Revenue]. The result still respects other applicable filters such as date unless the expression changes them. The formula is intentionally simple: it assumes Geography[Region] is a valid filter column and the model’s relationships are correct.
A filter argument on Region generally replaces an existing filter on the same column; KEEPFILTERS can change that behavior when intersection is required. Explaining this nuance shows an understanding of DAX context rather than memorized function names.
Skill check: Test the result against West and East slicer selections, then compare it with a KEEPFILTERS version.
Question 7: Presenting a two-year trend accessibly
A finance manager asks for monthly operating costs over twenty-four months, with clear trends and accessible labels. The audience includes people who use screen readers and people who cannot distinguish colors reliably. Which design is the strongest starting choice?
- A pie chart with twenty-four slices and a color-only legend.
- A line chart with a readable date axis, explanatory title, accessible text, and non-color cues where needed.
- A decorative 3D chart with no axis labels because its visual impact is higher.
- A large data table with every transaction but no month-level summary.
Correct answer: B. A line chart communicates changes over an ordered time axis more clearly than a twenty-four-slice pie. Meaningful axis labels, a descriptive title, accessible text, and adequate contrast help audiences interpret the report. When multiple series are present, use labels or patterns instead of relying solely on color. Good Power BI data visualization is not merely choosing an attractive chart; it connects the measure, its aggregation level, and the reader’s task.
A detailed table might still serve as a drill-through destination for auditors, but it does not replace the requested high-level trend. Ensure the months are sorted chronologically rather than alphabetically and check behavior with keyboard navigation.
Skill check: Rebuild the trend with monthly aggregation and explain one accessibility improvement beyond changing the palette.
Question 8: Enforcing regional access with RLS
A company publishes one sales semantic model to regional managers. Each manager must see only the regions they are authorized to review; the security mapping may change over time. Managers need to consume the report, not edit the model. What combination best satisfies these requirements?
- Give managers the workspace Admin role and rely on a report-page filter.
- Hide unauthorized pages from navigation without configuring model security.
- Give every manager Contributor access and assume RLS applies to all workspace roles.
- Use a security mapping table and a role filter based on the signed-in identity; assign appropriate RLS membership and distribute content with Viewer/app-consumer permissions.
Correct answer: D. Dynamic row-level security can use a mapping of user identities to permitted regions and a role expression involving USERPRINCIPALNAME(), subject to correct relationships and security role assignments. RLS must be tested under an appropriate user identity. In a Power BI workspace, Admin, Member and Contributor permissions can bypass RLS because they grant editing rights to the semantic model; RLS restricts Viewers and appropriate app consumers. Workspace convenience should never be substituted for data-access control.
Security tables must be maintained carefully, and changes in identity format or relationship direction can cause leaks or unexpectedly empty reports. Test both a permitted manager and one who must not access the same region.
Skill check: Use Test as role to compare two test identities, then confirm that the managers do not have edit roles that defeat the intended restriction.
Question 9: Refreshing a private SQL source
A published Import semantic model reads from SQL Server on a company network that Power BI’s cloud service cannot reach directly. The organization wants unattended scheduled refresh for multiple team-owned reports. Which architecture is the most appropriate?
- Deploy and configure an on-premises data gateway in standard mode, associate the supported source connection and credentials, then schedule refresh.
- Refresh the file once in Power BI Desktop and assume the service will automatically repeat the process.
- Configure a refresh schedule without any gateway or network path to the SQL Server.
- Give everyone workspace Admin rights so the security boundary no longer blocks database connectivity.
Correct answer: A. A standard on-premises data gateway provides a centrally managed connection between supported private sources and the Power BI service. Once the source connection and credentials are set up and the gateway is online, the Import semantic model can refresh according to a schedule within the applicable service limits. This is preferable to depending on one analyst’s desktop session for a team-owned reporting workload. Proper gateway administration also separates database permissions from general report viewing rights.
A personal-mode gateway can serve certain individual Import refresh scenarios but does not provide the same centrally managed sharing capabilities. Before enabling refresh, confirm source permissions, network access, time zones and failure alerts.
Skill check: Sketch the data flow from SQL Server through a gateway to the semantic model; identify which administrator controls each credential.
Question 10: Diagnosing the slowest report visual
Users complain that a Power BI report pauses for several seconds after they select a product slicer. The page contains several visuals, and nobody knows whether the bottleneck is a DAX query, rendering, or data retrieval. What should the analyst do first?
- Purchase a larger capacity immediately without identifying which operation is slow.
- Remove all slicers so the report no longer supports the intended analysis.
- Record the interaction with Performance Analyzer, examine visual timings and relevant queries, then optimize the identified bottleneck.
- Replace the entire star schema with unrelated flat tables because relational models are always slower.
Correct answer: C. Performance Analyzer shows the load durations for individual visuals and helps separate query time from display or other processing. Recording the troublesome slicer interaction identifies which visuals are actually affected. Where appropriate, inspect a copied DAX query, review high-cardinality columns, check model relationships, and verify that transformations are not producing needless data volume. Optimizing the measured bottleneck is a sound first step; buying capacity or deleting functionality before measurement is not.
If multiple queries are slow because of the upstream source, examine source latency and folding as well. Test after each adjustment and preserve the original business question the report was meant to answer.
Skill check: Record two interactions, rank visuals by duration and state one hypothesis you can verify before changing the model.
Treat the answer key as a diagnostic rather than a score guarantee. Mark every question you missed, identify which assumption or product behavior you misunderstood, and repeat the associated skill check with an unfamiliar dataset. For example, someone who chooses a many-to-many relationship automatically should rebuild the star schema, whereas a candidate who misses the security item should test how workspace roles and model filters interact.
Your next review session should concentrate on what you cannot yet explain from first principles: how Power Query changes rows before loading, why an active relationship affects DAX filter context, how a visual encodes a business measure, and what security boundary protects a published semantic model. These are portable analytical skills, regardless of whether your eventual job title is data analyst, business intelligence developer, or reporting specialist.