What is typically NOT a function of the APIs created within the framework called API-led connectivity?

What is typically NOT a function of the APIs created within the framework called API-led connectivity?
A . They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.
B. They allow for innovation at the user Interface level by consuming the underlying assets without being aware of how data Is being extracted from backend systems.
C. They reduce the dependency on the underlying backend systems by helping unlock data from backend systems In a reusable and consumable way.
D. They can compose data from various sources and combine them with orchestration logic to create higher level value.

View Answer

Answer: A

Explanation

Correct Answer. They provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems. *****************************************

In API-led connectivity,

>> Experience APIs – allow for innovation at the user interface level by consuming the underlying assets without being aware of how data is being extracted from backend systems.

>> Process APIs – compose data from various sources and combine them with orchestration logic to create higher level value

>> System APIs – reduce the dependency on the underlying backend systems by helping unlock data from backend systems in a reusable and consumable way.

However, they NEVER promise that they provide an additional layer of resilience on top of the underlying backend system, thereby insulating clients from extended failure of these systems.

https://dzone.com/articles/api-led-connectivity-with-mule