S90-09A · Question #40
Upon reviewing these requirements it becomes evident to you that the Orchestration compound pattern will need to be applied. However, there are additional requirements that need to be fulfilled. To…
The correct answer field appears blank in your question - the correct answer wasn't included. However, based on SOA pattern theory (Thomas Erl's SOA Design Patterns), I can still give you a solid explanation. --- Patterns associated with the Orchestration compound pattern (and…
Question
Upon reviewing these requirements it becomes evident to you that the Orchestration compound pattern will need to be applied. However, there are additional requirements that need to be fulfilled. To build this service composition architecture, which patterns that is not associated with the Orchestration compound pattern need to also be applied? (Be sure to choose only those patterns that relate directly to the requirements described above. Patterns associated with the Orchestration compound pattern include both the required or core patterns that are part of the basic compound pattern and the optional patterns that can extend the basic compound pattern.)
Options
- AAtomic Service Transaction
- BCompensating Service Transaction
- CData Format Transformation
- DData Model Transformation
- EEvent-Driven Messaging
- FIntermediate Routing
- GPolicy Centralization
- HProcess Centralization
- IProtocol Bridging
- JRedundant Implementation
Explanation
The correct answer field appears blank in your question - the correct answer wasn't included. However, based on SOA pattern theory (Thomas Erl's SOA Design Patterns), I can still give you a solid explanation.
Patterns associated with the Orchestration compound pattern (and therefore excluded from the answer) include:
| Category | Patterns |
|---|---|
| Required/Core | Process Centralization (H), Capability Composition |
| Optional extensions | Atomic Service Transaction (A), Compensating Service Transaction (B), Event-Driven Messaging (E), Intermediate Routing (F), Policy Centralization (G), Redundant Implementation (J) |
This means the patterns not associated with Orchestration - and therefore candidates for the correct answer - are:
- C. Data Format Transformation - handles mismatched message formats between services
- D. Data Model Transformation - reconciles semantic/structural differences in data models
- I. Protocol Bridging - enables communication across incompatible protocols
Why the distractors (A, B, E, F, G, H, J) are wrong: They are all listed in the Orchestration compound pattern itself (either as core or optional patterns), so the question explicitly tells you to exclude them.
Memory tip: Think of C, D, and I as the "translation trio" - format, model, and protocol. They're interoperability patterns, not orchestration patterns. Orchestration handles flow; the translation trio handles communication compatibility - two separate concerns.
If you have the full scenario text and/or the correct answer, share it and I can refine this explanation further.
Topics
Community Discussion
No community discussion yet for this question.