S90-08 practice question 24 of 35

The Protocol Bridging and Data Model Transformation patterns can be applied together to the same message or data exchange.

Full set: 100 questions
Answer options
A:

A. True

B:

B. False

Correct Answer:
TRUE
Explanation

The Protocol Bridging and Data Model Transformation patterns address two distinct but often concurrent interoperability challenges. Protocol Bridging resolves mismatches in communication protocols (e.g., bridging HTTP and JMS), while Data Model Transformation resolves mismatches in the structure and syntax of the data itself (e.g., converting one XML schema to another, or XML to JSON). In many enterprise integration scenarios, systems differ in both the protocol they use and the data model they expect. Therefore, it is a common and valid design to apply both patterns together within a single integration solution to mediate a message exchange between two disparate services.

Why Incorrect

The answer "False" would be incorrect because it implies that these patterns are mutually exclusive. In practice, they are highly complementary. A middleware component, such as an Enterprise Service Bus (ESB) or an integration broker, frequently performs protocol bridging and data model transformation as part of the same message processing flow. Denying their combined application would contradict fundamental principles of service and enterprise integration architecture.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall. In Chapter 17: Service Integration Patterns, the text describes both the Protocol Bridging pattern (Section 17.2) and the Data Model Transformation pattern (Section 17.3). The book emphasizes the composability of patterns to solve larger problems. The context of service integration inherently suggests that a message arriving via one protocol may need its data transformed before being sent out via another protocol, demonstrating the combined application.

2. Arcitura Education Inc. (2017). S90.09A: SOA Design & Architecture Lab 9 - Service implementation, positioning and integration. The lab exercises and course materials for this module frequently involve creating integration solutions where a service bus or mediator component must handle both protocol and data format differences, requiring the practical application of both patterns in conjunction.

3. Erl, T., et al. (2016). Next Generation SOA: A Concise Introduction to Service Technology & Service-Orientation. Prentice Hall. Chapter 11: "Fundamental Service-Orientation & Enterprise Architecture" discusses the role of middleware in resolving technical heterogeneity, which encompasses both protocol and data format incompatibilities, implicitly supporting the combined use of patterns that address these issues.

Scroll to Top