Solution logic is classified as "service-oriented" after:

Question

Options

• Ait has been built using Web services
• Bit has been built using RPC technologies
• Cit has been performance tested to a meaningful extent
• Dservice-orientation has been applied to a meaningful extent

• A
  6% (2)
• B
  3% (1)
• D
  91% (32)

Explanation

Service-orientation is a design paradigm, not a technology - solution logic earns the "service-oriented" label when the principles of service-orientation (loose coupling, abstraction, reusability, discoverability, etc.) have been meaningfully applied to its design, regardless of how it's implemented. Options A and B are wrong because they confuse the implementation technology (Web services, RPC) with the design approach; you can build with SOAP/REST or RPC and still produce tightly coupled, non-reusable logic that is not service-oriented. Option C is a red herring - performance testing validates runtime behavior but has no bearing on whether service-orientation principles were followed during design. A helpful memory tip: think of "service-oriented" the same way you'd think of "object-oriented" - calling code object-oriented doesn't mean it uses a specific language, it means OOP principles were applied; the same logic holds here.

No community discussion yet for this question.