MCIA - Level 1 Exam QuestionsBrowse all questions from this exam

MCIA - Level 1 Exam - Question 7


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 API implementations are Mule applications executing in a customer-hosted Mule runtime.

End-to-end correlation of all HTTP requests and responses belonging to each individual checkout instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.

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?

Show Answer
Correct Answer: B

The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATION-ID HTTP request header in each API invocation belonging to that checkout. This approach ensures that all systems (web store backend, Experience API, and Process API) can use a consistent correlation ID throughout the entire checkout process without requiring special code or configuration in the Experience API and Process API implementations to generate and manage the correlation ID. This minimizes custom coding and configuration, making it the most efficient approach.

Discussion

10 comments
Sign in to comment
GrumpOption: B
Dec 25, 2021

B. I think. correlationId should be generated by backend to have a possibility of making POST call idempotent in case something goes wrong in HTTP calls..

awstj
Aug 19, 2021

https://help.mulesoft.com/s/article/How-to-Set-Custom-Correlation-Id-for-Flows-with-HTTP-Endpoint-in-Mule-4

Pavan_NagineniOption: B
Aug 27, 2021

B. The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATION-ID HTTP request header in each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

meet_abdel
Jan 2, 2022

Correct

1MKOption: B
Jan 23, 2022

B is most efficient

rodriguescontOption: B
Jun 9, 2022

Use the original correlation ID generated by the back-end application for the check-out permits to trace the process end-to-end

madgeezerOption: B
Aug 4, 2022

B. The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATION-ID HTTP request header in each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

Ak_2020Option: B
Sep 27, 2022

B is correct

lzrvsOption: B
Dec 20, 2022

B is correct. x-correlation-id is not a standard HTTP header.

gilofernandesOption: B
Nov 9, 2023

X-correlation-id is not a standard HTTP header and is the only way to transmit a correlation id to a mule application using an HTTP Listener