Online Access Free S90.09 Exam Questions

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.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.The Standardized Service Contract principle can be applied to the service contract of
  Service A so that it is redesigned to use XML Schema A.
  This would make it capable ofreceiving the invoice document from Service Consumer A and sending the invoice
  document to Service B without the need to further apply the Data Model Transformation pattern.
• C.The Data Model Transformation pattern can be applied so that the invoice document
  sent by Service Consumer A is transformed into an invoice document that is compliant with
  the XML Schema B used by Service A . The Data Model Transformation pattern can be
  applied again to ensure that the invoice document sent by Service A is compliant with XML
  Schema A used by Service B.
• D.None of the above.

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?

• A.The Enterprise Service Bus pattern can be applied to establish an environment whereby
  the Process Abstraction and Process Centralization patterns are naturally applied, resulting
  in a clean separation of non-agnostic task services from newly designed agnostic services
  that are further shaped into reusable services by the application of the Service Reusability
  principle.
• B.The Process Centralization pattern can be applied, resulting in a redesign effort where
  agnostic logic is removed from the three task services so that they only encapsulate non-
  agnostic logic. The agnostic logic is then moved to one or more new agnostic services that
  are shaped into reusable services by the application of the Service Reusability principle.
  The Process Abstraction pattern is then applied to the redesigned task services Service A
  and Service B, so that their logic is physically centralized, turning them into orchestrated
  task services.
• C.The Process Abstraction pattern can be applied, resulting in a redesign effort where
  agnostic logic is removed from the three task services so that they only encapsulate non-
  agnostic logic. The agnostic logic is then moved to one or more new agnostic services that
  are shaped into reusable services by the application of the Service Reusability principle.
  The Orchestration pattern can be further applied to establish an environment whereby the
  Process Centralization pattern is naturally applied to Services A and B and the State
  Repository pattern in naturally applied to further help avoid remote communication by
  providing a local and centralized state database that can be shared by both services.
• D.None of the above.

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

Service A is a utility service that provides generic data access logic to a database that
contains 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.
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 operations in the WSDL definition that expresses the service contract. How
can the Service A architecture be changed to enforce these security restrictions while
avoiding negative forms of coupling?

• A.The Concurrent Contracts pattern can be applied to Service A in order to establish one
  or more alternative service contracts. This allows service consumers with different levels of
  security clearance to continue accessing the service logic via its published service
  contracts.
• B.The Contract Centralization pattern can be applied to force all service consumers to
  access the Service A architecture via its published service contract. This will prevent
  negative forms of coupling that could lead to problems when the database is replaced. The
  Service Abstraction principle can then be applied to hide underlying service architecture
  details so that future service consumers cannot be designed to access any part of the
  underlying service implementation.
• C.The Contract Centralization pattern can be applied to force service consumers to access
  the Service A architecture via its published service contract only. The Service Loose
  Coupling principle can then be applied to ensure that the centralized service contract does
  not contain any content that is dependent on or derived from the underlying service
  implementation.
• D.None of the above.

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?

• A.The State Repository pattern is applied so that Component A can defer the business
  document data to a state database while it waits for a response from Component B.
  The Service Data Replication pattern is applied so that Component B can interact with a
  database that is replicated from the shared Database A.
  This will improve performance and reliability that will affect both Component A and Service Consumer A.
  Finally, the Legacy Wrapper pattern is applied so that Database B is wrapped in a standardized contract. This
  will establish a new wrapper utility service that will allow Database B to be replaced with a
  different database product without affecting Service A . Furthermore, the Data Format
  Transformation pattern can be applied within the new wrapper utility service to enable it to
  convert to and from the new proprietary file format.
• B.The Legacy Wrapper pattern is applied so that Database B is wrapped in a standardized
  contract. This will establish a new wrapper utility service that will allow Database B to be
  replaced with a different database product without affecting Service A . The Data Format
  Transformation pattern can be applied within the new wrapper utility service to enable it to
  convert to and from the new proprietary file format. The Service Data Replication pattern is
  applied so that Component B can interact with a database that is replicated from the
  shared Database B, regardless of what database product is used to replace Database B.
  The Service Abstraction principle can be further applied to hide the implementation details,
  including the changes mentioned in this solution, from Service Consumer A.
• C.The State Repository pattern is applied so that Component A can defer the business
  document data to a state database while it waits for a response from Component B.
  The Asynchronous Queuing pattern can be applied so that a messaging queue is established
  between Service Consumer A and Service A, thereby guaranteeing delivery and avoiding
  Service Consumer A from being tied up too long waiting for Service A to respond. Finally,
  the Data Format Transformation pattern can be applied to enable Component B to convert
  to and from the new proprietary file format introduced by the database product that is
  replacing Database B.
• D.None of the above.