MuleSoft Certified Platform Architect – Level 1 — Question 1
When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon. This is the only downstream API dependency of that upstream API.
Assume the downstream API runs uninterrupted without crashing.
What is the impact of this advice?
Answer options
- A. An SLA for the upstream API CANNOT be provided.
- B. The invocation of the downstream API will run to completion without timing out.
- C. A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes.
- D. A load-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes.
Correct answer: A
Explanation
The correct answer is A because without setting timeouts, the upstream API cannot guarantee a response time, making it impossible to define a reliable SLA. Option B is incorrect as it suggests the downstream API will always complete, which is not guaranteed without a timeout. Options C and D are also incorrect as they imply automatic timeouts by the Mule runtime, which contradicts the advice given.