ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 31 - MCIA Level 1 Maintenance discussion

Report
Export

A company is building an application network and has deployed four Mule APIs: one experience API, one process API, and two system APIs. The logs from all the APIs are aggregated in an external log aggregation tool. The company wants to trace messages that are exchanged between multiple API implementations. What is the most idiomatic (based on its intended use) identifier that should be used to implement Mule event tracing across the multiple API implementations?

A.
Mule event ID
Answers
A.
Mule event ID
B.
Mule correlation ID
Answers
B.
Mule correlation ID
C.
Client's IP address
Answers
C.
Client's IP address
D.
DataWeave UUID
Answers
D.
DataWeave UUID
Suggested answer: B

Explanation:

Correct answer is Mule correlation ID By design, Correlation Ids cannot be changed within a flow in Mule 4 applications and can be set only at source. This ID is part of the Event Context and is generated as soon as the message is received by the application. When a HTTP Request is received, the request is inspected for "X-Correlation-Id" header. If "X-Correlation-Id" header is present, HTTP connector uses this as the Correlation Id. If "X-Correlation-Id" header is NOT present, a Correlation Id is randomly generated. For Incoming HTTP Requests: In order to set a custom Correlation Id, the client invoking the HTTP request must set "X-Correlation-Id" header. This will ensure that the Mule Flow uses this Correlation Id. For Outgoing HTTP Requests: You can also propagate the existing Correlation Id to downstream APIs. By default, all outgoing HTTP Requests send "X-Correlation-Id" header. However, you can choose to set a different value to "X-Correlation-Id" header or set "Send Correlation Id" to NEVER.

asked 18/09/2024
Andrew ROUSE
45 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first