S90-09A · Question #30
You are told that in this service composition architecture, all four services are exchanging invoice- related data in an XML format. The services in Service Inventory A are standardized to use a…
The correct answer is A. The Data Model Transformation pattern can be applied so that data model transformation logic is. Option A is correct because the Data Model Transformation pattern is purpose-built for exactly this scenario: it externalizes transformation logic into an intermediary layer (such as an ESB or transformation service), allowing incompatible data models to interoperate without…
Question
You are told that in this service composition architecture, all four services are exchanging invoice- related data in an XML format. The services in Service Inventory A are standardized to use a specific XML schema for invoice data. Design standards were not applied to the service contracts used in Service Inventory B, which means that each service uses a different XML schema for the same kind of data. Database A and Database B can only accept data in the Comma Separated Value (CSV) format and therefore cannot accept XML formatted data. What steps can be taken to enable the planned data exchange between these four services?
Exhibit
Options
- AThe Data Model Transformation pattern can be applied so that data model transformation logic is
- BThe Data Model Transformation pattern can be applied so that data model transformation logic is
- CThe Data Model Transformation pattern can be applied so that data model transformation logic is
- DNone of the above.
How the community answered
(41 responses)- A66% (27)
- B5% (2)
- C12% (5)
- D17% (7)
Explanation
Option A is correct because the Data Model Transformation pattern is purpose-built for exactly this scenario: it externalizes transformation logic into an intermediary layer (such as an ESB or transformation service), allowing incompatible data models to interoperate without modifying the services themselves - handling both the XML schema mismatches between Service Inventories A and B, and the XML-to-CSV conversion required by the databases.
The distractor choices (B and C) likely describe incorrect placements of the transformation logic - for example, embedding it directly inside individual services rather than centralizing it, which would violate SOA design principles by coupling transformation concerns to business logic and defeating the purpose of a standardized service inventory. Option D ("None of the above") is wrong because Data Model Transformation is exactly the recognized SOA pattern for this problem.
Memory tip: Think of the Data Model Transformation pattern as a "universal adapter plug" - rather than rewiring every device (service), you plug in one adapter in the middle that speaks all the formats. If the transformation lives inside a service, it's no longer a plug; it's hardwired, which is always the wrong answer in SOA pattern questions.
Topics
Community Discussion
No community discussion yet for this question.