The answer is that the 'score' value is passed as a string instead of a number. This is the most likely cause because the Power Automate condition expression uses the 'greater' function to compare the trigger body's 'score' property against the numeric value 0.8, but when the HTTP request sends the score as a string like '0.9', the comparison fails due to a data type mismatch—string comparison evaluates character by character rather than numerically. On the Microsoft Power Platform Fundamentals PL-900 exam, this scenario tests your understanding of how Power Automate handles data types in condition expressions, a common trap where JSON payloads from HTTP requests often default to strings. To avoid this, remember that functions like 'greater', 'less', and 'equals' require matching data types; a string '0.9' is not greater than 0.8 because '0' is compared to '0', then '.' to '.', and finally '9' to '8', which actually passes alphabetically, but the logic breaks in other cases. Memory tip: "Strings stick together, numbers compare—always check your trigger's data type before the condition."
PL-900 Practice Question: Demonstrate the capabilities of Power Automate
This PL-900 practice question tests your understanding of demonstrate the capabilities of power automate. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
Refer to the exhibit. A Power Automate flow definition is shown. The flow is triggered by an HTTP request with a 'score' property. When the score is greater than 0.8, it sends an approval email to the manager. Otherwise, it logs the score to a SharePoint list. The flow runs but when a score of 0.9 is submitted, no email is sent and the SharePoint log is created. 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 'score' value is passed as a string instead of a number.
Option B is correct because the condition expression uses 'greater(triggerBody()?['score'], 0.8)' but if the 'score' property is a string (e.g., '0.9'), the comparison will fail because string comparison is different from numeric. The expression expects a number. Option A is wrong because the trigger is manual, not SharePoint. Option C is wrong because the condition is correct syntactically. Option D is wrong because the condition uses 'greater' which is 'greater than'.
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 condition uses 'greater' but should use 'greaterThan'.
Why it's wrong here
Both are valid.
✓
The 'score' value is passed as a string instead of a number.
Why this is correct
String vs number comparison causes condition to evaluate to false.
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.
✗
The condition expression is misspelled as 'greater' instead of 'greaterThan'.
Why it's wrong here
'greater' is correct in expressions.
✗
The trigger is set to 'When a file is created' but the request is HTTP.
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which PL-900 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Demonstrate the capabilities of Power Automate — This question tests Demonstrate the capabilities of Power Automate — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The 'score' value is passed as a string instead of a number. — Option B is correct because the condition expression uses 'greater(triggerBody()?['score'], 0.8)' but if the 'score' property is a string (e.g., '0.9'), the comparison will fail because string comparison is different from numeric. The expression expects a number. Option A is wrong because the trigger is manual, not SharePoint. Option C is wrong because the condition is correct syntactically. Option D is wrong because the condition uses 'greater' which is 'greater than'.
What should I do if I get this PL-900 question wrong?
Identify which PL-900 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Refer to the exhibit. The Power Automate flow definition includes a manual trigger expecting employeeId and amount. If an expense amount is $6,000, what will happen?
hard
A.The flow will send an approval email to the employee.
✓ B.The flow will start an approval assigned to manager@contoso.com.
C.The flow will fail because employeeId is missing.
D.The flow will send an email to manager@contoso.com.
Why B: Option C is correct because the condition checks if amount > 5000; 6000 is greater, so the 'Send_approval' action runs. Option A is wrong because the flow does not check employeeId. Option B is wrong because the else branch won't run. Option D is wrong because the trigger schema does not define managerEmail.
Last reviewed: Jun 21, 2026
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.
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.