mediumMultiple ChoiceObjective-mapped

PL-900 Practice Question: Refer to the exhibit

Exhibit

{
  "table": "Contact",
  "permissions": [
    {"scope": "Global", "read": true, "write": false, "create": false, "delete": false},
    {"scope": "Contact", "read": true, "write": true, "create": true, "delete": true}
  ]
}

Refer to the exhibit. A Power Pages site has Dataverse table permissions configured for the Contact table as shown. What can an authenticated user do?

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

✓

Read, create, update, and delete their own contact record

The Contact table permissions with scope 'Contact' and all privileges (Read, Create, Write, Delete) grant authenticated users full CRUD access to their own contact record. Option A is incorrect because the exhibit shows Contact scope, not Global scope, so users cannot read/update all contacts. Option B is incorrect because Contact scope grants full CRUD, not just read and update. Option C is incorrect because Contact scope includes create, update, and delete privileges beyond just read.

Answer analysis

Option-by-option breakdown

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

✗
Read and update any contact record
Why it's wrong here
Global scope does not allow write.
✗
Only read and update their own contact record
Why it's wrong here
Contact scope allows create and delete too.
✗
Only read their own contact record
Why it's wrong here
Global scope allows read on all contacts, but not write.
✓
Read, create, update, and delete their own contact record
Why this is correct
Contact scope on self allows full CRUD.

Go deeper

PL-900 Practice Question: Refer to the exhibit

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question