PL-900 Practice Question: Demonstrate the capabilities of Power Automate
A Power Automate flow runs daily to copy data from a SQL Server database to a SharePoint list. The flow fails with a 'GatewayTimeout' error. What is the most likely cause?
⚠ Common exam trap
PL-900 often tests the difference between gateway offline and gateway timeout; candidates may pick 'gateway is offline' because it sounds like a connectivity issue, but GatewayTimeout specifically points to a slow backend response, not an unavailable gateway.
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 SQL query is taking longer than the allowed timeout.
A GatewayTimeout error in Power Automate typically indicates that the on-premises data gateway did not receive a response from the backend (SQL Server) within the allowed timeout window. The most likely cause is that the SQL query is taking longer than the gateway's timeout setting, so the gateway returns a timeout to Power Automate. Optimizing the query or increasing the timeout resolves the issue.
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 service account does not have write permission to the SharePoint list.
Why it's wrong here
A permissions failure returns an authorisation or access-denied error, not GatewayTimeout. This option is tempting because permission problems commonly break SharePoint writes, but the named error indicates the gateway connection timed out during the SQL or SharePoint operation.
- ✓
The SQL query is taking longer than the allowed timeout.
Why this is correct
GatewayTimeout errors occur when an operation exceeds the connector's allowed response window. A slow-running SQL query against the on-premises data gateway surpasses that limit, causing the flow to fail before results return, which matches the reported error precisely.
- ✗
The on-premises data gateway is offline.
Why it's wrong here
An offline gateway produces a connection or gateway-unavailable error rather than GatewayTimeout; the timeout arises when the gateway is reachable but the query or payload exceeds the limit. Offline gateways are tempting because they break on-premises connectivity, but the specific error differs.
- ✗
The flow has exceeded the daily API call limit.
Why it's wrong here
GatewayTimeout indicates the on-premises data gateway could not reach SQL Server within the timeout window, typically from network latency or an unreachable host. API call limits produce throttling errors (429), not gateway timeouts, so this misattributes the failure. The limit would be the cause only if the flow itself were being throttled by Power Platform request quotas.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 701 original PL-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.