The Certified SOA Architect S90.09 exam, delivered by Arcitura Education, validates your ability to design and architect service-oriented solutions using modern SOA principles and microservices patterns. This exam is intended for architects and senior developers who need to demonstrate practical expertise in designing scalable, maintainable service architectures. The SOA Design & Architecture Lab component emphasizes hands-on application of concepts through realistic scenarios. This page guides you through the syllabus, question formats, and proven preparation strategies to help you succeed.
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 a blend of question types to assess both conceptual understanding and practical decision-making in real-world SOA contexts.
Questions increase in complexity, moving from foundational concepts to nuanced architectural decisions that reflect real-world challenges.
A structured study plan aligned to the three core topic areas ensures you build knowledge progressively and retain practical skills. Dedicate time to each domain, then integrate concepts across design, implementation, and operational concerns.
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 for both formats: SOA Design & Architecture Lab.
Advanced SOA Design & Architecture and the SOA Design & Architecture Lab typically account for the majority of exam items. These sections test your ability to make sound architectural decisions under real-world constraints. Foundational SOA concepts are also tested, but the exam emphasizes practical application over theory alone.
In practice, foundational SOA knowledge informs your design choices, advanced patterns help you solve complex integration challenges, and lab skills let you implement and validate those designs. For example, understanding service boundaries (foundational) guides your use of orchestration patterns (advanced), which then shapes how you configure message flows (lab). All three reinforce each other.
Hands-on experience significantly boosts both understanding and confidence. Prioritize labs that involve service decomposition, API design, and message-based communication. If possible, work with a real or simulated microservices platform to design service contracts, configure routing, and troubleshoot integration issues. Even short, focused lab exercises strengthen your ability to answer scenario-based questions.
Candidates often overlook operational concerns such as monitoring, versioning, and deployment complexity when designing services. Another frequent error is choosing overly granular or overly coarse service boundaries without justifying the trade-off. Additionally, confusing orchestration with choreography or misunderstanding when to use synchronous versus asynchronous communication costs points. Always consider the full lifecycle impact of your design choices.
In your final week, focus on weak topic areas identified during practice tests rather than re-reading all material. Run a full-length timed mock exam to validate pacing and identify any remaining knowledge gaps. Review explanations for questions you answered incorrectly, paying special attention to the reasoning behind correct answers. On the day before your exam, do a light review of key definitions and patterns, then rest well.
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?
Service Consumer A invokes Service A (1). The logic within Service A is required to retrieve three independent data values from Services B, C, and D and to then return these data values back to Service Consumer A . To accomplish this, Service A begins by sending a request message to Service B (2). After receiving a response message with the first data value from Service B, Service A sends a request message to Service C (3). After it receives a response message with the second data value from Service C, Service A then sends a request message to Service D (4). Upon receiving a response message with the third data value from Service D . Service A finally sends its own response message (containing all three collected data values) back to Service Consumer A . Service Consumer A and Service A reside in Service Inventory A . Service B and Service C reside in Service Inventory B . Service D is a public service that can be openly accessed via the World Wide Web. The service is also available for purchase so that it can be deployed independently within IT enterprises. Due to the rigorous application of the Service Abstraction principle within Service Inventory B, the only information that is made available about Service B and Service C are the published service contracts. For Service D, the service contract plus a Service Level Agreement (SLA) are made available. The SLA indicates that Service D has a planned outage every night from 11 PM to midnight.
You are an architect with a project team building services for Service Inventory A . You are told that the owners of Service Inventory A and Service Inventory B are not generally cooperative or communicative. Cross-inventory service composition is tolerated, but not directly supported. As a result, no SLAs for Service B and Service C are available and you have no knowledge about how available these services are. Based on the service contracts you can determine that the services in Service Inventory B use different data models and a different transport protocol than the services in Service Inventory A . Furthermore, recent testing results have shown that the performance of Service D is highly unpredictable due to the heavy amount of concurrent access it receives from service consumers from other organizations. You are also told that there is a concern about how long Service Consumer A will need to remain stateful while waiting for a response from Service A . What steps can be taken to solve these problems?
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 Consumer A sends Service A a message containing a business document (1). The business document is received by Component A, which keeps the business document in memory and forwards a copy to Component B (3). Component B first writes portions of the business document to Database A (4). Component B writes the entire business document to Database B and then uses some of the data values from the business document as query parameters to retrieve new data from Database B (5). Next, Component B returns the new data back to Component A (6), which merges it together with the original business document it has been keeping in memory and then writes the combined data to Database C (7). The Service A service capability invoked by Service Consumer A requires a synchronous request-response data exchange. Therefore, based on the outcome of the last database update, Service A returns a message with a success or failure code back to Service Consumer A (8). Databases A and B are shared and Database C is dedicated to the Service A service architecture.
There are several problems with this architecture: First, the response time of Database A is often poor, resulting in Component B taking too much time to provide a response to Component A . This results in Component A consuming too many runtime resources while it holds the business document in memory and it also causes unreasonable delays in responding to Service Consumer A . Additionally, Database B is being replaced with a different database product that supports a proprietary file format. This will disable the current interaction between Component B and the new Database B . What steps can be taken to solve these problems?
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?
