When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API…

A Service Level Agreement (SLA) for an API typically includes performance guarantees, such as a maximum response time. If an upstream API implementation calls a downstream API without a configured timeout, the upstream API's processing thread will block and wait indefinitely for a response. Since the downstream API has no SLA and its response time is unpredictable, the upstream API's response time also becomes unbounded. This makes it impossible for the organization to offer and reliably meet a response time SLA for the upstream API, as it cannot guarantee when, or if, it will complete a request.

B. This describes the intended behavior of the single invocation but fails to address the wider architectural impact on the upstream API's reliability and contractual obligations (its SLA).

C. This is factually incorrect. The Mule runtime's HTTP Request connector does not apply a default timeout; if one is not configured, it will wait indefinitely for a response.

D. This is incorrect. Timeouts are configured in the calling (upstream) API's implementation, not the downstream one. Furthermore, the Mule runtime does not apply automatic, load-dependent timeouts.

1. MuleSoft Documentation - HTTP Request Connector: The documentation for the responseTimeout attribute states: "If a value is not provided, the connector waits indefinitely for a response." This directly refutes options C and D.

Source: MuleSoft Docs, "HTTP Request Connector Reference", section on Connection Parameters.

2. MuleSoft Whitepaper - A VSM for the Digital Age: This paper discusses the importance of SLAs in the context of an application network. It emphasizes that an API's value is tied to its contract, which includes its SLA. An unpredictable dependency without a timeout makes it impossible to define a reliable contract.

Source: MuleSoft Whitepaper, "A Value-Stream-Management Model for the Digital Age", section on "Measuring the Value of Reusable Assets".

3. MuleSoft Blog - API-led Connectivity and Microservices: Architectural articles frequently discuss resilience patterns. The absence of a timeout is an anti-pattern that leads to cascading failures, where a slow downstream service consumes all available resources in the upstream service. This directly prevents the upstream service from meeting any performance SLA.

Source: MuleSoft Blog, "Designing for Resiliency", (or similar architectural best practice articles on the official blog). The principles of timeout and circuit breaker patterns are foundational to ensuring service reliability and meeting SLAs.