Describe the business value of Microsoft Power Platform →mediumMultiple Choice

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
The Employee role grants Read at Organization scope, which lets the user view every asset record regardless of ownership. Changing that privilege to User scope restricts visibility to records they own or are shared, matching the requirement to see only assigned assets.
✗
The Asset table does not have a relationship to the User table
Why it's wrong here
Without a relationship linking Asset to User, Dataverse cannot filter rows by the signed-in user, so every record is returned. Relationships are the correct mechanism when building model-driven filtering that scopes records to their owning user.
✗
The employee is not the owner of the asset records
Why it's wrong here
Ownership governs record-level access only when the security role grants User-level read on the table. If the role grants Organisation-level read, every record is visible regardless of owner, so ownership is irrelevant here. Ownership matters when configuring row-level sharing or reassigning records.
✗
The app is not configured to filter records based on the current user
Why it's wrong here
Dataverse enforces row-level security through security roles, not app-level filtering. A Power Apps gallery filter changes only what is displayed, not what the connector can retrieve, so users could still access all records. App filtering suits cosmetic views, not access control.

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