SOA S90.09 - SOA Design & Architecture Lab Exam
Page: 3 / 8
Total 40 questions
Question #11 (Topic: )
Service A is an entity service that provides a set of generic and reusable service
capabilities. In order to carry out the functionality of any one of its service capabilities,
Service A is required to compose Service B (1) and Service C (2) and Service A is required
to access Database A (3), Database B (4), and Database C (5). These three databases are
shared by other applications within the IT enterprise.
All of service capabilities provided by Service A are synchronous, which means that for
each request a service consumer makes. Service A is required to issue a response
message after all of the processing has completed.
Depending on the nature of the service consumer request, Service A may be required to
hold data it receives in memory until its underlying processing completes. This includes
data it may receive from either Service A or Service B or from any of the three shared
databases.
Service A is one of many entity services that reside in a highly normalized service
inventory. Because Service A provides agnostic logic, it is heavily reused and is currently
part of many service compositions.
[SOA-S90.09-6.1/SOA-S90.09-19_2.png]
You are told that Service A has recently become unstable and unreliable. The problem has
been traced to two issues with the current service architecture. First, Service B, which is
also an entity service, is being increasingly reused and has itself become unstable and
unreliable. When Service B fails, the failure is carried over to Service A . Secondly, shared
Database B has a complex data model. Some of the queries issued by Service A to shared
Database B can take a very long time to complete. What steps can be taken to solve these
problems without compromising the normalization of the service inventory?
capabilities. In order to carry out the functionality of any one of its service capabilities,
Service A is required to compose Service B (1) and Service C (2) and Service A is required
to access Database A (3), Database B (4), and Database C (5). These three databases are
shared by other applications within the IT enterprise.
All of service capabilities provided by Service A are synchronous, which means that for
each request a service consumer makes. Service A is required to issue a response
message after all of the processing has completed.
Depending on the nature of the service consumer request, Service A may be required to
hold data it receives in memory until its underlying processing completes. This includes
data it may receive from either Service A or Service B or from any of the three shared
databases.
Service A is one of many entity services that reside in a highly normalized service
inventory. Because Service A provides agnostic logic, it is heavily reused and is currently
part of many service compositions.
[SOA-S90.09-6.1/SOA-S90.09-19_2.png]
You are told that Service A has recently become unstable and unreliable. The problem has
been traced to two issues with the current service architecture. First, Service B, which is
also an entity service, is being increasingly reused and has itself become unstable and
unreliable. When Service B fails, the failure is carried over to Service A . Secondly, shared
Database B has a complex data model. Some of the queries issued by Service A to shared
Database B can take a very long time to complete. What steps can be taken to solve these
problems without compromising the normalization of the service inventory?
A. The Redundant Implementation pattern can be applied to Service A, thereby making duplicate deployments of the service available. This way, when one implementation of Service A is too busy, another implementation can be accessed by service consumers instead. The Service Data Replication pattern can be applied to establish a dedicated database that contains an exact copy of the data from shared Database B that is required by Service A .
B. The Redundant Implementation pattern can be applied to Service B, thereby making duplicate deployments of the service available. This way, when one implementation of Service B is too busy, another implementation can be accessed by Service A instead. The Service Data Replication pattern can be applied to establish a dedicated database that contains an exact copy of the data from shared Database B that is required by Service A .
C. The Redundant Implementation pattern can be applied to Service B, thereby making duplicate deployments of the service available. This way, when one implementation of Service B is too busy, another implementation can be accessed by Service A instead. The Service Data Replication pattern can be applied to establish a dedicated database that contains a copy of the data from shared Database B that is required by Service A . The replicated database is designed with an optimized data model in order to
D. None of the above.
Answer: C
Question #12 (Topic: )
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).
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).
A. The Data Model Transformation pattern can be applied so that data model transformation logic is positioned between Service A and Service B, between Service C and Service D, and between the Service D logic and Database B. The Data Format Transformation pattern can be applied so that data format transformation logic is positioned between Service A and Service C, and between the Service B logic and Database A.
B. The Data Model Transformation pattern can be applied so that data model transformation logic is positioned between the Service B logic and Database A. The Data Format Transformation pattern can be applied so that data format transformation logic is positioned between Service A and Service B, between Service A and Service C, between Service C and Service D, and between the Service D logic and Database B.
C. The Data Model Transformation pattern can be applied so that data model transformation logic is positioned between Service A and Service B, between Service A and Service C, between Service C and Service D, and between the Service D logic and Database B. The Data Format Transformation pattern can be applied so that data format transformation logic is positioned between the Service B logic and Database A.
D. None of the above.
Answer: C
Question #13 (Topic: )
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.
[SOA-S90.09-6.1/SOA-S90.09-22_2.png]
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?
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.
[SOA-S90.09-6.1/SOA-S90.09-22_2.png]
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. 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 .
B. 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 Se
C. 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 ack
D. None of the above.
Answer: A
Question #14 (Topic: )
Our service inventory contains the following three services that provide invoice-related data
access capabilities: Invoice, InvProc, and Proclnv. These services were created at different
times by different project teams and were not required to comply to any design standards.
Therefore each of these services has a different data model for representing invoice data.
Currently each of these three services has one service consumer: Service Consumer A
accesses the Invoice service(1). Service Consumer B (2) accesses the InvProc service,
and Service Consumer C (3) accesses the Proclnv service. Each service consumer
invokes a data access capability of an invoice-related service, requiring that service to
interact with the shared accounting database that is used by all invoice-related services (4,
5, 6).
Additionally, Service Consumer D was designed to access invoice data from the shared
accounting database directly (7), (Within the context of this architecture. Service Consumer
D is labeled as a service consumer because it is accessing a resource that is related to the
illustrated service architectures.)
[SOA-S90.09-6.1/SOA-S90.09-24_2.png]
Assuming that the Invoice service, InvProc service, and ProcInv service are part of the
same service inventory, what steps would be required to fully apply the Official Endpoint
pattern?
access capabilities: Invoice, InvProc, and Proclnv. These services were created at different
times by different project teams and were not required to comply to any design standards.
Therefore each of these services has a different data model for representing invoice data.
Currently each of these three services has one service consumer: Service Consumer A
accesses the Invoice service(1). Service Consumer B (2) accesses the InvProc service,
and Service Consumer C (3) accesses the Proclnv service. Each service consumer
invokes a data access capability of an invoice-related service, requiring that service to
interact with the shared accounting database that is used by all invoice-related services (4,
5, 6).
Additionally, Service Consumer D was designed to access invoice data from the shared
accounting database directly (7), (Within the context of this architecture. Service Consumer
D is labeled as a service consumer because it is accessing a resource that is related to the
illustrated service architectures.)
[SOA-S90.09-6.1/SOA-S90.09-24_2.png]
Assuming that the Invoice service, InvProc service, and ProcInv service are part of the
same service inventory, what steps would be required to fully apply the Official Endpoint
pattern?
A. One of the invoice-related services needs to be chosen as the official service providing invoice data access capabilities. Service Consumers A, B, and C then need to be redesigned to only access the chosen invoice-related service. Because Service Consumer D does not rely on an invoice-related service, it is not affected by the Official Endpoint pattern and can continue to access the accounting database directly. The Service Abstraction principle can be further applied to hide the existence of th
B. One of the invoice-related services needs to be chosen as the official service providing invoice data access capabilities. Service Consumers A, B, and C then need to be redesigned to only access the chosen invoice-related service. Service Consumer D also needs to be redesigned to not access the shared accounting database directly, but to also perform its data access by interacting with the official invoice-related service. The Service Abstraction principle can be further applied to hide the exis
C. Because Service Consumers A, B, and C are already carrying out their data access via published contracts, they are not affected by the Official Endpoint pattern. Service Consumer D needs to be redesigned to not access the shared accounting database directly, but to perform its data access by interacting with the official invoice-related service. The Service Abstraction principle can be further applied to hide the existence of the shared accounting database and other implementation details from c
D. None of the above.
Answer: B
Question #15 (Topic: )
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 .
[SOA-S90.09-6.1/SOA-S90.09-26_2.png]
How can this service composition architecture be changed to reduce the redundancy of
policy content and fulfill the new security requirement?
security credential check performed by Service Agent B also needs to be carried out on
messages sent to Service B .
[SOA-S90.09-6.1/SOA-S90.09-26_2.png]
How can this service composition architecture be changed to reduce the redundancy of
policy content and fulfill the new security requirement?
A. The Policy Centralization pattern can be applied so that Policy A and Policy B are combined into the same policy. The policy enforcement logic is removed from Service Agent C and Service Agent A is then used to enforce the policy for messages sent to Service A and Service B . Service Agent B can be used to perform the security credential check for Service A and Service B .
B. The Policy Centralization pattern can be applied so that Policy A and Policy B are combined into the same policy. The Service Agent pattern is then applied to introduce a new service agent (called Service Agent D) which carries out the validation and enforcement of Policy A and Policy B. Service Agent B can be moved so that it performs the security credential check for Service B, but not for Service A .
C. The Policy Centralization pattern can be applied so that Service Agent A is changed to enforce the policy for messages sent to Service A and Service B and to perform the security credential check for Service A and Service B .
D. None of the above.
Answer: A
