Assuming that external web service response time can’t be improved, what changes can be made to the custom Visaualforce page and Apex Controller to avoid hitting the Apex Concurrent limit?
Universal Containers has a custom Visualforce page that makes a callout to an external service to show historical sales data from the warehouse. Due to heavy usage and slow response time of the external web service, Salesforce continues to hit the Apex Concurrent limit.
Assuming that external web service response time can’t be improved, what changes can be made to the custom Visaualforce page and Apex Controller to avoid hitting the Apex Concurrent limit?
A . Use @future annotation to make the HTTP Callout.
B . Replace the standard HTTP Callout with Continuation.
C . Invoke a Workflow Outbound message from the Apex trigger.
D . Set a timeout on the web service HTTP callout.
Answer: B
Latest Integration Architecture Designer Dumps Valid Version with 141 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund