S90-08 practice question 6 of 35

By applying the Service Broker compound pattern, you establish an environment capable of carrying out which of the following patterns?

Full set: 100 questions
Answer options
A: Data Model Transformation Correct answer
B: Data Format Transformation Correct answer
C: Transaction Protocol Transformation
D: Policy Transformation
Correct Answer:
A. Data Model Transformation; B. Data Format Transformation
Explanation

The Service Broker is a compound design pattern that establishes a centralized intermediary for message processing, routing, and transformation. Its core purpose is to decouple services by handling incompatibilities between them. This explicitly includes the capability to transform message payloads by applying both the Data Model Transformation pattern (to alter the data's semantic structure between different schemas) and the Data Format Transformation pattern (to convert the message's physical format, such as from XML to JSON). These patterns are fundamental components that can be realized within a Service Broker implementation.

Why Incorrect

C. Transaction Protocol Transformation: This is not a standard Arcitura design pattern. The related pattern is Protocol Bridging, which handles transformations between communication protocols (e.g., HTTP to JMS), not specifically "transaction protocols."
D. Policy Transformation: A service broker typically acts as a policy enforcement point, applying existing policies to messages. It is not primarily designed to perform "policy transformation" as a distinct function.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall.

Page 498, Section 15.3 (Service Broker): The text and diagrams explicitly state that the Service Broker pattern is a compound pattern that can be composed of several other patterns, including Data Model Transformation and Data Format Transformation. Figure 15.11 illustrates this composition.

Page 388, Section 12.2 (Data Model Transformation): Describes the pattern that a Service Broker can implement to resolve schematic dissimilarities between services.

Page 394, Section 12.3 (Data Format Transformation): Details the pattern for converting data between different formats, a common function applied within a Service Broker.

Scroll to Top