PL-400 · Question #64
Case Study 2 - Adventure Works Background Current environment Adventure Works Cycles wants to replace their paper-based bicycle manufacturing business with an efficient paperless solution. The…
The correct answer is C. Add a timeout setting to the approval flow. When an approval flow in Power Automate may stall because an approver does not respond, adding a timeout setting to the approval action is the correct solution. Power Automate's approval action includes a built-in timeout configuration that specifies how long the flow waits…
Question
Options
- AAdd a data operation that specifies the false conditions.
- BAdd a configure run that is set to Is successful.
- CAdd a timeout setting to the approval flow.
- DAdd b condition containing approval hierarchy.
How the community answered
(57 responses)- A5% (3)
- B11% (6)
- C82% (47)
- D2% (1)
Explanation
When an approval flow in Power Automate may stall because an approver does not respond, adding a timeout setting to the approval action is the correct solution. Power Automate's approval action includes a built-in timeout configuration that specifies how long the flow waits before continuing or branching to an alternative path (such as auto-escalation or auto-rejection). Option A (adding a data operation for false conditions) does not address the timing issue. Option B (configure run after set to 'Is successful') only controls flow execution on success, not on non-response. Option D (adding a condition for approval hierarchy) addresses routing logic, not timeout behavior. The timeout setting directly solves the scenario where an approver is unresponsive, ensuring the flow does not wait indefinitely.
Community Discussion
No community discussion yet for this question.