PL-900 Practice Question: Describe the business value of Microsoft Power Platform
A company uses Power Automate to process purchase orders. After a recent update, the flow fails intermittently with a '429 Too Many Requests' error. What is the most likely cause?
⚠ Common exam trap
It's easy for candidates to confuse '429 Too Many Requests' with authentication or connectivity issues, but the exam specifically tests knowledge of Power Platform service protection limits as a distinct throttling mechanism.
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 flow is exceeding Power Platform service protection limits.
The '429 Too Many Requests' error is an HTTP status code indicating rate limiting. In Power Automate, this occurs when a flow exceeds the Power Platform service protection limits, which are designed to prevent resource overconsumption. These limits include API request caps (e.g., 30 requests per 60 seconds per connection) and daily invocation quotas (e.g., 5,000 requests per day for a per-user plan). The error is not related to authentication expiry, outdated flow versions, or data source availability.
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 flow uses an expired connector authentication.
Why it's wrong here
An expired connector authentication returns 401 Unauthorized, not 429, so it cannot explain the throttling error. It is tempting because broken credentials are a common cause of flow failures, and reconnecting the connector is the standard fix when Power Automate reports authentication problems rather than request-rate limits.
- ✗
The flow is running an outdated version.
Why it's wrong here
An outdated flow version does not produce HTTP 429 responses; the platform executes the saved definition regardless. Versioning matters when a flow references a deprecated action or connector schema, causing configuration errors rather than throttling.
- ✓
The flow is exceeding Power Platform service protection limits.
Why this is correct
HTTP 429 signals throttling, not a malformed expression or expired connection. Power Automate applies per-connection and per-flow service protection limits, so bursts of purchase-order runs exceeding those request thresholds cause intermittent failures until the retry window resets.
- ✗
The data source is temporarily unavailable.
Why it's wrong here
A 429 signals the service rejected the request due to rate limiting, not that the source is down; an unavailable data source yields connection or timeout errors instead. Transient source outages are addressed with retry policies, not throttling limits.
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.