S90.09 무료 덤프문제 온라인 액세스

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.

How can the application of the Orchestration pattern improve this architecture?

• A.The application of the Orchestration pattern will result in an environment whereby the
  Process Abstraction and Process Centralization patterns are naturally applied to Services
  A, B, and C, resulting in a clean separation of non-agnostic task services from newly
  designed agnostic services with reuse potential. Also, the State Repository pattern can be
  applied by the availability of a central state database that can be shared by Services A and
• B.This database can be made available as a local part of the environment so that Services
  A and B can avoid remote communication.
• C.The application of the Orchestration pattern will result in an environment whereby the
  Compensating Service Transaction is naturally applied, resulting in the opportunity to
  create sophisticated exception logic that can be used to compensate for the performance
  problems caused by Services A and B having to remotely access the state database. The
  Process Abstraction and Service Broker patterns are also naturally applied, enabling the
  separation of non-agnostic logic and agnostic logic while providing common transformation
  functions required to overcome any disparity in the service contracts that will need to be
  created for the new agnostic services.
• D.None of the above.
• E.The application of the Orchestration pattern will result in an environment whereby the
  State Repository and Service Data Replication patterns are naturally applied, allowing the
  shared state database to be replicated for Services A and B so that each task service can
  have its own dedicated state database. The Process Centralization pattern can also be
  applied to Services A and B, so that their logic is physically centralized, turning them into
  orchestrated task services.

Service A has become increasingly difficult to maintain. Its core service logic has become
bloated and convoluted because it has been updated numerous times during which
additional functionality was added to interact with the database and the legacy system and
to support interaction with Service Consumers A and B (via the two service contracts) as
well as interaction directly with Service Consumer C.

What steps can be taken to solve these problems and to prevent them from happening
again in the future?

• A.The Service Facade pattern can be applied to position a Facade component between
  the core service logic and the implementation resources (the database and the legacy
  system) and to also position a Facade component between the two service contracts and
  Service Consumers A and
• B.None of the above.
• C.The Official Endpoint pattern can be applied to limit access to Service A to one of its two
  published service contracts. The Service Loose Coupling principle can be applied so that
  Service Consumer C does not negatively couple itself directly to the core service logic of
  Service A . B.
  The Service Facade pattern can be applied to position a Facade component
  between the core service logic and the implementation resources (the database and the
  legacy system) and to position a faade component between the core service logic and the
  two service contracts. The Contract Centralization pattern can be applied to limit access to
  Service A to one of its two published service contracts. The Service Abstraction principle
  can be applied to hide the implementation details of Service A from service consumers.
• D.The Service Faade pattern can be applied to position a Facade component between the
  core service logic and the two service contracts. The Contract Centralization pattern can be
  applied to limit access to Service A to one of its two published service contracts. The
  Service Loose Coupling principle can be applied so that Service Consumer C does not
  negatively couple itself directly to the core service logic of Service A .

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 despite the fact that duplicate implementations of Service A exist,
performance is still poor at times. Also, you are informed that a new service capability will
soon need to be added to Service A that will introduce functionality that will require access
to a shared database that is used by many other clients and applications in the IT
enterprise. This is expected to add further performance demands on Service A . How can
this service architecture be changed to improve performance in preparation for the addition
of the new service capability?

• A.The Service Autonomy principle is applied to further isolate the individual
  implementations of Service A by separating them onto different physical servers. When the
  new service capability is added, the Service Data Replication pattern is applied to give
  each implementation of Service A its own copy of the data it requires from the shared
  database.
• B.None of the above.
• C.The Service Loose Coupling principle is applied together with the Standardized Service
  Contract principle to ensure that Service Consumer A is not indirectly coupled to the shared
  database after the new service capability is added to the service contract. The Legacy
  Wrapper pattern can be applied to establish a new utility service that will provide
  standardized data access service capabilities for the shared database.
• D.The Standardized Service Contract principle is applied to ensure that the new service
  capability extends the existing service contract in a manner that is compliant with current
  design standards. The Redundant Implementation pattern is applied to establish separate
  implementations of Service A that include duplicate databases with copies of the data that
  Service A requires from the shared database.

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 the 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 pattern
is being applied and that the Logic Centralization is not 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 requirements of
the service composition?

• A.The service composition can be redesigned so that Service Consumer A sends the
  invoice document directly to Service B.
  Because Service Consumer A and Service B use XML Schema A, the need for transformation logic is avoided. This naturally applies the
  Service Loose Coupling principle because Service Consumer A is not required to send the
  invoice document in a format that is compliant with the database used by Service B.
• B.None of the above.
• C.Service Consumer A can be redesigned to use XML Schema B so that the SOAP
  message it sends is compliant with the service contract of Service A . The Data Model
  Transformation pattern can then be applied to transform the SOAP message sent by
  Service A so that it conforms to the XML Schema A used by Service B.
  The Standardized Service Contract principle must then be applied to Service B and Service Consumer A so
  that the invoice XML document is optimized to avoid unnecessary validation.
• D.Service Consumer A can be redesigned to write the invoice document directly to the
  database. This reduces performance requirements by avoiding the involvement of Service
  A and Service B . It further supports the application of the Service Abstraction principle by
  ensuring that Service Consumer A hides the details of the data access logic required to
  write to the database.

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.

You are told that the current service composition architecture is having performance
problems because of two specific reasons. First, too many services need to be explicitly
invoked in order for the message to arrive at its destination. Secondly, because each of the
intermediary services is required to read the entire message contents in order to determine
where to forward the message to, it is taking too long for the overall task to complete. What
steps can be taken to solve these problems without sacrificing any of the functionality that
currently exists?

• A.None of the above.
• B.The Intermediate Routing pattern can be applied together with the Service Agent pattern
  in order to establish a set of service agents capable of intercepting and forwarding the
  message based on pre-defined routing logic. The Service Discoverability principle can be
  applied to improve the communications quality of message contents, which will reduce the
  time required by service agents to read the message contents at runtime.
• C.The Intermediate Routing pattern can be applied together with the Service Agent pattern
  in order to establish a set of service agents capable of intercepting and forwarding the
  message based on pre-defined routing logic. To avoid the need for service agents to read
  the entire message contents, the Messaging Metadata pattern can be applied so that
  content relevant to the routing logic is placed in the header of a message. This way, only
  the message header content needs to be read by the service agents.
• D.The Intermediate Routing pattern can be applied together with the Service Agent pattern
  in order to establish a set of service agents capable of intercepting and forwarding the
  message based on pre-defined routing logic. To avoid the need for service agents to read
  the entire message contents, the Rules Centralization pattern can be applied so that
  content relevant to the routing logic is isolated into a separate Rules service. This way,
  service agents are only required to access the Rules service in order to determine where to
  forward messages to. The Standardized Service Contract principle will need to be applied
  to ensure that the new Rules service and the new service agents provide service contracts
  that are compliant to existing design standards.