The S90.09 exam, SOA Design & Architecture Lab, validates your ability to design and architect service-oriented solutions using modern patterns and practices. This exam is intended for professionals pursuing the Certified SOA Architect credential who need to demonstrate hands-on competency in applying SOA principles to real-world scenarios. Arcitura Education's SOA Design & Architecture Lab focuses on translating design theory into practical implementation decisions. This page provides a clear study roadmap, question formats, and resources to help you prepare efficiently and confidently.
Use this topic map to guide your study for Arcitura Education S90.09 (SOA Design & Architecture Lab) within the Certified SOA Architect path.
The S90.09 exam uses multiple-choice and scenario-based items to assess both conceptual knowledge and practical decision-making ability in SOA and microservices contexts.
Questions increase in complexity, moving from foundational concepts to nuanced architectural decisions that reflect actual enterprise projects.
An effective study plan maps the three core topic areas to weekly milestones, ensures you practice with realistic questions, and builds confidence through timed exercises. Dedicate time to understanding both the "what" (concepts) and the "why" (business and technical justifications).
Explore other Arcitura Education certifications: view all Arcitura Education exams.
Strengthen your preparation with up-to-date resources from validexamdumps.com. These materials align to S90.09 and cover practical scenarios with clear explanations.
Visit the exam page to download the PDF, Online Practice Test, or get a Bundle Discount offer for both formats: SOA Design & Architecture Lab.
Advanced SOA Design & Architecture with Services & Microservices typically represents the largest portion of the exam, as it tests your ability to make nuanced architectural decisions. The practical lab scenarios also carry significant weight because they require you to apply concepts in realistic contexts. Foundational knowledge is important but is often tested indirectly through scenario-based questions.
In practice, foundational concepts inform your initial service decomposition strategy, advanced design patterns help you handle complex interactions and scalability, and lab-style decision-making mirrors the trade-offs you face during actual architecture reviews. For example, you might start by identifying services (foundational), then apply patterns like API gateways and event sourcing (advanced), and finally decide on versioning and resilience strategies (lab-based). Understanding these connections helps you see the exam as a coherent journey rather than isolated topics.
Direct experience designing or refactoring services is valuable but not required; the exam tests architectural reasoning more than tool-specific skills. Prioritize labs that involve service decomposition, API design, and handling cross-cutting concerns like security and logging. If you lack real-world exposure, focus on understanding the "why" behind each decision, why you'd choose REST over messaging, or when to split a service, rather than memorizing syntax.
Candidates often overlook the business context in scenario questions, focusing only on technical elegance rather than cost, timeline, and organizational constraints. Another frequent error is confusing SOA principles with microservices architecture; while related, they have different trade-offs. Finally, many rush through lab-style questions without fully analyzing the given constraints, leading to suboptimal architectural recommendations.
In your final week, take one full-length timed practice test early to identify your weakest topics, then spend 2-3 days drilling those areas with focused question sets. Avoid trying to learn new topics; instead, review your notes on advanced patterns and common decision frameworks. On the day before the exam, do a light review of key definitions and take a short, untimed practice quiz to build confidence without mental fatigue.
Service A is a task service that sends Service B a message (2) requesting that Service B return data back to Service A in a response message (3). Depending on the response received. Service A may be required to send a message to Service C (4) for which it requires no response. Before it contacts Service B, Service A must first retrieve a list of code values from its own database (1) and then place this data into its own memory. If it turns out that it must send a message to Service C, then Service A must combine the data it receives from Service B with the data from the code value list in order to create the message it sends to Service C . If Service A is not required to invoke Service C, it can complete its task by discarding the code values. Service A and Service C reside in Service Inventory A . Service B resides in Service Inventory B . You are told that the services in Service Inventory A were designed with service contracts based on different design standards than the services in Service Inventory B . As a result, Service A and Service B use different data models to represent the data they need to exchange. Therefore, Service A and Service B cannot currently communicate. Furthermore, Service C is an agnostic service that is heavily accessed by many concurrent service consumers. Service C frequently reaches its usage thresholds during which it is not available and messages sent to it are not received. How can this service composition architecture be changed to avoid these problems?
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?
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.
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?
Service Consumer A sends a message to Service A . Before the message arrives with Service A, it is intercepted by Service Agent A (1). which checks the message for compliance to Policy A that is required by Service A . If the message fails compliance, Service Agent A will not allow it to proceed and will instead write the message contents to a log. If the message does comply to the policy, it continues to be transmitted toward Service A, but before it arrives it is intercepted by Service Agent B (2), which validates the security credentials in the message header. If the security credential validation fails, the message is rejected and a runtime exception is raised. If the security credentials are validated, the message is sent to Service A . Upon receiving the message, Service A retrieves a data value from a database and populates the message header with this data value (3) prior to forwarding the message to Service B . Before the message arrives at Service B . it is intercepted by Service Agent C (4) which checks the message for compliance with two policies: Policy B and Policy C . Policy B is identical to Policy A that was checked by Service Agent A . To check for compliance to Policy C . Service Agent C uses the data value added by Service A . If the message complies with both of the policies, it is forwarded to Service B (5), which stores the message contents in its own database.
You are told that Policy B and Policy C have changed. Also, in order to carry out the compliance check of Policy C, Service Agent C will now require a new data value from the Service B database. How can this service composition architecture be changed to fulfill these new requirements?
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.)
A project team recently proclaimed that it has successfully applied the Contract Centralization pattern to the service inventory in which the Invoice service, InvProc service, and ProcInv service reside. Upon reviewing the previously described architecture you have doubts that this is true. After voicing your doubts to a manager, you are asked to provide specific evidence as to why the Contract Centralization is not currently fully applied. Which of the following statements provides this evidence?
