S90-04 practice question 32 of 35

While reviewing the logic assigned to a task service candidate, it is discovered that there is some logic that is identical to logic residing in two other service candidates. Given the discovery of this redundant logic, which of the following makes sense?

Full set: 100 questions
Answer options
A: Comments should be made in the task service candidate's service profile to note the observation about the redundant logic. If there is a need to change the logic in one place, these notes will eventually lead developers to other places where the logic should not change so as to preserve the independence of each service candidate.
B: The redundant logic should be encapsulated within a single reusable and agnostic task service candidate.
C: The redundant logic should be moved from the task service candidate to an orchestrated task service candidate.
D: None of the above. Correct answer
Correct Answer:
D. None of the above.
Explanation

The discovery of redundant logic across multiple service candidates indicates a violation of the Service Reusability principle. The correct course of action is to refactor this common logic into a single, reusable, and agnostic service. None of the provided options accurately describe this solution. Option B suggests creating an "agnostic task service," which is a contradiction; task services are by definition process-specific and non-agnostic. The appropriate service model for reusable, non-entity-specific logic is a utility service. Option C misapplies the role of an orchestrated service, which is for composition, not for housing reusable logic. Option A proposes documenting the problem instead of solving it, which increases maintenance overhead.

Why Incorrect

A: Documenting redundancy instead of eliminating it contradicts the goal of service-orientation to reduce maintenance overhead and promote standardized reuse. B: A task service is inherently non-agnostic and tied to a specific business process. Reusable, agnostic logic should be encapsulated in a utility service, not a task service. C: An orchestrated task service is a composition controller responsible for coordinating other services; it is not the appropriate location for hosting low-level, reusable business logic.

References

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

Chapter 10, Service Models, Task Services (p. 298): This section defines task services as representing a specific business task or action, making them inherently process-specific and non-agnostic. This supports why option B is incorrect.

Chapter 10, Service Models, Utility Services (p. 302): This section describes utility services as generic, reusable services that encapsulate non-business-specific functions, which is the correct model for the redundant logic in the scenario. The absence of this as an option supports the choice of D.

Chapter 8, Service Reusability (Design Principle) (p. 221): This chapter emphasizes that a key goal of service-orientation is to create reusable services to reduce waste and redundancy. This principle directly contradicts the inaction suggested in option A.

Scroll to Top