A SOAP-based Web service is required to transmit an XML-based invoice document to a REST service. However, the SOAP-based Web service is designed to represent invoice data using an XML schema that…

Question

Options

• AA layer of data format transformation logic needs to be introduced based on mashup
• BA layer of protocol transformation logic needs to be introduced based on Web technologies, such
• CA layer of data model transformation logic needs to be introduced, based on XML technologies,
• DThere is no technique or technology for overcoming differences between XML schemas.

• A
  5% (3)
• B
  11% (7)
• C
  82% (54)
• D
  3% (2)

Explanation

Option C is correct because the core problem is a data model mismatch - both services use XML, but their schemas (structure, element names, types) differ. The solution is an XML transformation layer (typically using XSLT or similar XML mapping tools) that converts one schema's invoice representation into the other's, allowing the document content to be understood by both sides.

Option A is wrong because "mashup" refers to combining data or UIs from multiple sources into a new application - it addresses aggregation, not schema translation. Option B is wrong because there is no protocol disparity here; both services already communicate over HTTP/web protocols - the problem is the data format, not the transport layer. Option D is a distractor testing whether you know that XML technologies (especially XSLT) were specifically designed for exactly this kind of cross-schema transformation.

Memory tip: Match the type of mismatch to the type of transformation - different schemas = data model transformation (C), different protocols = protocol transformation (B). If both sides already speak XML over the web, the only thing left to fix is the shape of the data.

No community discussion yet for this question.