PL-900 Practice Question: Manage the Microsoft Power Platform environment
Your organization uses Power Automate to automate business processes. A flow that runs daily fails intermittently with 'HTTP 429 - Too Many Requests' errors. What should you do to resolve this issue?
⚠ Common exam trap
PL-900 often tests the misconception that throttling can be bypassed by changing triggers or using gateways, when the correct answer is always to respect the limits and implement retry/backoff logic.
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
✓
Configure retry policies with exponential backoff in the flow actions.
HTTP 429 responses indicate the flow is hitting Power Automate's service protection limits (throttling). The correct mitigation is to configure retry policies with exponential backoff on the actions that call the throttled connector, so the flow retries after increasing delays instead of failing immediately. This aligns with Microsoft's documented guidance for handling 429 errors.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the frequency of the flow to run more often.
Why it's wrong here
Running more often increases request volume against the same connector, worsening the HTTP 429 throttling rather than relieving it. It is tempting when freshness matters and limits appear generous, but the correct fix is reducing concurrency or honouring Retry-After delays between calls.
- ✗
Change the flow trigger from a schedule to an instant trigger.
Why it's wrong here
An instant trigger still calls the same connector at the same rate, so HTTP 429 throttling persists; the trigger type does not alter request volume. It is tempting for latency-sensitive, user-initiated runs, but throttling is resolved by reducing call frequency or adding retry-after handling.
- ✗
Set up an on-premises data gateway to bypass the throttling limits.
Why it's wrong here
An on-premises data gateway routes connectivity to internal systems; it does not exempt cloud connector calls from service throttling limits. It is tempting when flows must reach on-premises data sources, but HTTP 429 originates from the SaaS API's rate limits, which require backoff or reduced call frequency.
- ✓
Configure retry policies with exponential backoff in the flow actions.
Why this is correct
Exponential backoff retry policies directly address HTTP 429 throttling by spacing repeated attempts progressively further apart, letting the service's request limit reset before the next call. This satisfies the intermittent daily-flow failure constraint, since transient rate limiting resolves without manual intervention or flow redesign.
Visual reference
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.