The correct answer is to use a 'When an HTTP request is received' trigger and check for a unique identifier. This works because the unique identifier allows the flow to implement a deduplication pattern—often called a cooldown or debounce—by storing the identifier in a variable or data operation and ignoring subsequent requests with the same ID. On the Microsoft Power Platform Fundamentals PL-900 exam, this scenario tests your understanding of how triggers handle repeated events, especially when external systems like sensors may resend data. A common trap is assuming that simply adding a delay or using a different trigger type will stop duplicates, but those options either delay all alerts or fail to filter repeated HTTP calls. Remember the memory tip: "ID it to avoid the repeat"—if you can identify the unique event, you can block the duplicate.
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.
A manufacturing company uses Power Automate to monitor equipment sensors. When a temperature sensor exceeds a threshold, a flow sends an alert to the maintenance team. However, duplicate alerts are being sent for the same event. What should the flow developer implement to prevent duplicates?
Why wrong: 'Get changes' is used for SharePoint, not sensor data.
B
Use a 'When an HTTP request is received' trigger and check for a unique identifier.
By checking a unique identifier (like sensor ID + timestamp) in a SharePoint list or using a 'Condition' to see if the alert was already sent, duplicates can be avoided.
C
Increase the threshold value so alerts are less frequent.
Why wrong: This avoids the problem but does not prevent duplicates for the same event.
D
Add a 'Delay' action of 5 minutes before sending the alert.
Why wrong: A delay only postpones the alert; it does not prevent duplicates.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a 'When an HTTP request is received' trigger and check for a unique identifier.
Using a 'Cooldown' or 'Debounce' pattern with a variable or a data operation can prevent duplicate triggers. The trigger for HTTP request can receive the same event multiple times if the sensor resends. Option A would delay all alerts, not prevent duplicates. Option B would not prevent duplicates because the trigger fires for each HTTP request. Option D is not a built-in feature and would require custom logic.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use the 'Get changes' action for the sensor data.
Why it's wrong here
'Get changes' is used for SharePoint, not sensor data.
✓
Use a 'When an HTTP request is received' trigger and check for a unique identifier.
Why this is correct
By checking a unique identifier (like sensor ID + timestamp) in a SharePoint list or using a 'Condition' to see if the alert was already sent, duplicates can be avoided.
Related concept
Static NAT maps one inside address to one outside address.
✗
Increase the threshold value so alerts are less frequent.
Why it's wrong here
This avoids the problem but does not prevent duplicates for the same event.
✗
Add a 'Delay' action of 5 minutes before sending the alert.
Why it's wrong here
A delay only postpones the alert; it does not prevent duplicates.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. 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.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related PL-900 NAT questions on configuration and troubleshooting.
Demonstrate the capabilities of Power Automate — This question tests Demonstrate the capabilities of Power Automate — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use a 'When an HTTP request is received' trigger and check for a unique identifier. — Using a 'Cooldown' or 'Debounce' pattern with a variable or a data operation can prevent duplicate triggers. The trigger for HTTP request can receive the same event multiple times if the sensor resends. Option A would delay all alerts, not prevent duplicates. Option B would not prevent duplicates because the trigger fires for each HTTP request. Option D is not a built-in feature and would require custom logic.
What should I do if I get this PL-900 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related PL-900 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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.