Salesforce-MuleSoft-Platform-Architect Practice Test
152 Questions
An Order API triggers a sequence of other API calls to look up details of an order's items in a back-end inventory database. The Order API calls the OrderItems process API, which calls the Inventory system API. The Inventory system API performs database operations in the back-end inventory database.
The network connection between the Inventory system API and the database is known to be unreliable and hang at unpredictable times.
Where should a two-second timeout be configured in the API processing sequence so that the Order API never waits more than two seconds for a response from the Orderltems process API?
A. In the Orderltems process API implementation
B. In the Order API implementation
C. In the Inventory system API implementation
D. In the inventory database
Explanation:
To guarantee that the Order API never waits more than two seconds for a response from its upstream OrderItems Process API, you must configure the timeout on the HTTP Request connector in the Order API itself. Setting a 2000 ms response timeout in the Order API’s HTTP Request operation ensures that if the Process API call hangs, the HTTP operation will fail fast after two seconds and allow the Order API to handle the error accordingly. By default, Mule’s HTTP connector uses a 30 000 ms (30 s) response timeout; you can override this per-connector instance using the “Response timeout” attribute. Configuring the timeout in downstream components or at the database level does not prevent the Order API from waiting indefinitely on the HTTP call.
| Salesforce-MuleSoft-Platform-Architect Practice-Test - Home | Previous |
| Page 6 out of 152 Pages |