SOA Design & Architecture Lab - S90.09 Free Exam Questions

A. The Atomic Service Transaction pattern can be applied to encompass Service A,
Service B and Service Consumer A.
This will guarantee that all of the actions performed by the service composition participants will either be successful or will be rolled back if anyone
is not successful.

B. The Service Data Replication pattern can be applied to Service Consumer A and
Service B so that separate dedicated databases can be established allowing Service
Consumer A to make updates independently of Service B . Service A is simply redesigned
to not write the business document to Database A until after it receives a message
containing a success code from Service B.

C. None of the above.

D. The State Repository pattern can be applied so that Service A writes the business
document data to a separate state database until it receives a response message from
Service B . If the response message contains a success code, Service A writes the
business document to Database A.
If the response contains a failure code, Service A
discards the data that was written to the state database.

A. The Asynchronous Queuing pattern can be applied so that messaging queues are
established between Service A and Service B and between Service Consumer A and
Service A . This way, messages are never lost due to the unavailability of Service A or
Service B.

B. The Event-Driven Messaging pattern can be applied by establishing a subscriber-
publisher relationship between Service Consumer A and Service A . This way, every time
the data value is updated, an event is triggered and Service A, acting as the publisher, can
notify Service Consumer A, which acts as the subscriber. The Asynchronous Queuing
pattern can be applied between Service Consumer A and Service A so that the event
notification message sent out by Service A will be received by Service Consumer A, even
when Service Consumer A is unavailable.

C. None of the above.

D. The Event-Driven Messaging pattern can be applied by establishing a subscriber-
publisher relationship between Service A and Service B . This way, every time the data
value is updated, an event is triggered and Service B, acting as the publisher, can notify
Service A, which acts as the subscriber. The Asynchronous Queuing pattern can be
applied between Service A and Service B so that the event notification message sent out
by Service B will be received by Service A, even when Service A is unavailable.

A. 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.

B. None of the above.

C. This database can be made available as a local part of the environment so that Services
A and B can avoid remote communication.

D. 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.

E. 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

A. The Contract Centralization pattern can be applied so that when the new service
capability is added, the Service A service contract will become the primary contact point for
Service A . This will avoid Service Consumer A or any other potential service consumer
from being designed to access the shared database directly. The Service Abstraction
principle can be applied to further hide the implementation details so that Service
Consumer A and other service consumers are unaware of the fact that the shared
database is being accessed.

B. The Standardized Service Contract principle is applied to ensure that the new service
capability is consistently added to the service contract of each implementation and that it
extends the existing Service A service contract in a manner that is compliant with current
design standards. The Service Loose Coupling principle is applied to ensure that the new
service capability remains decoupled from the underlying logic and implementation so that
Service Consumer A does not become indirectly coupled to any new logic or to the shared
database.

C. The Legacy Wrapper pattern can be applied to establish a new wrapper utility service
that will provide standardized data access service capabilities for the shared database.
This will avoid Service A from having to access the shared database directly and will further
support the application of the Service Loose Coupling principle between Service A and the
new utility service. By abstracting the data access logic into the wrapper service, there is
no need to add the new service capability to each implementation of Service A .

D. None of the above.