nerdexam
Microsoft

DP-500 · Question #136

You have a Power BI dataset that has only the necessary fields visible for report development. You need to ensure that only 25 fields are available when end users personalize visuals. What should…

The correct answer is A. From Tabular Editor, create a new perspective. To limit the fields available for end users when personalizing visuals in Power BI, while keeping all fields visible for report development, you should create a new perspective in Tabular Editor that includes only the desired 25 fields.

Implement and manage data models

Question

You have a Power BI dataset that has only the necessary fields visible for report development. You need to ensure that only 25 fields are available when end users personalize visuals. What should you do?

Exhibit

DP-500 question #136 exhibit

Options

  • AFrom Tabular Editor, create a new perspective.
  • BFrom Tabular Editor, create a new role.
  • CHide all the fields in the dataset.
  • DConfigure object-level security (OLS).

How the community answered

(38 responses)
  • A
    76% (29)
  • B
    3% (1)
  • C
    13% (5)
  • D
    8% (3)

Why each option

To limit the fields available for end users when personalizing visuals in Power BI, while keeping all fields visible for report development, you should create a new perspective in Tabular Editor that includes only the desired 25 fields.

AFrom Tabular Editor, create a new perspective.Correct

Creating a new perspective in Tabular Editor is the correct approach. A perspective defines a subset of a model that can be presented to users, allowing you to show only the necessary 25 fields for end-user personalization without affecting the full set of fields visible for report development or other consumers.

BFrom Tabular Editor, create a new role.

Creating a new role in Tabular Editor is for implementing Row-Level Security (RLS) or Object-Level Security (OLS), which restricts data access or object visibility based on user roles, not for limiting the fields shown for visual personalization.

CHide all the fields in the dataset.

Hiding all but 25 fields in the dataset directly would restrict report developers as well, which contradicts the requirement that necessary fields are visible for report development (implying more than 25 are needed).

DConfigure object-level security (OLS).

Configuring object-level security (OLS) restricts users from seeing or accessing certain tables or columns, which is a stronger restriction than merely limiting what's available for visual personalization.

Concept tested: Power BI data model perspectives for personalization

Source: https://learn.microsoft.com/en-us/power-bi/consumer/end-user-personalize-visuals#limit-personalization-options-for-a-report

Topics

#Data Modeling#Perspectives#Tabular Editor#Report Personalization

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DP-500 Practice