問題1
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?
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
問題2
Service Consumer A sends a message to Service A.
There are currently three duplicate implementations of Service A (Implementation 1, Implementation 2, 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. Also, you are informed that a new service capability will
soon need to be added to Service A that will introduce functionality that will require access
to a shared database that is 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?
Service Consumer A sends a message to Service A.
There are currently three duplicate implementations of Service A (Implementation 1, Implementation 2, 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. Also, you are informed that a new service capability will
soon need to be added to Service A that will introduce functionality that will require access
to a shared database that is 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?
正確答案: B
問題3
It has been confirmed that Policy A and Policy B are, in fact, the same policy and that the
security credential check performed by Service Agent B also needs to be carried out on
messages sent to Service B .
How can this service composition architecture be changed to reduce the redundancy of
policy content and fulfill the new security requirement?
It has been confirmed that Policy A and Policy B are, in fact, the same policy and that the
security credential check performed by Service Agent B also needs to be carried out on
messages sent to Service B .
How can this service composition architecture be changed to reduce the redundancy of
policy content and fulfill the new security requirement?
正確答案: D
問題4
Service A.
Service B.
and Service C are each designed to access the same shared legacy
system. The service contracts for Service A, Service B, and Service C are standardized
and decoupled from the underlying service logic. Service A and Service B are agnostic
services that are frequently reused by different service compositions. Service C is a non-
agnostic task service that requires access to the legacy system in order to retrieve
business rules required for the service to make runtime decisions that determine its service
composition logic. The legacy system uses a proprietary file format that Services A, B, and
C need to convert to and from.
Service A is an agnostic utility service that is used by other services to gain access to the
legacy system. Services B and C were not designed to access the legacy system via
Service A because the Service A service contract was derived from the legacy system API
and is therefore not standardized and exhibits negative contract-to-implementation
coupling. You are told that additional services need to be created, all of which need access
to the legacy system. You are also told that the legacy system may be replaced in the near
future. What steps can be taken to ensure that the replacement of the legacy system has a
minimal impact on Services B and C and any future services that are designed to rely upon
it?
Service A.
Service B.
and Service C are each designed to access the same shared legacy
system. The service contracts for Service A, Service B, and Service C are standardized
and decoupled from the underlying service logic. Service A and Service B are agnostic
services that are frequently reused by different service compositions. Service C is a non-
agnostic task service that requires access to the legacy system in order to retrieve
business rules required for the service to make runtime decisions that determine its service
composition logic. The legacy system uses a proprietary file format that Services A, B, and
C need to convert to and from.
Service A is an agnostic utility service that is used by other services to gain access to the
legacy system. Services B and C were not designed to access the legacy system via
Service A because the Service A service contract was derived from the legacy system API
and is therefore not standardized and exhibits negative contract-to-implementation
coupling. You are told that additional services need to be created, all of which need access
to the legacy system. You are also told that the legacy system may be replaced in the near
future. What steps can be taken to ensure that the replacement of the legacy system has a
minimal impact on Services B and C and any future services that are designed to rely upon
it?
正確答案: B