easyMultiple Choice
PL-900 Practice Question: Allow customers to view their order history on a…
A company wants to allow customers to view their order history on a Power Pages site. Customers must log in to see their own orders only. Which feature should be used to enforce data security?
⚠ Common exam trap
It's easy for candidates to confuse authentication (logging in) with authorization (data filtering), assuming that requiring a login (Option D) is sufficient to secure data, when in fact row-level security requires explicit entity permissions.
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
✓
Configure entity permissions for the Orders table and assign to a web role.
Entity permissions in Power Pages allow you to define granular access rights (Create, Read, Update, Delete) for specific Dataverse tables. By configuring entity permissions for the Orders table and assigning them to a web role that is associated with the authenticated user, you ensure that customers can only see their own orders based on the relationship between the Contact record and the Orders table. This is the correct approach because it enforces row-level security tied to the authenticated user's identity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure entity permissions for the Orders table and assign to a web role.
Why this is correct
Entity permissions in Power Pages define table-level access for each web role, so assigning the Orders table permission to the authenticated customer role restricts records to the signed-in contact. This satisfies the stem's requirement that customers view only their own orders, since permissions scope access by the contact relationship rather than granting blanket table read.
- ✗
Enable column-level security on the Orders table.
Why it's wrong here
Column-level security restricts which fields a user can read or write, not which rows belong to them, so customers could still see other customers' orders. It tempts because it does secure data, but row-level filtering by contact is what isolates each customer's records.
- ✗
Use a custom authentication provider to filter data.
Why it's wrong here
A custom authentication provider only verifies identity; it does not filter Dataverse rows, so authenticated customers could still query others' orders. It tempts because authentication feels like the security boundary, but table permissions scoped to the contact are what restrict each customer to their own records.
- ✗
Set page permissions to require authentication.
Why it's wrong here
Requiring authentication on a page only gates anonymous visitors; every signed-in customer still sees all orders unless table permissions filter rows by contact. It tempts because login feels like data isolation, but page permissions control access to the page, not which records within it are returned.
Go deeper
Related to this question
About these practice questions
This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-900 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-900 exam.