S90.09 試験問題を無料オンラインアクセス
| 試験コード: | S90.09 |
| 試験名称: | SOA Design & Architecture Lab |
| 認定資格: | SOA |
| 無料問題数: | 40 |
| 更新日: | 2026-07-25 |
Service Consumer A sends a message to Service A (1), which then forwards the message
to Service B (2). Service B forwards the message to Service C (3), which finally forwards
the message to Service D (4).
Services A, B, and C each contain logic that reads the content of the message and, based
on this content, determines which service to forward the message to. As a result, what is
shown in the Figure is one of several possible runtime scenarios.
Currently, this service composition architecture is performing adequately, despite the
number of services that can be involved in the transmission of one message. However, you
are told that new logic is being added to Service A that will require it to compose one other
service in order to retrieve new data at runtime that Service A will need access to in order
to determine where to forward the message to. The involvement of the additional service
will make the service composition too large and slow. What steps can be taken to improve
the service composition architecture while still accommodating the new requirements and
avoiding an increase in the amount of service composition members?
Upon reviewing these requirements it becomes evident to you that the Orchestration
compound pattern will need to be applied. However, there are additional requirements that
need to be fulfilled. To build this service composition architecture, which patterns that is not
associated with the Orchestration compound pattern need to also be applied? (Be sure to
choose only those patterns that relate directly to the requirements described above.
Patterns associated with the Orchestration compound pattern include both the required or
core patterns that are part of the basic compound pattern and the optional patterns that can
extend the basic compound pattern.)
Service A is a task service that is required to carry out a series of updates to a set of
databases in order to complete a task. To perform the database updates Service A must
interact with three other services, each of which provides standardized data access
capabilities.
Service A sends its first update request message to Service B (1), which then responds
with a message containing a success or failure code (2). Service A then sends its second
update request message to Service C (3), which also responds with a message containing
a success or failure code (4). Finally, Service A sends a request message to Service D (5),
which responds with its own message containing a success or failure code (6).
You've been given a requirement that all database updates must either be completed
successfully or not at all. This means that if any of the three response messages received
by Service A contain a failure code, all of the updates carried out until that point must be
reversed. Note that if Service A does not receive a response message back from Services
B, C, or D, it must assume that a failure has occurred. How can this service composition
architecture be changed to fulfill these requirements?
You are told that in this service composition architecture, all four services are exchanging
invoice-related data in an XML format. The services in Service Inventory A are
standardized to use a specific XML schema for invoice data. Design standards were not
applied to the service contracts used in Service Inventory B, which means that each
service uses a different XML schema for the same kind of data. Database A and Database
B can only accept data in the Comma Separated Value (CSV) format and therefore cannot
accept XML formatted data. What steps can be taken to enable the planned data exchange
between these four services?
When Service A receives a message from Service Consumer A(1),the message is
processed by Component A.
This component first invokes Component B (2), which uses
values from the message to query Database A in order to retrieve additional data.
Component B then returns the additional data to Component A.
Component A then invokes Component C (3), which interacts with the API of a legacy
system to retrieve a new data value. Component C then returns the data value back to
Component A.
Next, Component A sends some of the data it has accumulated to Component D (4), which
writes the data to a te>X file that is placed in a specific folder. Component D then waits
until this file is imported into a different system via a regularly scheduled batch import.
Upon completion of the import, Component D returns a success or failure code back to
Component A.
Component A finally sends a response to Service Consumer A (5) containing all of the data
collected so far and Service Consumer A writes all of the data to Database B (6).
Components A, B, C.
and D belong to the Service A service architecture. Database A, the
legacy system, and the file folders are shared resources within the IT enterprise.
Service A is an entity service with a service architecture that has grown over the past few
years. As a result of a service inventory-wide redesign project, you are asked to revisit the
Service A service architecture in order to separate the logic provided by Components B, C,
and D into three different utility services without disrupting the behavior of Service A as it
relates to Service Consumer A . What steps can be taken to fulfill these requirements?