S90-08 practice question 10 of 35

When applying the Messaging Metadata pattern, it is customary to place business document data in the message header and supplementary messaging metadata in the message body.

Full set: 100 questions
Answer options
A:

A. True

B:

B. False

Correct Answer:
[FALSE]
Explanation

The statement is false because it describes the inverse of the correct application of the Messaging Metadata design pattern. The fundamental principle of this pattern is to separate the primary business data from the supplementary, descriptive data used for message processing. The correct and customary implementation is to place the supplementary messaging metadata (e.g., routing information, security credentials, correlation IDs) into the message header and the primary business document data (the payload) into the message body. This allows intermediary services and messaging infrastructure to efficiently access and process the metadata in the header without needing to parse the potentially large and complex business data in the body.

Why Incorrect

The option "True" is incorrect because it endorses a flawed and inefficient implementation that contradicts the core purpose of the Messaging Metadata pattern. Placing the business document in the header and metadata in the body would force any intermediary service that needs to make a routing or processing decision to parse the entire business document, which is computationally expensive and defeats the efficiency gains the pattern is designed to provide. The message body is intended for the payload, while the header is specifically designed for lightweight, easily parsable metadata.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall. In the detailed description of the Messaging Metadata (118) pattern, the "Solution" section explicitly states: "The solution is to place the business data within the message body and the supplementary metadata in the message header." (p. 119). The problem statement for the pattern also highlights the issue of "commingling" data, which this incorrect implementation would represent.

2. Erl, T., et al. (2008). Web Service Contract Design and Versioning for SOA. Prentice Hall. Chapter 11, "Advanced Messaging," discusses the structure of SOAP messages, reinforcing the standard practice that the SOAP Header is the designated location for metadata (processing instructions, transaction information), while the SOAP Body contains the application-specific payload. This aligns directly with the principles of the Messaging Metadata pattern.

3. Papazoglou, M. P. (2012). Web Services & SOA: Principles and Technology (2nd ed.). Pearson. Chapter 7, "Messaging with SOAP," describes the structure of a SOAP message, explaining that the element is optional and "contains context information, such as security, transaction, or routing information," while the element is mandatory and "contains the application-specific message (payload)." This university-level textbook confirms the standard separation of metadata and payload.

Scroll to Top