Refer to the exhibit.
What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and of System APIs?
Refer to the exhibit.
What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and of System APIs?
The best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs is to use a Process API to orchestrate calls to multiple System APIs, but not to other Process APIs. This ensures a clear separation of concerns and promotes an organized, layered architecture. The System APIs handle the core systems and data access, the Process APIs handle the business logic and orchestration, while the Experience APIs manage the interaction with end-user applications. Keeping the Process APIs from calling other Process APIs prevents unnecessary complexity and potential circular dependencies.
A PAPI may call another PAPI. Moreover, it is not a general rule to stick by one EAPI, PAPI and SAPI to represent a business requirement. In fact, we may have several EAPI and PAPI, that may interact with each other. Finally, the data customization to return to the end user is typically performed at the upper layer, the EAPI. Therefore, the answer is B
B. Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.
B correct
All SAPi can be access through one PAPI, no need of other PAPI.
in question we have ' one end-to-end business process ' so B is not right .
A, id PAPI is available to orchestrate multiple system API no need to have future API.
Answer: B
B. Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.
Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs
It should not be B allow system apis to return data that is not currently required by identified process or experience api. There is no best practice by Mule restricting only one implementation per layer.
Answer: B