S90-08 practice question 14 of 35

Each service composition within a service inventory shares the same service composition architecture.

Full set: 100 questions
Answer options
A:

A. True

B:

B. False

Correct Answer:
FALSE
Explanation

A service inventory is a collection of services designed to support the automation of various and distinct business processes across an enterprise. A service composition is created to automate a specific business process by assembling a unique set of services. Because different business processes have different requirements, logic, and steps, the corresponding service compositions that automate them will naturally have different architectures. The architecture of a composition includes the specific member services, their roles, and the sequence and logic of their invocation (orchestration). Therefore, it is incorrect to state that all compositions within an inventory share the same architecture; in fact, the opposite is expected.

Why Incorrect

The statement "True" is incorrect because it implies a rigid, one-size-fits-all approach to business process automation, which contradicts the fundamental principles of service-orientation, such as composability and agility. The primary benefit of a service inventory is to provide a flexible foundation from which diverse and customized service compositions can be built to meet specific business needs, each with its own unique architecture.

References

1. Erl, T. (2008). SOA: Principles of Service Design. Prentice Hall.

Chapter 4: SOA Design Principles, Section: Service Composability: This principle is defined as a quality where "services are designed to be composable so that they can participate as effective members of multiple service compositions." The text explains that services can be "assembled and reassembled" to form "multiple, unique compositions." This directly implies that different compositions will exist and be unique, thus having different architectures. (p. 101).

Chapter 3: Service-Orientation and the Enterprise, Section: Service Composition: A service composition is described as "an aggregate of services collectively automating a particular task or business process." The use of the word "particular" emphasizes that each composition is tailored to a specific process, and therefore will have a distinct architecture from a composition designed for a different process. (p. 41).

2. Erl, T., et al. (2009). SOA Design Patterns. Prentice Hall.

Chapter 6: Composition Design Patterns, Section: Service Composition (as a pattern): The book discusses various patterns for composing services, such as those involving different capability distributions and levels of orchestration. The existence of multiple composition patterns (e.g., Capability Composition, Capability Decomposition) itself demonstrates that not all compositions follow the same architectural structure. Different business problems will require the application of different composition patterns, leading to different architectures. (p. 130-132).

Scroll to Top