MENU
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?
Suggested Answer: D
Get Premium Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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
29 comments · newest first
FR
Francine
11 months ago
D seems a bit overkill for just propagating an ID, right?
AN
Anjelica
11 months ago
A is a solid choice too, headers are straightforward.
RA
Rasheeda
11 months ago
Wait, does Anypoint MQ really auto-propagate the correlation ID? Sounds too easy.
IR
Irving
11 months ago
Definitely agree with B, it gives more control!
OL
Olen
12 months ago
I think option B is the way to go for custom properties.
KI
Kirk
12 months ago
I think wrapping the publish operations in a With CorrelationID scope from the Tracing module, as in option D, is a solid method. It aligns with what we practiced about ensuring traceability.
HE
Heike
1 year ago
I recall a similar question where we had to set headers for observability. Using the 'X-CORRELATION_ID' header in option A could work, but I'm not confident it's the best approach.
RO
Rodolfo
1 year ago
I'm not entirely sure, but I think the default correlation ID might not be sufficient for our needs. Option C feels a bit too simplistic for this scenario.
BO
Bobbye
1 year ago
I remember we discussed using custom properties in Anypoint MQ during our practice sessions. Option B seems like a good choice for propagating the order ID.
TO
Tony
1 year ago
I'm leaning towards option A. Setting the 'X-CORRELATION_ID' header on the underlying HTTP request seems like a straightforward way to propagate the order ID. As long as the receiving applications are looking for that header, it should work well.
GA
Gabriele
1 year ago
Option D seems like the most robust solution to me. Using the Tracing module to wrap the Anypoint MQ Publish operations and set the correlation ID to the order ID should ensure consistent tracing across the system.
LI
Lindsey
1 year ago
This looks like a pretty straightforward question. I think I'll go with option B - setting a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
CH
Cheryll
1 year ago
Hmm, I'm a bit unsure about this one. I'm not super familiar with Anypoint MQ, so I'll need to think through the different options carefully. Maybe I'll start by reviewing the documentation on correlation IDs and message propagation.
CH
Cherri
1 year ago
This looks like a tricky question. I'll need to think through the different options carefully.
MA
Mari
1 year ago
Hmm, I'm a bit confused about the difference between the services that are installed on the Backup Exec server and the ones available on the remote computer. I'll need to carefully read through the options to figure this out.
AL
Aleta
1 year ago
Okay, let me think this through. A digital certificate is used to verify the identity of the person or entity you're communicating with, so it must be verifying the public key. I'll go with option A.
MI
Micheline
2 years 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?
GE
Gearldine
2 years 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.
PE
Peggie
2 years 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.
SH
Sharmaine
2 years ago
Yeah, option B definitely gives us the control we need over the correlation ID. It's the most straightforward approach.
GL
Glennis
2 years ago
I think option B is the way to go as well, it provides a clear and direct method for propagating the order ID.
FR
Francesco
2 years ago
I agree, option B seems like the best choice for maintaining control over the correlation ID.
GE
Gearldine
2 years 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.
AL
Alaine
2 years ago
Option A might be a bit risky, relying on the underlying HTTP request of Anypoint MQ for the correlation ID.
LU
Luisa
2 years ago
I think option B could also work well, setting a custom Anypoint MQ user property for the order ID.
TA
Tanja
2 years ago
I agree, option D seems like the most reliable choice for propagating the order ID as the correlation ID.
ER
Eric
2 years 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?
WI
William
2 years ago
I agree, using custom Anypoint MQ user properties for propagating the order ID is a straightforward approach.
LI
Ling
2 years 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?