Question 335 of 966
Manage and secure Power BIhardMultiple ChoiceObjective-mapped

PL-300 Row-Level Security (RLS) Practice Question

This PL-300 practice question tests your understanding of manage and secure power bi. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: row-Level Security (RLS). Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Your organization uses Power BI Premium and wants to enforce that users can only see data relevant to their department (Sales, Marketing, Finance) using row-level security (RLS). The dataset contains a 'Department' column. You have created three RLS roles, each with a filter like [Department] = "Sales". You publish the dataset and add users to the roles. However, users in the Sales role can see all data. What is the most likely cause?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The users are also assigned to workspace roles (e.g., Member) that grant them access to the dataset without RLS restrictions.

The correct answer is D. In Power BI, users assigned to workspace roles (Admin, Member, Contributor) have dataset-level permissions that bypass Row-Level Security (RLS). Since these users can access the dataset directly, RLS filters are not applied. Option A is incorrect because RLS roles are typically created in Power BI Desktop before publishing. Option B is incorrect; multiple roles combine filters using OR logic, so users in multiple roles see union of all allowed data, not all data. Option C is incorrect because RLS filters are case-insensitive by default. Option D correctly identifies that workspace roles override RLS.

Key principle: Row-Level Security (RLS)

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The RLS roles were created in the Power BI service, not in Power BI Desktop.

    Why it's wrong here

    RLS roles can be created in Desktop and then applied in the service.

  • The users are members of multiple RLS roles, so they see all data.

    Why it's wrong here

    Multiple roles combine, but if one role restricts to Sales, they should only see Sales data from that role.

  • The RLS filter uses a string comparison that is case-sensitive and the data contains mixed case.

    Why it's wrong here

    DAX string comparisons are case-insensitive by default.

  • The users are also assigned to workspace roles (e.g., Member) that grant them access to the dataset without RLS restrictions.

    Why this is correct

    Users with edit permissions on the dataset bypass RLS.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Row-Level Security (RLS)

Common exam traps

Common exam trap: answer the scenario, not the keyword

A common trap is assuming that RLS always applies to all users, but workspace-level permissions (Admin, Member, Contributor) supersede RLS. Only users with no workspace role or the 'Viewer' role are subject to RLS.

Detailed technical explanation

How to think about this question

Treat this as a scenario question. Identify the problem, the constraint, and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Row-Level Security (RLS)
  • Workspace Roles
  • RLS Bypass
  • RLS Role Membership

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Row-Level Security (RLS)

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Review row-Level Security (RLS), then practise related PL-300 questions on the same topic to reinforce the concept.

Related practice questions

Related PL-300 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PL-300 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PL-300 question test?

Manage and secure Power BI — This question tests Manage and secure Power BI — Row-Level Security (RLS).

What is the correct answer to this question?

The correct answer is: The users are also assigned to workspace roles (e.g., Member) that grant them access to the dataset without RLS restrictions. — The correct answer is D. In Power BI, users assigned to workspace roles (Admin, Member, Contributor) have dataset-level permissions that bypass Row-Level Security (RLS). Since these users can access the dataset directly, RLS filters are not applied. Option A is incorrect because RLS roles are typically created in Power BI Desktop before publishing. Option B is incorrect; multiple roles combine filters using OR logic, so users in multiple roles see union of all allowed data, not all data. Option C is incorrect because RLS filters are case-insensitive by default. Option D correctly identifies that workspace roles override RLS.

What should I do if I get this PL-300 question wrong?

Review row-Level Security (RLS), then practise related PL-300 questions on the same topic to reinforce the concept.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

What is the key concept behind this question?

Row-Level Security (RLS)

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More PL-300 practice questions

Last reviewed: Jun 21, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This PL-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-300 exam.