DEV Community

Skillmarked
Skillmarked

Posted on AI-assisted

PL-300: 7 Power BI answers that look right and cost you points

You can build Power BI reports every day and still lose points on PL-300 (Microsoft Power BI Data Analyst). The exam likes questions where the answer you'd reach for at work is almost right.

Here are seven of those, across all four domains.

1. Sorting month names by the Date column

Your months come out as April, August, December… The fix is Sort by column, but the column you sort by matters.

The rule: the sort column must have exactly one value for each value of the column you're sorting. Sorting Month Name by Month Number works. Sorting Month Name by Date fails, because every month name has many dates.

If an answer option sorts by the date column "because it's already in order", it's the trap.

2. Reporting by ship date when the relationship uses order date

Sales has OrderDate and ShipDate, and both relate to one Date table. Only one relationship between two tables can be active, so the ship-date one is inactive (the dashed line).

For a handful of measures, keep it inactive and switch it on inside the measure:

Sales by Ship Date =
CALCULATE ( [Total Sales], USERELATIONSHIP ( Sales[ShipDate], 'Date'[Date] ) )
Enter fullscreen mode Exit fullscreen mode

Two details the exam checks: USERELATIONSHIP only works inside CALCULATE (or CALCULATETABLE), and only for a relationship that already exists in the model.

The other valid answer is a copy of the date table per role (a Ship Date table with its own active relationship). That's the right choice when users need to slice by order date and ship date independently, or see both in the same visual. Read the scenario for that requirement before choosing.

3. Time intelligence that "should" work but doesn't

TOTALYTD and SAMEPERIODLASTYEAR expect a proper date table:

  • one row per day, no gaps, no duplicates
  • a Date-typed column with no blanks
  • complete years covering every date in your facts

Then mark it as a date table. Marking also lets time intelligence work when the relationship uses an integer key like 20260131 instead of a date.

And once you have your own date table, turn off Auto date/time. It creates a hidden date table for every date column, which bloats the model and doesn't share dates across fact tables.

4. Expecting CALCULATE to respect the slicer

Red Sales = CALCULATE ( [Total Sales], Product[Color] = "Red" )
Enter fullscreen mode Exit fullscreen mode

Put a slicer on Color, pick Blue, and this still shows red sales. A simple filter argument replaces any existing filter on that column.

If you want it to intersect with the slicer instead (blank for Blue), wrap it: KEEPFILTERS ( Product[Color] = "Red" ). Questions about "why does this measure ignore the slicer" are usually this.

5. Testing RLS with your own account

You set up row-level security, publish, open the report and see everything. Is RLS broken?

Probably not. RLS applies to Viewers, and to people who get access through an app or sharing. Admins, Members and Contributors of the workspace are not filtered. If you're a Member, you'll see all rows.

Two more details that turn up in questions:

  • Roles you define in Desktop only take effect once you assign members in the service (semantic model > Security). Security groups are the tidy way to do that.
  • Once RLS exists, someone with access to the report but no role sees no data.

6. Dynamic RLS with USERNAME()

For "each salesperson sees only their own rows", you want one role with a filter like:

[Email] = USERPRINCIPALNAME ()
Enter fullscreen mode Exit fullscreen mode

usually on a user mapping table, with the filter flowing to the facts through relationships.

Why not USERNAME()? In Desktop it returns DOMAIN\user, while USERPRINCIPALNAME() returns the sign-in name in both Desktop and the service. If one option uses each, pick the UPN.

7. The wrong gateway (or a gateway you don't need)

Scheduled refresh from an on-premises SQL Server needs an on-premises data gateway. Two traps around it:

  • Personal mode serves one user and supports Import refresh only. If the scenario mentions DirectQuery, several users or a team, it's standard mode.
  • Cloud sources such as Azure SQL Database, SharePoint Online or Dataverse don't need a gateway at all. "Install a gateway" is a distractor there.

How to study for this

Most of these only stick once you've hit them yourself. Build one small model end to end:

  1. Make a proper date table and sort month names correctly.
  2. Add a ship-date measure with USERELATIONSHIP.
  3. Publish it, add a colleague as a Viewer, and test dynamic RLS.

We run Skillmarked, an independent exam-prep site (not affiliated with Microsoft). The full PL-300 study guide is free: 30 lessons across all four domains, with a practice scenario after every lesson.

Top comments (0)