S90-09A · Question #28
Service Consumer A sends a message to Service A. There are currently three duplicate implementations of Service A (Implementation 1, Implementation 2, Implementation 3). The message sent by Service…
The correct answer is C. The Standardized Service Contract principle is applied to ensure that the new service capability is. Option C is correct because the Standardized Service Contract principle ensures that all services within the same inventory share the same design standards, conventions, and contract policies - so when the new capability is defined, all three owners have a binding contract…
Question
Service Consumer A sends a message to Service A. There are currently three duplicate implementations of Service A (Implementation 1, Implementation 2, Implementation 3). The message sent by Service Consumer A is intercepted by Service Agent A (1), which determines at runtime which implementation of Service A to forward the message to. All three implementations of Service A reside on the same physical server. You are told that after Service A was deployed, each of its three implementations was claimed by a different IT department, which means each implementation of Service A has a different owner. You are informed that a new service capability will soon need to be added to Service A . This service capability will introduce new business logic specific to Service A as well as logic required to access a shared database. What steps can be taken to ensure that the service owners will each add the service capability in a consistent manner to their respective implementations of Service A?
Exhibit
Options
- AThe Contract Centralization pattern can be applied so that when the new service capability is
- BThe Legacy Wrapper pattern can be applied to establish a new wrapper utility service that will
- CThe Standardized Service Contract principle is applied to ensure that the new service capability is
- DNone of the above.
How the community answered
(17 responses)- A12% (2)
- B24% (4)
- C59% (10)
- D6% (1)
Explanation
Option C is correct because the Standardized Service Contract principle ensures that all services within the same inventory share the same design standards, conventions, and contract policies - so when the new capability is defined, all three owners have a binding contract specification to implement against, guaranteeing consistency regardless of who does the work.
Option A (Contract Centralization) is about consolidating multiple separate service contracts into one to reduce contract sprawl; it governs how contracts are organized, not how new capabilities are consistently implemented by multiple independent owners.
Option B (Legacy Wrapper) applies when you need to expose a legacy system behind a modern service interface - there is no legacy system here, just three co-equal implementations, so wrapping is irrelevant to the problem.
Memory tip: Think of Standardized Service Contract as the "blueprint law" - just as building codes force all contractors to follow the same blueprint regardless of who owns the building, this principle forces all service owners to conform to the same capability contract. Whenever you see a question about multiple owners/teams implementing the same service consistently, reach for this principle first.
Topics
Community Discussion
No community discussion yet for this question.