Giving workspace roles powers they do not hold
The wrong answers hand app publishing and user management to the wrong role: a Contributor publishing a first app, or a Member changing another user's existing role. Publishing, unpublishing and changing app permissions belong to Admin and Member only. A Member can add users with lower permissions but cannot remove users or change an existing role. A Contributor can update an existing app only when an Admin enables Allow contributors to update the app for this workspace.
See it in a sample questionAssuming row-level security reaches further than it does
The wrong answers stretch RLS beyond its scope: hiding individual columns, filtering users who can edit content, or accepting service principals and Microsoft 365 groups as role members. RLS secures rows only, and it restricts data access only for users with Viewer permissions on the workspace. Service principals cannot be added to an RLS role. Microsoft 365 groups cannot either, while Entra security groups, distribution groups and mail-enabled groups can.
See it in a sample questionConfusing the identity formats RLS filters receive
The wrong answers swap or alter what the identity functions return. In Power BI Desktop, USERNAME() returns DOMAIN\username, while in the Power BI service it returns the UPN, which looks like an email address, so a role tested locally can filter differently once published. For B2B guests, USERPRINCIPALNAME() may return the external email or a guest UPN in #EXT# form, so the returned value has to be verified rather than stripped or assumed.
See it in a sample questionTreating sensitivity labels as access control
The wrong answers give a label power over who can open content, or assume it follows data down every route. In the Power BI service a label does not affect access; Power BI permissions still govern it. The label applies its protection on supported exports such as Excel, Analyze in Excel, a PivotTable with a live connection and .pbix download. It does not reach .csv exports or subscription email text and preview images, and PowerPoint carries it only with Export as image.
See it in a sample questionReading personal mode as a full gateway
The wrong answers treat the personal mode gateway as broader than it is: writing rows back for Power Automate, or serving a whole team. Personal mode is narrowed to Power BI scheduled refresh and DirectQuery, serves one user and cannot be shared. The standard on-premises data gateway lets multiple users reach multiple on-premises sources, and it works with Power BI, Azure Data Factory, Power Automate and other services.
See it in a sample question