nerdexam
Microsoft

PL-400 · Question #423

A company requires a plug-in that makes multiple requests to an external web service. The plug- in must not time out when the web service has issues or is slow to respond. You need to create the…

The correct answer is C. Set the HTTP connection timeout value explicitly to limit how long each connection can remain. To prevent a plug-in from timing out when an external web service is slow, the most effective solution is to explicitly set a higher HTTP connection timeout value for the requests made within the plug-in.

Submitted by omar99· Apr 18, 2026

Question

A company requires a plug-in that makes multiple requests to an external web service. The plug- in must not time out when the web service has issues or is slow to respond. You need to create the plug-in. What should you do?

Options

  • ARegister the plug-in to run synchronously.
  • BRegister the plug-in by using isolation mode = none.
  • CSet the HTTP connection timeout value explicitly to limit how long each connection can remain
  • DRegister the plug-in step once for each web service request.

How the community answered

(42 responses)
  • A
    10% (4)
  • B
    2% (1)
  • C
    81% (34)
  • D
    7% (3)

Why each option

To prevent a plug-in from timing out when an external web service is slow, the most effective solution is to explicitly set a higher HTTP connection timeout value for the requests made within the plug-in.

ARegister the plug-in to run synchronously.

Registering a synchronous plug-in makes it subject to a strict 2-minute timeout, which will likely cause the plug-in itself to time out if the external web service is slow, rather than preventing timeouts.

BRegister the plug-in by using isolation mode = none.

Registering a plug-in with `isolation mode = none` is unsupported and a security vulnerability in Dataverse, and it does not affect external web service timeouts.

CSet the HTTP connection timeout value explicitly to limit how long each connection can remainCorrect

When an external web service is slow to respond, the default HTTP connection timeout might be too short, causing requests to fail prematurely. Explicitly setting a higher timeout value on the `HttpClient` or `HttpWebRequest` object within the plug-in allows more time for the web service to process and return a response, thus preventing timeouts.

DRegister the plug-in step once for each web service request.

Registering plug-in steps defines the trigger points for plug-in execution, not the timeout behavior of HTTP requests made by the plug-in to external web services.

Concept tested: Dataverse plug-in external web service HTTP timeout

Source: https://learn.microsoft.com/en-us/power-apps/developer/dataverse/best-practices/business-logic/external-web-service-callouts

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice