Service Autonomy, Service Statelessness, and Service Loose Coupling are examples of:

Question

Options

• Aservice-oriented architecture types
• Bservice-orientation design principles
• Cservice models
• Dnone of the above

• A
  3% (1)
• B
  94% (34)
• D
  3% (1)

Explanation

Service Autonomy, Service Statelessness, and Service Loose Coupling are service-orientation design principles - a defined set of guidelines established by Thomas Erl that govern how services should be designed to be reusable, interoperable, and composable within a service-oriented architecture (SOA).

Why the distractors are wrong:

• A (SOA types): SOA doesn't have "types" in this context - SOA is itself an architectural style, not a category with subtypes named after these concepts.
• C (service models): Service models (e.g., entity service, task service, utility service) describe what kind of service something is based on its function, not how it should be designed.
• D (none of the above): Incorrect because B is definitively correct.

Memory tip: Think of the word "principles" - these are prescriptive rules that tell you how to design a service (stateless, autonomous, loosely coupled). If it sounds like a rule or guideline for behavior, it's a design principle, not a model or type.

No community discussion yet for this question.