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?

• A. The Rules Centralization pattern can be applied to establish a centralized service that
  contains routing-related business rules. This new Rules service would replace Service B
  and could be accessed by Service A and Service C in order for Service A and Service C to
  determine where to forward a message to at runtime. The Service Composability principle
  can be further applied to ensure that all remaining services are designed as effective
  service composition participants.
• B. The Intermediate Routing pattern can be applied together with the Service Agent pattern
  by removing Service B or Service C from the service composition and replacing it with a
  service agent capable of intercepting and forwarding the message at runtime based on pre-
  defined routing logic. The Service Composability principle can be further applied to ensure
  that all remaining services are designed as effective service composition participants.
• C. The Asynchronous Queuing pattern can be applied together with the Rules
  Centralization pattern to establish a Rules service that encapsulates a messaging queue.
  This new Rules service would replace Service B and could be accessed by Service A and
  Service C in order for Service A and Service C to determine where to forward a message to
  at runtime. The Service Composability principle can be further applied to ensure that all
  remaining services are designed as effective service composition participants.
• D. None of the above.

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. 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.
• B. 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.
• C. 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.
• D. None of the above.

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. The problem has
been traced to two issues with the current service architecture. First, Service B, which is
also an entity service, is being increasingly reused and has itself become unstable and
unreliable. When Service B fails, the failure is carried over to Service A . Secondly, shared
Database B has a complex data model. Some of the queries issued by Service A to shared
Database B can take a very long time to complete. What steps can be taken to solve these
problems without compromising the normalization of the service inventory?

• A. The Redundant Implementation pattern can be applied to Service A, thereby making
  duplicate deployments of the service available. This way, when one implementation of
  Service A is too busy, another implementation can be accessed by service consumers
  instead. The Service Data Replication pattern can be applied to establish a dedicated
  database that contains an exact copy of the data from shared Database B that is required
  by Service A .
• B. None of the above.
• C. The Redundant Implementation pattern can be applied to Service B, thereby making
  duplicate deployments of the service available. This way, when one implementation of
  Service B is too busy, another implementation can be accessed by Service A instead. The
  Service Data Replication pattern can be applied to establish a dedicated database that
  contains a copy of the data from shared Database B that is required by Service A . The
  replicated database is designed with an optimized data model in order to improve query
  execution performance.
• D. The Redundant Implementation pattern can be applied to Service B, thereby making
  duplicate deployments of the service available. This way, when one implementation of
  Service B is too busy, another implementation can be accessed by Service A instead. The
  Service Data Replication pattern can be applied to establish a dedicated database that
  contains an exact copy of the data from shared Database B that is required by Service A .

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. Additionally, a
review of the logic of both services has revealed that some of the business rules used by
the Client and Vendor services are actually the same. What steps can be taken to improve
performance and reduce redundant business rule logic?

• A. The Rules Centralization pattern can be applied to isolate business rules logic into a
  central and reusable Rules service. Additionally, the Service Abstraction principle can be
  applied to hide the implementation details of new the Rules service.
• B. The Rules Centralization pattern can be applied by extracting the business rule logic
  from the Client and Vendor services and placing it into a new Rules service, thereby
  reducing the redundancy of business rules logic. The Redundant Implementation pattern
  can then be applied to establish a scalable Rules service that is capable of supporting
  concurrent access from many service consumers.
• C. The Redundant Implementation pattern can be applied to the Client and Vendor
  services, thereby establishing duplicate service implementations that can be accessed
  when a service reaches its runtime usage threshold. The Intermediate Routing pattern can
  be further applied to provide load balancing logic that can, at runtime, determine which of
  the redundant service implementations is the least busy for a given service consumer
  request.
• D. None of the above.