Refer to Exhibit. 
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 that are based on different design standards and technologies than the services In Service Inventory B. As a result, Service A is a SOAP-based Web service and Service B Is a REST service that exchanges JSON- formatted messages. 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. What steps can be taken to solve these problems?
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 primarily provides data access logic to a client database but also coordinates with
other services to determine a clients credit rating. The Vendor service provides some data access
logic but can also generate various dynamic reports based on specialized business requirements.
After reviewing historical statistics about the runtime activity of the two services, it is discovered that
the Client service is serving an ever-increasing number of service consumers. It is regularly timing
out, which in turn increases its call rate as service consumers retry their requests. The Vendor service
occasionally has difficulty meeting its service-level agreement (SLA) and when this occurs, penalties
are assessed.
Recently, the custodian of the Client service was notified that the Client service will be made
available to new service consumers external to its service inventory. The Client service will be
providing free credit rating scores to any service consumer that connects to the service via the
Internet. The Vendor service will remain internal to the service inventory and will not be exposed to
external access.
Which of the following statements describes a solution that addresses these issues and
requirements?Refer to Exhibit. 
Service A is a SOAP-based Web service with a functional context dedicated to invoice-related processing. Service B is a REST-based 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 (3). 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 a proprietary 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 pattern 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?
Refer to Exhibit. 
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 text 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?
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 that each provides standardized data access capabilities.
Service A sends its first update request message to Service B (1), which then responds with a
message containing either 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 either a success or
failure code (4). Finally, Service A sends a request message to Service D (5), which responds with its
own message containing either a success or failure code (6).
Services B, C and D are agnostic services that are reused and shared by multiple service consumers.
This has caused unacceptable performance degradation for the service consumers of Service A as it is
taking too long to complete its overall task. You've been asked to enhance the service composition
architecture so that Service A provides consistent and predictable runtime performance. You are
furthermore notified that a new type of data will be introduced to all three databases. It is important
that this data is exchanged in a standardized manner so that the data model used for the data in
inter-service messages is the same.
What steps can be taken to fulfill these requirements?Refer to Exhibit. 
Service A sends a message to Service B (1). After Service B writes the message contents to Database A (2), it issues a response message back to Service A (3). Service A then sends a message to Service C (4). Upon receiving this message, Service C sends a message to Service D (5), which then writes the message contents to Database B (6) and issues a response message back to Service C (7). Service A and Service D are located in Service Inventory A. Service B and Service C are located in Service Inventory B. You are told that In this service composition architecture, all four services are exchanging invoice- related data in an XML format. However, the services in Service Inventory A are standardized to use a different XML schema for invoice data than the services in Service Inventory B. Also, Database A can only accept data in the Comma Separated Value (CSV) format and therefore cannot accept XML- formatted data. Database B only accepts XML-formatted data. However, it is a legacy database that uses a proprietary XML schema to represent invoice data that is different from the XML schema used by services in Service Inventory A or Service Inventory B. What steps can be taken to enable the planned data exchange between these four services?
Service A is a utility service that provides generic data access logic to a database containing data that
is periodically replicated from a shared database (1). Because the Standardized Service Contract
principle was applied to the design of Service A, its service contract has been fully standardized.
The service architecture of Service A Is being accessed by three service consumers. Service Consumer
A accesses a component that is part of the Service A Implementation by Invoking it directly (2).
Service Consumer B invokes Service A by accessing Its service contract (3). Service Consumer C
directly accesses the replicated database that Is part of the Service A Implementation (4).
You've been told that the reason Service Consumers A and C bypass the published Service A service
contract is because, for security reasons, they are not allowed to access a subset of the capabilities in
the API that comprises the Service A service contract. How can the Service A architecture be changed
to enforce these security restrictions while avoiding negative forms of coupling?
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). However, Services A, B and C each contain logic that reads the contents of the message to
determine what intermediate processing to perform and which service to forward the message to.
As a result, what is shown in the diagram is only 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 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?Refer to Exhibit. 
Service Consumer A sends a message to Service A. There are currently three duplicate implementations of Service A (Implementation 1, Implementation 2 and 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. You are also informed that a new service capability will soon need to be added to Service A to introduce functionality that will require access to a shared database being 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?
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 the three services reveals that each contains some agnostic logic that cannot be
made available for reuse because it is bundled together with non-agnostic logic.
The assessment also determines that because Service A, 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?