List of questions
Related questions
Question 19 - MCIA - Level 1 discussion
Refer to the exhibit.
A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all APIimplementations are Mule applications executing in a customer -hosted Mule runtime.
End-to-end correlation of all HTTP requests and responses belonging to each individual checkoutInstance is required. This is to be done through a common correlation ID, so that all log entrieswritten by the web store backend, Experience API implementation, and Process API implementationinclude the same correlation ID for all requests and responses belonging to the same checkoutinstance.
What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?
0 comments
Leave a comment first