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 D. Set the HTTP connection timeout value explicitly to limit how long each connection can remain. When a Dataverse plugin makes HTTP calls to an external web service, the default .NET HttpWebRequest timeout may be too long or even indefinite, causing the plugin to hang and exceed Dataverse's own sandbox execution time limit. By explicitly setting the HTTP connection timeout…

Submitted by jian89· 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

ASend requests to use multiple threads.
BRegister the plug-in to run synchronously.
CRegister the plug-in step once for each web service request.
DSet the HTTP connection timeout value explicitly to limit how long each connection can remain

How the community answered

(33 responses)

A
12% (4)
B
6% (2)
C
3% (1)
D
79% (26)

Explanation

When a Dataverse plugin makes HTTP calls to an external web service, the default .NET HttpWebRequest timeout may be too long or even indefinite, causing the plugin to hang and exceed Dataverse's own sandbox execution time limit. By explicitly setting the HTTP connection timeout (e.g., via HttpWebRequest.Timeout or HttpClient.Timeout), you bound how long each request can wait, allowing the plugin to fail gracefully instead of becoming unresponsive. Option A (multithreading) does not prevent timeouts. Option B (synchronous registration) would make the problem worse by blocking the Dataverse pipeline. Option C (multiple step registrations) affects when the plugin fires, not how it handles slow HTTP responses.

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice