Question 18 of 966
Manage and secure Power BImediumMultiple ChoiceObjective-mapped

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

This PL-300 practice question tests your understanding of manage and secure power bi. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.

Exhibit

{
  "policies": [
    {
      "name": "SalesRLS",
      "roles": [
        {
          "name": "SalesManager",
          "filterExpression": "[SalesAmount] > 10000"
        },
        {
          "name": "SalesRep",
          "filterExpression": "[SalesAmount] > 0"
        }
      ]
    }
  ]
}

Refer to the exhibit. A Power BI administrator reviews a row-level security (RLS) policy for the Sales dataset. The SalesManager role should see all sales above $10,000, and the SalesRep role should see all sales above $0. However, users in the SalesRep role report that they cannot see any data when they open the report. What is the most likely issue?

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.

Exhibit

{
  "policies": [
    {
      "name": "SalesRLS",
      "roles": [
        {
          "name": "SalesManager",
          "filterExpression": "[SalesAmount] > 10000"
        },
        {
          "name": "SalesRep",
          "filterExpression": "[SalesAmount] > 0"
        }
      ]
    }
  ]
}

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 column name in the filter expression does not match the actual column name in the dataset

The correct answer is B because if the column name in the RLS filter expression does not match the actual column name in the dataset (e.g., using 'SalesAmount' when the column is 'Amount'), the filter will fail silently, causing users to see no data. RLS filters are evaluated at query time and must reference valid column names. Option A is wrong because the SalesRep role is assigned to users, so that is not the issue. Option C is wrong because the 'greater than' operator is supported in RLS. Option D is wrong because RLS filters must be applied on columns, not measures, but the issue here is mismatched column names.

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 SalesRep role is not assigned to any users

    Why it's wrong here

    If assigned, users would see data; the issue is no data.

  • The column name in the filter expression does not match the actual column name in the dataset

    Why this is correct

    Mismatched column names cause RLS to not apply, resulting in no data.

    Clue confirmation

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

    Related concept

    Row-Level Security (RLS)

  • The filter expression uses a comparison operator that is not supported in RLS

    Why it's wrong here

    '>' is supported.

  • The RLS role uses a filter on a measure, not a column

    Why it's wrong here

    RLS can filter on columns; the filter uses a column name, not a measure.

Common exam traps

Common exam trap: answer the scenario, not the keyword

A common trap is assuming that an RLS role assignment is incomplete when users see no data, but the actual problem is often a mismatch between the column name in the filter expression and the actual column in the dataset.

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)
  • RLS filter expressions
  • Column name mismatch

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 column name in the filter expression does not match the actual column name in the dataset — The correct answer is B because if the column name in the RLS filter expression does not match the actual column name in the dataset (e.g., using 'SalesAmount' when the column is 'Amount'), the filter will fail silently, causing users to see no data. RLS filters are evaluated at query time and must reference valid column names. Option A is wrong because the SalesRep role is assigned to users, so that is not the issue. Option C is wrong because the 'greater than' operator is supported in RLS. Option D is wrong because RLS filters must be applied on columns, not measures, but the issue here is mismatched column names.

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.