최신 S90.09 무료덤프 - SOA Design & Architecture Lab
The Client and Vendor services are agnostic services that are both currently part of
multiple service compositions. As a result, these services are sometimes subjected to
concurrent access by multiple service consumers.
The Client service is an entity service that primarily provides data access logic to a client
database but also provides some calculation logic associated with determining a client's
credit rating. The Vendor service is also an entity service that provides some data access
logic but can also generate various dynamic reports.
After reviewing historical statistics about the runtime activity of the two services, it was
discovered that the majority of concurrent runtime access is related to the processing of
business rules. With the Client service, it is the calculation logic that is frequently required
and with the Vendor service it is the dynamic reporting logic that needs to be accessed
separately from the actual report generation.
Currently, due to the increasing amount of concurrent access by service consumers, the
runtime performance of both the Client and Vendor services has worsened and has
therefore reduced their effectiveness as service composition members. What steps can be
taken to solve this problem without introducing new services?
multiple service compositions. As a result, these services are sometimes subjected to
concurrent access by multiple service consumers.
The Client service is an entity service that primarily provides data access logic to a client
database but also provides some calculation logic associated with determining a client's
credit rating. The Vendor service is also an entity service that provides some data access
logic but can also generate various dynamic reports.
After reviewing historical statistics about the runtime activity of the two services, it was
discovered that the majority of concurrent runtime access is related to the processing of
business rules. With the Client service, it is the calculation logic that is frequently required
and with the Vendor service it is the dynamic reporting logic that needs to be accessed
separately from the actual report generation.
Currently, due to the increasing amount of concurrent access by service consumers, the
runtime performance of both the Client and Vendor services has worsened and has
therefore reduced their effectiveness as service composition members. What steps can be
taken to solve this problem without introducing new services?
정답: A
Service A is a task service that sends Service B a message (2) requesting that Service B
return data back to Service A in a response message (3). Depending on the response
received. Service A may be required to send a message to Service C (4) for which it
requires no response.
Before it contacts Service B, Service A must first retrieve a list of code values from its own
database (1) and then place this data into its own memory. If it turns out that it must send a
message to Service C, then Service A must combine the data it receives from Service B
with the data from the code value list in order to create the message it sends to Service C.
If Service A is not required to invoke Service C, it can complete its task by discarding the
code values.
Service A and Service C reside in Service Inventory A.
Service B resides in Service Inventory B.
You are told that the services in Service Inventory A were designed with service contracts
based on different design standards than the services in Service Inventory B.
As a result,Service A and Service B use different data models to represent the data they need to
exchange. Therefore, Service A and Service B cannot currently communicate.
Furthermore, Service C is an agnostic service that is heavily accessed by many concurrent
service consumers. Service C frequently reaches its usage thresholds during which it is not
available and messages sent to it are not received. How can this service composition
architecture be changed to avoid these problems?
return data back to Service A in a response message (3). Depending on the response
received. Service A may be required to send a message to Service C (4) for which it
requires no response.
Before it contacts Service B, Service A must first retrieve a list of code values from its own
database (1) and then place this data into its own memory. If it turns out that it must send a
message to Service C, then Service A must combine the data it receives from Service B
with the data from the code value list in order to create the message it sends to Service C.
If Service A is not required to invoke Service C, it can complete its task by discarding the
code values.
Service A and Service C reside in Service Inventory A.
Service B resides in Service Inventory B.
You are told that the services in Service Inventory A were designed with service contracts
based on different design standards than the services in Service Inventory B.
As a result,Service A and Service B use different data models to represent the data they need to
exchange. Therefore, Service A and Service B cannot currently communicate.
Furthermore, Service C is an agnostic service that is heavily accessed by many concurrent
service consumers. Service C frequently reaches its usage thresholds during which it is not
available and messages sent to it are not received. How can this service composition
architecture be changed to avoid these problems?
정답: B
Service A is an orchestrated task service that is invoked by a separate composition initiator
(1) and then sends a request message to Service C (2). Service C queries Database B to
retrieve a large data record (3) and provides this data in a response message that is sent
back to Service A.
Service A temporarily stores this data in a central state database (4) and
then sends a request message to Service D (5), which accesses a legacy system API to
retrieve a data value (6). Service D then sends this data value in a response message back
to Service A.
The data in the state database is subsequently retrieved by Service A (7) and
merged with the newly received data value. This combined data is written to Database A
(8), which triggers an event that results in the invocation of Service B (9).
Service B is an orchestrated task service that sends a request message to Service D (10).
which accesses a legacy system API to retrieve a data value (11) and then sends this data
value in a response message back to Service B.
Service B temporarily stores this data in a
central state database (12) and then sends a request message to Service E (13), which
performs a runtime calculation and then responds with the calculated data value back to
Service B.
The data in the state database is then retrieved by Service B (14) and merged
with the calculated data value. Service B then uses the merged data to complete its
business task.
The following specific problems and requirements exist:
* Database B uses a proprietary data format that is not compliant with the XML
format used by all of the services in this service composition architecture This
incompatibility needs to be solved in order to enable the described service
message exchanges.
* The service contract provided by Service D does not comply with the data model
standards that were applied to the other services and therefore uses a different
data model to represent the same type of data that is exchanged. This
incompatibility needs to be solved in order to enable communication with Service
D.
* Database B is a shared database that can be accessed by other services and
applications within the IT enterprise, which causes unpredictable runtime
performance. This performance problem needs to be solved in order to make the
runtime behavior of Service C more predictable.
* For performance and maintenance reasons, Service A and Service B need to be
deployed in the same physical environment where they can share a common state
database.
Upon reviewing these requirements it becomes evident to you that the Enterprise Service
Bus 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 Enterprise Service Bus 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 Enterprise Service Bus 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.)
(1) and then sends a request message to Service C (2). Service C queries Database B to
retrieve a large data record (3) and provides this data in a response message that is sent
back to Service A.
Service A temporarily stores this data in a central state database (4) and
then sends a request message to Service D (5), which accesses a legacy system API to
retrieve a data value (6). Service D then sends this data value in a response message back
to Service A.
The data in the state database is subsequently retrieved by Service A (7) and
merged with the newly received data value. This combined data is written to Database A
(8), which triggers an event that results in the invocation of Service B (9).
Service B is an orchestrated task service that sends a request message to Service D (10).
which accesses a legacy system API to retrieve a data value (11) and then sends this data
value in a response message back to Service B.
Service B temporarily stores this data in a
central state database (12) and then sends a request message to Service E (13), which
performs a runtime calculation and then responds with the calculated data value back to
Service B.
The data in the state database is then retrieved by Service B (14) and merged
with the calculated data value. Service B then uses the merged data to complete its
business task.
The following specific problems and requirements exist:
* Database B uses a proprietary data format that is not compliant with the XML
format used by all of the services in this service composition architecture This
incompatibility needs to be solved in order to enable the described service
message exchanges.
* The service contract provided by Service D does not comply with the data model
standards that were applied to the other services and therefore uses a different
data model to represent the same type of data that is exchanged. This
incompatibility needs to be solved in order to enable communication with Service
D.
* Database B is a shared database that can be accessed by other services and
applications within the IT enterprise, which causes unpredictable runtime
performance. This performance problem needs to be solved in order to make the
runtime behavior of Service C more predictable.
* For performance and maintenance reasons, Service A and Service B need to be
deployed in the same physical environment where they can share a common state
database.
Upon reviewing these requirements it becomes evident to you that the Enterprise Service
Bus 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 Enterprise Service Bus 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 Enterprise Service Bus 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.)
정답: B,I,L
Services A, B, and C are non-agnostic task services. Service A and Service B use the
same shared state database to defer their state data at runtime.
An assessment of these three services reveals that each contains some agnostic logic, but
because it is bundled together with the non-agnostic logic, the agnostic logic cannot be
made available for reuse.
The assessment also determines that because Service A and Service B and the shared
state database are each located in physically separate environments, the remote
communication required for Service A and Service B to interact with the shared state
database is causing an unreasonable decrease in runtime performance.
You are asked to redesign this architecture in order to increase the opportunity for agnostic
service logic to be reused and in order to decrease the runtime processing demands so
that performance can be improved. What steps can be taken to achieve these goals?
same shared state database to defer their state data at runtime.
An assessment of these three services reveals that each contains some agnostic logic, but
because it is bundled together with the non-agnostic logic, the agnostic logic cannot be
made available for reuse.
The assessment also determines that because Service A and Service B and the shared
state database are each located in physically separate environments, the remote
communication required for Service A and Service B to interact with the shared state
database is causing an unreasonable decrease in runtime performance.
You are asked to redesign this architecture in order to increase the opportunity for agnostic
service logic to be reused and in order to decrease the runtime processing demands so
that performance can be improved. What steps can be taken to achieve these goals?
정답: B