최신SOA Design & Architecture Lab - S90.09무료샘플문제
문제1
Service A is an entity service that provides a set of generic and reusable service
capabilities. In order to carry out the functionality of any one of its service capabilities,
Service A is required to compose Service B (1) and Service C (2) and Service A is required
to access Database A (3), Database B (4), and Database C (5). These three databases are
shared by other applications within the IT enterprise.
All of service capabilities provided by Service A are synchronous, which means that for
each request a service consumer makes. Service A is required to issue a response
message after all of the processing has completed.
Depending on the nature of the service consumer request, Service A may be required to
hold data it receives in memory until its underlying processing completes. This includes
data it may receive from either Service A or Service B or from any of the three shared
databases.
Service A is one of many entity services that reside in a highly normalized service
inventory. Because Service A provides agnostic logic, it is heavily reused and is currently
part of many service compositions.
You are told that Service A has recently become unstable and unreliable and several of the
service consumers that access it have had to raise runtime exceptions due to these
problems. What steps can be taken to solve these problems without compromising the
normalization of the service inventory?
Service A is an entity service that provides a set of generic and reusable service
capabilities. In order to carry out the functionality of any one of its service capabilities,
Service A is required to compose Service B (1) and Service C (2) and Service A is required
to access Database A (3), Database B (4), and Database C (5). These three databases are
shared by other applications within the IT enterprise.
All of service capabilities provided by Service A are synchronous, which means that for
each request a service consumer makes. Service A is required to issue a response
message after all of the processing has completed.
Depending on the nature of the service consumer request, Service A may be required to
hold data it receives in memory until its underlying processing completes. This includes
data it may receive from either Service A or Service B or from any of the three shared
databases.
Service A is one of many entity services that reside in a highly normalized service
inventory. Because Service A provides agnostic logic, it is heavily reused and is currently
part of many service compositions.
You are told that Service A has recently become unstable and unreliable and several of the
service consumers that access it have had to raise runtime exceptions due to these
problems. What steps can be taken to solve these problems without compromising the
normalization of the service inventory?
정답: A
문제2
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?
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?
정답: C
문제3
Service A is an entity service with a functional context dedicated to invoice-related
processing. Service B is a utility service that provides generic data access to a database.
In this service composition architecture, Service Consumer A sends a SOAP message
containing an invoice XML document to Service A(1). Service A then sends the invoice
XML document to Service B (2), which then writes the invoice document to a database.
The data model used by Service Consumer A to represent the invoice document is based
on XML Schema A.
The service contract of Service A is designed to accept invoice documents based on XML Schema B.
The service contract for Service B is designed to accept invoice documents based on XML Schema A.
The database to which Service B needs to write the invoice record only accepts entire business documents in Comma
Separated Value (CSV) format.
Due to the incompatibility of XML schemas used by the services, the sending of the invoice
document from Service Consumer A through to Service B cannot be accomplished using
the services as they currently exist. Assuming that the Contract Centralization and Logic
Centralization patterns are being applied, what steps can be taken to enable the sending of
the invoice document from Service Consumer A to the database without adding logic that
will increase the runtime performance of the service composition?
Service A is an entity service with a functional context dedicated to invoice-related
processing. Service B is a utility service that provides generic data access to a database.
In this service composition architecture, Service Consumer A sends a SOAP message
containing an invoice XML document to Service A(1). Service A then sends the invoice
XML document to Service B (2), which then writes the invoice document to a database.
The data model used by Service Consumer A to represent the invoice document is based
on XML Schema A.
The service contract of Service A is designed to accept invoice documents based on XML Schema B.
The service contract for Service B is designed to accept invoice documents based on XML Schema A.
The database to which Service B needs to write the invoice record only accepts entire business documents in Comma
Separated Value (CSV) format.
Due to the incompatibility of XML schemas used by the services, the sending of the invoice
document from Service Consumer A through to Service B cannot be accomplished using
the services as they currently exist. Assuming that the Contract Centralization and Logic
Centralization patterns are being applied, what steps can be taken to enable the sending of
the invoice document from Service Consumer A to the database without adding logic that
will increase the runtime performance of the service composition?
정답: A
문제4
Service Consumer A sends Service A a message containing a business document (1). The
business document is received by Component A, which keeps the business document in
memory and forwards a copy to Component B (3). Component B first writes portions of the
business document to Database A (4).
Component B writes the entire business document to Database B and then uses some of
the data values from the business document as query parameters to retrieve new data from
Database B (5).
Next, Component B returns the new data back to Component A (6), which merges it
together with the original business document it has been keeping in memory and then
writes the combined data to Database C (7). The Service A service capability invoked by
Service Consumer A requires a synchronous request-response data exchange. Therefore,
based on the outcome of the last database update, Service A returns a message with a
success or failure code back to Service Consumer A (8).
Databases A and B are shared and Database C is dedicated to the Service A service
architecture.
There are several problems with this architecture: First, the response time of Database A is
often poor, resulting in Component B taking too much time to provide a response to
Component A.
This results in Component A consuming too many runtime resources while it
holds the business document in memory and it also causes unreasonable delays in
responding to Service Consumer A.
Additionally, Database B is being replaced with a different database product that supports a proprietary file format. This will disable the
current interaction between Component B and the new Database B.
What steps can be taken to solve these problems?
Service Consumer A sends Service A a message containing a business document (1). The
business document is received by Component A, which keeps the business document in
memory and forwards a copy to Component B (3). Component B first writes portions of the
business document to Database A (4).
Component B writes the entire business document to Database B and then uses some of
the data values from the business document as query parameters to retrieve new data from
Database B (5).
Next, Component B returns the new data back to Component A (6), which merges it
together with the original business document it has been keeping in memory and then
writes the combined data to Database C (7). The Service A service capability invoked by
Service Consumer A requires a synchronous request-response data exchange. Therefore,
based on the outcome of the last database update, Service A returns a message with a
success or failure code back to Service Consumer A (8).
Databases A and B are shared and Database C is dedicated to the Service A service
architecture.
There are several problems with this architecture: First, the response time of Database A is
often poor, resulting in Component B taking too much time to provide a response to
Component A.
This results in Component A consuming too many runtime resources while it
holds the business document in memory and it also causes unreasonable delays in
responding to Service Consumer A.
Additionally, Database B is being replaced with a different database product that supports a proprietary file format. This will disable the
current interaction between Component B and the new Database B.
What steps can be taken to solve these problems?
정답: D