Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Salesforce MuleSoft Developer II Topic 2 Question 2 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer II exam
Question #: 2
Topic #: 2
[All Salesforce MuleSoft Developer II Questions]

An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication using Anypoint MQ. Each message must be correlated against the original order ID for observability and tracing.

How should a developer propagate the order ID as the correlation ID across each message?

Show Suggested Answer Hide Answer
Suggested Answer: D

To propagate the order ID as the correlation ID across each message using Anypoint MQ, the developer should wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID. The With CorrelationID scope allows setting a custom correlation ID for any event that occurs within it. The Tracing module also enables distributed tracing across different Mule applications and services using Anypoint Monitoring. Reference: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#with-correlation-id-scope https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts


Contribute your Thoughts:

Micheline
6 months ago
Option D is the way to go, it's like having a personal assistant for your correlation ID. Why make your life harder when there's a module for that?
upvoted 0 times
...
Gearldine
6 months ago
Option A looks good, using the HTTP header is a classic move. But wait, do we even have HTTP requests in Anypoint MQ? Better stick with option B to be safe.
upvoted 0 times
...
Peggie
6 months ago
Option C is tempting, but come on, we need to have better control over the correlation ID. I'm going with option B, it's the most straightforward approach.
upvoted 0 times
Sharmaine
5 months ago
Yeah, option B definitely gives us the control we need over the correlation ID. It's the most straightforward approach.
upvoted 0 times
...
Glennis
5 months ago
I think option B is the way to go as well, it provides a clear and direct method for propagating the order ID.
upvoted 0 times
...
Francesco
5 months ago
I agree, option B seems like the best choice for maintaining control over the correlation ID.
upvoted 0 times
...
...
Gearldine
6 months ago
I'd go with option D, the Tracing module makes it so easy to manage the correlation ID. Plus, it's probably the most robust solution.
upvoted 0 times
Alaine
5 months ago
Option A might be a bit risky, relying on the underlying HTTP request of Anypoint MQ for the correlation ID.
upvoted 0 times
...
Luisa
5 months ago
I think option B could also work well, setting a custom Anypoint MQ user property for the order ID.
upvoted 0 times
...
Tanja
5 months ago
I agree, option D seems like the most reliable choice for propagating the order ID as the correlation ID.
upvoted 0 times
...
...
Eric
7 months ago
Option B seems like the way to go, keep it simple and custom. Why overcomplicate things when Anypoint MQ has built-in user properties?
upvoted 0 times
William
6 months ago
I agree, using custom Anypoint MQ user properties for propagating the order ID is a straightforward approach.
upvoted 0 times
...
Ling
6 months ago
Option B seems like the way to go, keep it simple and custom. Why overcomplicate things when Anypoint MQ has built-in user properties?
upvoted 0 times
...
...

Save Cancel