PL-900 Practice Question: Demonstrate the capabilities of Power Automate
An operations team has a Power Automate cloud flow that reads rows from a Microsoft Dataverse table and, for each row, calls an external REST API that enforces a limit of 10 requests per second. During peak hours the flow hits '429 Too Many Requests' errors and many runs fail. The maker must reduce throttling failures while still processing every row. What should the maker do?
⚠ Common exam trap
The trap here is assuming faster processing through higher parallelism fixes throttling, when exceeding the API's rate limit is precisely what causes the 429 errors.
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
✓
Enable concurrency control on the Apply to each loop and set the degree of parallelism to a value that stays within the API limit, and configure retry policy on the HTTP action.
Throttling from a downstream API is controlled by limiting outbound request rate and gracefully retrying transient failures. Setting concurrency control on the Apply to each loop to a degree that keeps calls under ten per second, combined with a retry policy on the HTTP action, lets the flow process every row while staying inside the API's limits and absorbing occasional 429 responses.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable concurrency control on the Apply to each loop and set the degree of parallelism to a value that stays within the API limit, and configure retry policy on the HTTP action.
Why this is correct
Concurrency control on Apply to each caps how many iterations run in parallel, so the maker can keep outbound calls under ten per second, and a retry policy on the HTTP action re-sends transient 429 responses. Together they reduce throttling failures while ensuring every row is still processed.
- ✗
Add a Terminate action inside the loop that stops the flow when a 429 response is received.
Why it's wrong here
Terminating on the first 429 abandons the remaining rows, so not every record is processed. The requirement is to complete all rows while avoiding throttling, and stopping the run accomplishes neither, leaving data partially imported and requiring manual restart.
- ✗
Replace the Apply to each loop with a single HTTP action that sends all rows in one request.
Why it's wrong here
The external API is a REST endpoint that enforces per-request rate limits; batching all rows into one call is not a supported pattern here and would likely exceed payload size or still be rejected. It also changes the contract with the API and does not reliably process each row individually.
- ✗
Increase the loop's concurrency to the maximum so all rows finish before the peak window ends.
Why it's wrong here
Raising parallelism sends more simultaneous requests, which pushes the call rate even further above the API's ten-per-second ceiling and produces more 429 responses, not fewer. It accelerates failure rather than alleviating throttling, so it is the opposite of the required change.
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.