S90-04 practice question 2 of 35

Which of the following statements describe business process steps that are not suitable for service encapsulation?

Full set: 100 questions
Answer options
A: manual business process steps that cannot be automated Correct answer
B: business process steps that are related to the functional context of a business entity
C: business process steps that are performed by existing legacy systems that may introduce unacceptable performance constraints or security risks Correct answer
D: business process steps that contain decision logic based upon business rules
Correct Answer:
A. manual business process steps that cannot be automated; C. business process steps that are performed by existing legacy systems that may introduce unacceptable performance constraints or security risks
Explanation

Service encapsulation is the process of exposing business or technical logic as a formally defined service. This is only feasible for logic that can be automated and invoked programmatically.
1. Manual business process steps (A), by definition, require human intervention and cannot be automated. Therefore, they cannot be encapsulated into a software service.
2. While encapsulating logic from legacy systems (C) is a common SOA practice, it is not suitable if doing so introduces unacceptable performance degradation or security vulnerabilities. The resulting service would fail to meet fundamental quality of service requirements, making the encapsulation counterproductive and a poor design choice.

Why Incorrect

B: Business process steps related to the functional context of a business entity (e.g., "Create Invoice," "Check Customer Credit") are ideal candidates for service encapsulation as they represent core, reusable business logic. D: Business process steps containing decision logic and business rules are excellent candidates for encapsulation. This promotes the centralization and reuse of rules, a key benefit of service-orientation.

References

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

For option A: Chapter 5, "Service-Oriented Analysis," explains that the goal of the analysis is to identify logic that can be automated and represented by services. Manual processes are explicitly outside the scope of what can be encapsulated into a programmatically invokable service. (See Section 5.3, "Step 2: Decompose the business process").

For option C: Chapter 16, "Legacy Encapsulation (Service-Orientation Principle)," discusses the considerations for this pattern. It explicitly states that the service inherits the limitations of the legacy system, including performance, reliability, and security constraints. If these inherited constraints are "unacceptable" for the target consumers, the encapsulation is not a viable solution. (See "Considerations" section within Chapter 16).

For options B and D: Chapter 5, "Service-Oriented Analysis," and Chapter 6, "Service-Oriented Design," detail the process of identifying service candidates from business domains and processes. Logic tied to business entities and business rules are presented as primary sources for service capabilities.

Scroll to Top