S90.09 試験問題を無料オンラインアクセス

You are an architect with a project team building services for Service Inventory A . You are
told that no SLAs for Service B and Service C are available. You cannot determine how
available these services will be, but it has been confirmed that both of these services
support atomic transactions and the issuance of positive and negative acknowledgements.
However, you also find out that the services in Service Inventory B use different data
models than the services in Service Inventory A.
Furthermore, recent testing results have shown that the performance of Service D is steady and reliable. However, Service D uses a
different transport protocol than the services in Service Inventory A.
The response time of Service A is not a primary concern, but Service Consumer A does need to be able to issue
request messages to Service A 24 hours a day without disruption. What steps can be taken
to fulfill these requirements?

• A.None of the above.
• B.The Asynchronous Queuing pattern is applied so that a central messaging queue is
  positioned between Service A and Service B and between Service A and Service C and
  between Service A and Service D and so that a separate messaging queue is positioned
  between Service A and Service Consumer A.
  The Data Model Transformation pattern is
  applied to enable communication between Service A and Service B and between Service A
  and Service C . The Protocol Bridging pattern is applied to enable communication between
  Service A and Service D .
• C.The Event-Driven Messaging pattern is applied so that a subscriber-publisher
  relationship is established between Service Consumer A and Service A . This gives Service
  A the flexibility to provide its response to Service Consumer A whenever it is able to collect
  the three data values without having to require that Service Consumer A remain stateful.
  The Asynchronous Queuing pattern is applied so that a central messaging queue is
  positioned between Service A and Service B and between Service A and Service C . The
  Data Model Transformation and Protocol Bridging patterns are applied to enable
  communication between Service A and Service B and between Service A and Service C .
  The Service Autonomy principle is further applied to Service A in order to improve its
  overall runtime behavioral predictability.
• D.The Reliable Messaging pattern is applied so that a system of acknowledgements is
  established between Service Consumer A and Service A . This gives Service A the
  flexibility to provide Service Consumer A with acknowledgements that indicate that the
  processing steps that are occurring between Service A and Service B, Service C, and
  Service D are progressing. The Asynchronous Queuing pattern is applied so that a central
  messaging queue is positioned between Service A and Service B and between Service A
  and Service C and between Service A and Service D . The Redundant Implementation
  pattern is applied so that a copy of Service D is brought in-Upon reviewing these
  requirements it becomes D with a standardized service contract that is in compliance with
  the design standards used in Service Inventory 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.None of the above.
• 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.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.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 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.None of the above.
• B.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.
• 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.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.

Service Consumer A sends a message with a business document to Service A (1), which
writes the business document to Database A (2). Service A then forwards the business
document to Service B (3), which writes the business document to Database B (4).
Service B then responds to Service A with a message containing a failure or success code
(5) after which Service A responds to Service Consumer A with a message containing a
failure or success code (6). Upon receiving the message, Service Consumer A updates a
log table in Database B (7). The log entry is comprised of the entire business document.
Database A is dedicated to the Service A service architecture and Database B is a shared
database.

There are two problems with this service composition architecture that you are asked to
address: First, both Service Consumer A and Service B need to transform the business
document data from an XML format to a proprietary Comma Separated Value (CSV) in
order to write the data to Database B.
This has led to redundant data format transformation logic that has been difficult to keep in synch when Database B changes. Secondly, Service
A is an entity service that is being reused by several other service compositions. It has
lately developed reliability problems that have caused the service to become unavailable
for extended periods. What steps can be taken to solve these problems?

• A.None of the above.
• B.The service composition can be redesigned with the application of the Contract
  Centralization pattern so that instead of writing the business document to Database B,
  Service Consumer A sends the business document to Service B instead. This way, Service
  B would provide the only location where data format transformation logic for Database B
  needs to be carried out, which further supports the application of the Service Reusability
  principle. The Reliable Messaging pattern can be applied so that acknowledgements are
  passed between Service Consumer A and Service A and between Service A and Service B
  . The Service Composability principle can be further applied to Service A in order to
  optimize its service architecture for improved participation in multiple service compositions.
• C.The Legacy Wrapper pattern can be applied so that data access to Database B is
  separated into a new wrapper utility service. This way, the Data Format Transformation
  pattern only needs to be applied within the logic of this new service which will expose a
  standardized contract that both Service Consumer A and Service B can access. The
  Asynchronous Queuing pattern can be applied so that messaging queues are established
  between Service Consumer A and Service A and between Service A and Service B . The
  Service Autonomy principle can be further applied to Service A in order to establish a more
  isolated and reliable surrounding infrastructure.
• D.The Legacy Wrapper pattern can be applied so that data access to Database B is
  separated into a new wrapper utility service. This way, the Data Format Transformation
  pattern only needs to be applied within the logic of this new service which will expose a
  standardized contract that both Service Consumer A and Service B can access. The
  Reliable Messaging pattern can be applied so that acknowledgements are passed between
  Service Consumer A and Service A and between Service A and Service B . The Service
  Composability principle can be further applied to Service A in order to optimize its service
  architecture for improved participation in multiple service compositions.

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