The answer is a column name mismatch in the LookUp function. The most likely cause is that the Roles data source uses a column name different from 'UserEmail', such as 'Email' or 'UserID', so the function cannot find a match and returns blank even for existing users. This happens because Power Apps LookUp requires exact column name matching to filter records; any discrepancy in the schema causes the function to evaluate as false and return blank. On the PL-900 exam, this tests your understanding of data source integration and common schema mismatch issues in canvas apps, often appearing as a trap where testers assume the user’s existence guarantees a result. A reliable memory tip is “Check the column, not the value”—always verify that the column name in your formula matches the data source’s schema exactly, as Power Apps does not auto-map or alias field names.
PL-900 Practice Question: Describe the business value of Microsoft Power Platform
This PL-900 practice question tests your understanding of describe the business value of microsoft power platform. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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'.
Option D is correct because 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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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
Data source is typically loaded automatically, but refresh may help, but not the most likely cause.
✗
The Set function cannot store records.
Why it's wrong here
Set can store any value, including text from LookUp.
✗
The User() function is not available in Power Apps.
Why it's wrong here
User() is a valid function that returns current user info.
✓
The Roles data source column name does not match 'UserEmail'.
Why this is correct
Column name mismatch causes LookUp to return blank.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that 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.
Detailed technical explanation
How to think about this question
Under the hood, the LookUp function performs a server-side query against the data source using the specified filter condition. If the column name in the filter does not match the actual schema (e.g., 'UserEmail' vs. 'Email'), the query returns no rows, resulting in a blank. In real-world scenarios, this often occurs when data sources like SharePoint lists or Dataverse tables have different column display names versus logical names, or when the app references a column that was renamed after the app was built.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Describe the business value of Microsoft Power Platform — This question tests Describe the business value of Microsoft Power Platform — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The Roles data source column name does not match 'UserEmail'. — Option D is correct because 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.
What should I do if I get this PL-900 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.