An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.
For this reason, a fallback API is to be called when the Order API is unavailable.
What approach to designing the invocation of the fallback API provides the best resilience?
To handle the high availability of the API effectively, it's optimal to configure the HTTP Requester component to automatically invoke a fallback API whenever the primary Order API returns an HTTP 4xx or 5xx response status code. This method directly addresses the scenario where the Order API is down due to client or server errors, ensuring that a fallback mechanism is instantly in place without needing additional client-side redirection or manual intervention. It provides a seamless and resilient strategy for maintaining service continuity.
Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API
Answer should be A.
Answer: A