S90-08 practice question 11 of 35

The Messaging Metadata pattern requires a messaging framework that supports the processing of messages with headers or properties.

Full set: 100 questions
Answer options
A:

A. True

B:

B. False

Correct Answer:
TRUE
Explanation

The Messaging Metadata design pattern is fundamentally based on the principle of augmenting a message with supplementary data (metadata) without altering the primary business payload contained within the message body. This metadata—such as correlation IDs, security tokens, or routing information—is placed into dedicated header blocks or property fields provided by the underlying messaging technology. Therefore, the successful application of this pattern is entirely contingent upon using a messaging framework that natively supports messages with distinct headers or properties that can be independently processed.

Why Incorrect

The option "False" is incorrect because it would suggest that the Messaging Metadata pattern could be implemented on a system that does not support message headers or properties. This contradicts the pattern's core solution. If metadata were embedded within the message body itself, it would violate the pattern's primary goal of separating metadata from the payload, leading to a more tightly coupled and less flexible solution. This alternative approach would not be an implementation of the Messaging Metadata pattern.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall. In Chapter 12: Service Messaging Patterns, the "Messaging Metadata (5.6)" pattern is detailed. The solution section explicitly states, "Metadata is added to the message in the form of one or more message headers" (p. 379). The "Application" section further clarifies that this pattern requires a messaging product that supports the use of message headers.

2. Arcitura Education Inc. (2022). S90.09B: Advanced SOA Design & Architecture with Services & Microservices. Module 9: Service Messaging Design Patterns. The description of the Messaging Metadata pattern establishes that its implementation relies on leveraging the header or properties feature of the messaging middleware to carry contextual and technical data separately from the business data in the message body.

Scroll to Top