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?
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?
Setting the HTTP connection KeepAlive property to false can help prevent the plug-in from timing out when the external web service has issues or is slow to respond. This approach allows each request to the web service to use a new connection instead of maintaining a single persistent one, which can mitigate timeout issues caused by problematic or slow connections.
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/best-practices/business-logic/set-keepalive-false-interacting-external-hosts-plugin Correct answer is D. If option B instead of synchronous would put asynchronous then I would have my doubts, but synchronous is not the way to go.
This allows the plug-in to continue processing without waiting for the web service response, reducing the risk of timeouts.
IMO: D
IMO: D
If you try to use KeepAlive on a closed connection, it will cause the plug-in to fail(time out): taken from MS Docs: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/best-practices/business-logic/set-keepalive-false-interacting-external-hosts-plugin Register plugin as synchronous. It will throw an error and not timeout.
B can not be. Synchronous plug-ins have a 2-minute execution time limit.(https://learn.microsoft.com/en-us/power-apps/developer/data-platform/analyze-performance#time-and-resource-constraints) Also, KeepAlive doc: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/best-practices/business-logic/set-keepalive-false-interacting-external-hosts-plugin#symptoms
Option C (Register the plug-in step once for each web service request): By registering separate plug-in steps for each web service request, you allow each request to be processed independently. This prevents timeouts for the overall plug-in if one request is slow or experiencing issues. This is the best approach for ensuring that each external service request is handled without affecting others. Option D (Set the HTTP connection KeepAlive property to false): Setting the HTTP KeepAlive property to false would disable persistent connections, which could reduce the efficiency of multiple web service requests. However, this setting wouldn't necessarily help with timeouts related to the speed or availability of the web service.