SOA S90.09 valid exam dumps : SOA Design & Architecture Lab

Demo first, download instantly, update free for a year, refund in writing if the conditions are met: ValidDumps covers the full SOA Design & Architecture Lab journey in one stop. For 2026 S90.09 candidates, the logistics are already solved.

SOA S90.09 Exam Overview:

Certification Vendor:	Arcitura Education
Exam Name:	SOA Design & Architecture Lab
Exam Number:	S90.09 (also S90.09A)
Related Certifications:	Certified SOA Security Specialist Certified Microservices Architect Certified SOA Consultant
Passing Score:	70% or 700/1000
Exam Price:	$295 USD
Exam Duration:	90–100
Available Languages:	English
Exam Format:	Drag-and-drop, Lab exercises, Case studies, Design tasks, Scenario-based
Certificate Validity Period:	3 years
Real Exam Qty:	40–70
Recommended Training:	SOACP Module 9 Study Kit SOA School Official Training
Exam Registration:	Pearson VUE Scheduling Arcitura Official Exam Registration
Sample Questions:
Exam Way:	Online proctored or onsite at Pearson VUE testing centers
Pre Condition:	Recommended: S90.01, S90.02, S90.03, S90.04, S90.05, S90.08 or equivalent knowledge; strong practical experience in SOA design
Official Syllabus URL:	https://www.arcitura.com/soacp-gen-1/exams/

SOA S90.09 Exam Syllabus Topics:

Questions Candidates Ask About SOA Design & Architecture Lab

SOA Design & Architecture Lab Sample Questions:

Question 1

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

Question 2

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

Question 3

Service A has become increasingly difficult to maintain. Its core service logic has become
bloated and convoluted because it has been updated numerous times during which
additional functionality was added to interact with the database and the legacy system and
to support interaction with Service Consumers A and B (via the two service contracts) as
well as interaction directly with Service Consumer C.

What steps can be taken to solve these problems and to prevent them from happening
again in the future?

A. None of the above.
B. The Service Facade pattern can be applied to position a Facade component between
the core service logic and the implementation resources (the database and the legacy
system) and to also position a Facade component between the two service contracts and
Service Consumers A and
C. The Service Faade pattern can be applied to position a Facade component between the
core service logic and the two service contracts. The Contract Centralization pattern can be
applied to limit access to Service A to one of its two published service contracts. The
Service Loose Coupling principle can be applied so that Service Consumer C does not
negatively couple itself directly to the core service logic of Service A .
D. The Official Endpoint pattern can be applied to limit access to Service A to one of its two
published service contracts. The Service Loose Coupling principle can be applied so that
Service Consumer C does not negatively couple itself directly to the core service logic of
Service A . B.
The Service Facade pattern can be applied to position a Facade component
between the core service logic and the implementation resources (the database and the
legacy system) and to position a faade component between the core service logic and the
two service contracts. The Contract Centralization pattern can be applied to limit access to
Service A to one of its two published service contracts. The Service Abstraction principle
can be applied to hide the implementation details of Service A from service consumers.

Question 4

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

Solutions: