PL-900 Practice Question: Demonstrate the capabilities of Power Automate
A flow fails with the error: 'GatewayTimeout'. The flow connects to an on-premises SQL Server via a data gateway. What is the most likely cause?
⚠ Common exam trap
It's easy for candidates to confuse a 'GatewayTimeout' with authentication or data errors, assuming the issue is with credentials or the SQL object rather than the gateway's availability or network path.
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 on-premises data gateway is not running or unreachable
The 'GatewayTimeout' error indicates that the flow successfully reached the on-premises data gateway but the gateway did not respond within the expected time frame. This typically occurs when the gateway service is not running, the machine hosting the gateway is offline, or network connectivity between the gateway and the SQL Server is broken. Incorrect credentials or missing tables would produce different errors (e.g., 'Login failed' or 'Invalid object name').
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 SQL login credentials are incorrect
Why it's wrong here
Invalid SQL credentials return an authentication failure such as Login failed for user, not GatewayTimeout; the gateway reached the server and was rejected. Credential errors are the cause when the flow reports authorisation or login failures against the data source.
- ✓
The on-premises data gateway is not running or unreachable
Why this is correct
A GatewayTimeout means the cloud service waited for the on-premises data gateway and received no response. If the gateway is stopped or unreachable, the SQL Server connection never completes, producing exactly this timeout rather than an authentication or query error.
- ✗
The SQL table does not exist
Why it's wrong here
A missing table produces an Invalid object name error returned by SQL Server, not GatewayTimeout; the query executed and the server replied. Table existence matters when the flow fails with a schema or object-not-found message rather than an unanswered request.
- ✗
The flow trigger did not fire
Why it's wrong here
A GatewayTimeout means the gateway received the request but the on-premises SQL Server did not respond within the timeout window, so the trigger firing is irrelevant — a trigger that never fired produces no run at all, not a timeout. Trigger configuration would be the suspect if the flow simply never started.
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.