What approach to designing the invocation of the fallback API provides the best resilience?

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?
A . Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order AP
C . Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable.
D . Redirect client requests through an HTTP 307 Temporary Redirectstatus code to the fallback API whenever the Order API is unavailable.
E . Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order AP

View Answer

Answer: A