A message payload is modified using a Message Enricher scope with an empty target. What is true about the message payload that leaves the Message Enricher scope?

A message payload is modified using a Message Enricher scope with an empty target. What is true about the message payload that leaves the Message Enricher scope?

• A. The payload returns to the original payload
• B. The payload is replaced with a null value
• C. The payload becomes an empty map
• D. The payload is discarded

Answer: (A)

The key idea is how a Message Enricher writes its result. When you configure the enricher with no target specified, there’s nowhere to write the enriched data back into the message. As a result, the enrichment doesn’t alter the payload that leaves the scope—the payload remains exactly what it was when it entered the enricher. In other words, leaving the enricher scope preserves the original payload. This isn’t about the data being set to null, an empty map, or being discarded; it’s simply that without a target, there’s no write-back path for the enrichment, so the existing payload is carried forward unchanged.

The key idea is how a Message Enricher writes its result. When you configure the enricher with no target specified, there’s nowhere to write the enriched data back into the message. As a result, the enrichment doesn’t alter the payload that leaves the scope—the payload remains exactly what it was when it entered the enricher. In other words, leaving the enricher scope preserves the original payload.

This isn’t about the data being set to null, an empty map, or being discarded; it’s simply that without a target, there’s no write-back path for the enrichment, so the existing payload is carried forward unchanged.