PL-900 Practice Question: Describe the business value of Microsoft Power Platform
Exhibit
Refer to the exhibit.
```yaml
# Example: Power Apps component library reference
App.OnStart = Set(
varUserEmail,
User().Email
);
Set(varUserRole, LookUp(Roles, UserEmail = varUserEmail).Role)
```In a Power Apps canvas app, the App.OnStart property contains the code above. The LookUp function returns blank for a user who exists in the Roles data source. What is the most likely cause?
⚠ Common exam trap
A common mix-up: candidates assume the LookUp function will automatically match any column containing the user's email, ignoring the exact column name requirement, or they confuse this with a data refresh or function availability issue.
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 Roles data source column name does not match 'UserEmail'.
The LookUp function in Power Apps relies on exact column name matching. If the Roles data source has a column named 'Email' or 'UserID' instead of 'UserEmail', the function will not find a match and will return blank, even if the user exists. This is a common schema mismatch issue in canvas apps.
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 app needs to refresh the Roles data source first.
Why it's wrong here
LookUp queries the data source directly at runtime, so a stale cache is not the cause; blank results typically stem from a mismatched column or value type in the lookup condition. Refreshing is tempting because it fixes genuinely stale collections, and would be correct if the app read from a cached collection instead.
- ✗
The Set function cannot store records.
Why it's wrong here
Set stores any value, including records, so this is factually untrue and cannot explain the blank result. It is tempting because Set is often associated with scalars in simple apps, and would be correct only if the function genuinely rejected record types, which it does not.
- ✗
The User() function is not available in Power Apps.
Why it's wrong here
User() is a supported Power Apps function returning the signed-in user's record, so this claim is false and cannot cause the blank lookup. It is tempting because User() behaves differently across environments, and would be correct only if the function were unavailable in the app's context, which it is not.
- ✓
The Roles data source column name does not match 'UserEmail'.
Why this is correct
LookUp matches the formula's column argument against the actual column logical name in the Roles data source. If that column is named differently from 'UserEmail', the lookup finds no matching record and returns blank even though the user exists.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-900 question from scratch — 701 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.