Which of the following service designs are considered not supportive of service-orientation due to improper selection of technologies? SELECT ALL THAT APPLY

Question

Options

• AA REST service designed to respond to service consumers via standard HTTP response codes.
• BA SOAP-based Web service designed with a service contract that includes WS-Policy definitions
• CA reusable component-based service designed to reject messages containing XML so as to limit
• DA SOAP-based Web service designed with a decoupled service contract that includes a

• A
  25% (8)
• B
  63% (20)
• D
  13% (4)

Explanation

Options B and C represent poor technology choices that undermine core service-orientation principles. Option C is the clearest violation: a service that rejects XML messages actively breaks interoperability, since XML is the foundational data format of web service communication - excluding it contradicts the very standard on which service-oriented messaging is built. Option B is problematic because including WS-Policy definitions in a service contract imposes technology-specific runtime requirements on consumers, creating technology coupling that violates the neutrality principle - consumers must support those specific policy assertions to interact with the service.

Option A is a distractor because using standard HTTP response codes in a REST service is precisely the right technology choice - leveraging established, neutral standards is a hallmark of good service design. Option D is a distractor because a decoupled service contract is a best practice that supports service-orientation by reducing dependency between the service and its consumers.

Memory tip: Ask yourself, "Does this technology choice restrict who can use the service or break a widely accepted standard?" If yes, it's likely not supportive. Think R.I.P. - Reject standards, Impose coupling, Proprietary lock-in = bad service design.

No community discussion yet for this question.