Describe the business value of Microsoft Power Platform →mediumMultiple ChoiceObjective-mapped

PL-900 Practice Question: Describe the business value of Microsoft Power Platform

Exhibit

{
  "app": {
    "name": "Asset Management",
    "dataSource": "Microsoft Dataverse",
    "tables": [
      {
        "name": "Asset",
        "columns": [
          {"name": "Name", "type": "Text"},
          {"name": "SerialNumber", "type": "Text"},
          {"name": "AssignedTo", "type": "Lookup", "targetTable": "User"},
          {"name": "Status", "type": "Choice", "options": ["Active", "Inactive", "Disposed"]}
        ]
      }
    ],
    "roles": [
      {
        "name": "Asset Manager",
        "permissions": "Create, Read, Write"
      },
      {
        "name": "Employee",
        "permissions": "Read"
      }
    ]
  }
}

Refer to the exhibit. A Power Apps app uses Dataverse with the defined table and roles. An employee reports that they can see all assets in the app, but they should only see assets assigned to them. What is the most likely reason?

⚠ Common exam trap

Candidates often assume the app must explicitly filter records (Option D) or that a table relationship is needed (Option B), when in fact Dataverse's built-in security role scopes handle record-level visibility automatically without custom app logic.

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 Employee security role has 'Read' permission set to 'Organization' scope instead of 'User'

The Employee security role's 'Read' permission is set to 'Organization' scope, which allows the employee to see all asset records in the Dataverse table. To restrict visibility to only assets assigned to the employee, the 'Read' permission should be set to 'User' scope, which limits record access to those the user owns or is assigned to. This is a common misconfiguration in Dataverse role-based security that directly causes the reported issue.

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 Employee security role has 'Read' permission set to 'Organization' scope instead of 'User'
Why this is correct
With 'Organization' scope, users see all records; with 'User' scope, they see only records they own or are assigned to.
✗
The Asset table does not have a relationship to the User table
Why it's wrong here
The table has an AssignedTo lookup to User, so relationship exists.
✗
The employee is not the owner of the asset records
Why it's wrong here
Ownership is not required; the AssignedTo field could be used with 'User' scope if scoped to that field.
✗
The app is not configured to filter records based on the current user
Why it's wrong here
Even if the app does not filter, security roles would limit at the data layer if set correctly.

Go deeper

PL-900 Practice Question: Describe the business value of Microsoft Power Platform

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question