S90-04 practice question 19 of 35

What is the primary difference between designing a task service and an orchestrated task service?

Full set: 100 questions
Answer options
A: A task service does not need to be part of a service composition, whereas an orchestrated task service always does.
B: The scope of logic encapsulated by a task service tends to be smaller than an orchestrated task service. Correct answer
C: A task service is delivered as a single-purpose service, whereas an orchestrated task service is expected to be agnostic and therefore multi-purpose.
D: None of the above.
Correct Answer:
B. The scope of logic encapsulated by a task service tends to be smaller than an orchestrated task service.
Explanation

The primary design difference lies in the scope of the encapsulated business logic. A standard task service is designed to automate a single, specific business task (e.g., "Validate Customer Credit"). An orchestrated task service, by contrast, is a composite service that automates a broader business process by coordinating and sequencing calls to other, more granular services (which can include other task services). Therefore, the scope of the logic within an orchestrated task service, which includes the entire process flow, is inherently larger and more complex than that of a single task service.

Why Incorrect

A. An orchestrated task service is a composition controller, but a standard task service is also frequently designed to be a composable part of a larger business process.
C. Both task services and orchestrated task services are typically non-agnostic, as they are designed to automate specific business processes. Agnosticism is a primary goal for entity and utility services, not task-centric ones.
D. Option B accurately describes the primary difference in scope and complexity between the two service types, making this option incorrect. ---

References

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

Page 358, Section 10.2, "Composition Roles": This section distinguishes between the "composition member" and the "composition controller." A standard task service is a composition member, while an orchestrated task service acts as the composition controller, governing the overall process logic. This directly supports the idea of a larger scope for the orchestrated service.

Page 268, Section 8.3, "Service Models": This section describes the Task Service model as representing a specific business task. In contrast, the concept of a Process Service (functionally equivalent to an orchestrated task service) is introduced as encapsulating an entire business process workflow, highlighting the difference in scope.

2. Arcitura Education Inc. (2017). Module 3: SOA Design & Architecture Lab. S90.03B SOA Design & Architecture Lab Course Booklet.

Section "Task Services" and "Orchestrated Task Services": The official courseware explains that while a task service encapsulates logic for a single unit of work, an orchestrated task service is a compound service that contains the parent business process logic required to compose other services. This confirms the scope of an orchestrated service is larger as it encompasses the coordination of multiple services.

Scroll to Top