The Arcitura Education S90.08B - SOA Design & Architecture Lab with Services & Microservices exam is part of the SOA Certified Professional Gen 2 certification path. It is designed for candidates who want to validate their knowledge of SOA, services, microservices, and architecture design in a practical lab-focused format. This exam matters for professionals who need to demonstrate both conceptual understanding and applied design skills in modern service-based environments. Passing it shows that you are ready to work with advanced SOA and microservices architecture concepts with confidence.
| # | Exam Topics | Sub-Topics | Approximate Weightage (%) |
|---|---|---|---|
| 1 | Fundamental SOA, Services & Microservices | SOA principles, service orientation, microservices basics | 20% |
| 2 | Microservice Technology Concepts | Service decomposition, communication patterns, deployment concepts | 18% |
| 3 | Design & Architecture with SOA, Services & Microservices | Architecture styles, service contracts, integration design, governance basics | 22% |
| 4 | Advanced SOA Design & Architecture with Services & Microservices | Scalability, resilience, composition patterns, advanced design considerations | 20% |
| 5 | SOA Design & Architecture Lab with Services & Microservices | Scenario analysis, applied solution design, lab-based architecture decisions | 20% |
This exam tests how well candidates understand core SOA and microservices concepts and how effectively they can apply that knowledge in design and architecture scenarios. It focuses on practical decision-making, architecture analysis, and the ability to choose suitable service-based solutions for real-world situations. Candidates should be ready for both theory and applied lab-style questions.
QA4Exam.com offers Exam PDF material with actual questions and answers, plus an Online Practice Test designed to help you prepare for the Arcitura Education S90.08B exam efficiently. The practice test gives you a real exam simulation so you can get familiar with the question style and pacing before test day. The PDF and practice test are updated to help you study with current content and verified answers. You can also improve your time management by practicing under exam-like conditions, which is a major advantage for first-attempt success.
With focused preparation and realistic practice, you can build confidence and reduce surprises in the exam room.
It is intended for candidates pursuing the SOA Certified Professional Gen 2 certification path and for professionals who want to validate their knowledge of SOA, services, microservices, and architecture design.
Yes, it can be challenging because it covers both conceptual knowledge and practical design and architecture skills. Preparation should focus on understanding the topics and applying them in scenario-based questions.
Using only braindumps is not a reliable strategy. You should combine dumps with study and practice so you understand the concepts behind the answers and can handle different question styles confidently.
Hands-on experience is very helpful because the exam includes design and lab-oriented topics. Practical exposure makes it easier to understand how SOA and microservices concepts are applied in real situations.
They are very useful for first-attempt preparation because they provide actual questions and answers, verified content, and a realistic practice environment. For best results, use them to reinforce your study and improve exam readiness.
QA4Exam.com provides an Exam PDF with actual questions and answers and an Online Practice Test that simulates the exam experience. Both formats are designed to support efficient study and exam practice.
Yes, the Online Practice Test helps you practice under timed conditions, which improves pacing and time management. This is valuable for building confidence before the real exam.
Refer to Exhibit.

Service A is a task service that is required to carry out a series of updates to a set of databases in order to complete a task. To perform the database updates. Service A must interact with three other services that each provides standardized data access capabilities.
Service A sends its first update request message to Service B (1), which then responds with a message containing either a success or failure code (2). Service A then sends its second update request message to Service C (3), which also responds with a message containing either a success or failure code (4). Finally, Service A sends a request message to Service D (5), which responds with its own message containing either a success or failure code (6).
Services B, C and D are agnostic services that are reused and shared by multiple service consumers. This has caused unacceptable performance degradation for the service consumers of Service A as it is taking too long to complete its overall task. You've been asked to enhance the service composition architecture so that Service A provides consistent and predictable runtime performance. You are furthermore notified that a new type of data will be introduced to all three databases. It is important that this data is exchanged in a standardized manner so that the data model used for the data in inter-service messages is the same.
What steps can be taken to fulfill these requirements?
This approach isolates the services used by Service A, allowing it to avoid the performance degradation caused by multiple service consumers. By creating redundant implementations of Services B, C, and D that are accessed only by Service A, the Composition Autonomy pattern also ensures that Service A's runtime performance is consistent and predictable. Applying the Canonical Schema pattern ensures that the new type of data is exchanged in a standardized manner, ensuring consistent representation of the data model used for the data in inter-service messages.
Refer to Exhibit.

Services A, B, and C are non-agnostic task services. Service A and Service B use the same shared state database to defer their state data at runtime.
An assessment of the three services reveals that each contains some agnostic logic that cannot be made available for reuse because it is bundled together with non-agnostic logic.
The assessment also determines that because Service A, Service B and the shared state database are each located in physically separate environments, the remote communication required for Service A and Service B to interact with the shared state database is causing an unreasonable decrease in runtime performance.
How can the application of the Orchestration pattern improve this architecture?
The application of the Orchestration pattern can improve this architecture by cleanly separating the non-agnostic logic from the agnostic logic, allowing the design of new agnostic services with reuse potential. The State Repository pattern, which is supported by and local to the orchestration environment, provides a central state database that can be shared by Services A and B. The local state database avoids problems with remote communication. Additionally, the Orchestration pattern provides a central controller that can coordinate the interactions between Services A, B, and C, reducing the need for remote communication between services and improving runtime performance.
Refer to Exhibit.

The architecture for Service A displayed in the figure shows how the core logic of Service A has expanded over time to connect to a database and a proprietary legacy system (1), and to support two separate service contracts (2) that are accessed by different service consumers.
The service contracts are fully decoupled from the service logic. The service logic is therefore coupled to the service contracts and to the underlying implementation resources (the database and the legacy system).
Service A currently has three service consumers. Service Consumer A and Service Consumer B access Service A's two service contracts (3, 4). Service Consumer C bypasses the service contracts and accesses the service logic directly (5).
You are told that the database and legacy system that are currently being used by Service A are being replaced with different products. The two service contracts are completely decoupled from the core service logic, but there is still a concern that the introduction of the new products will cause the core service logic to behave differently than before.
What steps can be taken to change the Service A architecture in preparation for the introduction of the new products so that the impact on Service Consumers A and B is minimized? What further step can be taken to avoid consumer-to-implementation coupling with Service Consumer C?
The Service Fagade pattern can be applied to position fagade components between the core service logic and the implementation resources (the database and the legacy system). These fagade components will be designed to insulate the core service logic of Service A from the changes in the underlying implementation resources. This will minimize the impact of the introduction of the new products on Service Consumers A and B since the service contracts are fully decoupled from the core service logic. The Schema Centralization and Endpoint Redirection patterns can also be applied to force Service Consumer C to access Service A via one of its existing service contracts, avoiding direct access to the core service logic and the underlying implementation resources.
Refer to Exhibit.

When Service A receives a message from Service Consumer A (1), the message is processed by Component
Refer to Exhibit.

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 then writes the entire business document to Database B and 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 date* 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. The business document that Component A is required to keep in memory (while it waits for Component B to complete its processing) can be very large. The amount of runtime resources Service A uses to keep this data in memory can decrease the overall performance of all service instances, especially when it is concurrently invoked by multiple service consumers. Additionally, Service A can take a long time to respond back to Service Consumer A because Database A is a shared database that sometimes takes a long time to respond to Component B. Currently, Service Consumer A will wait for up to 30 seconds for a response, after which it will assume the request to Service A has failed and any subsequent response messages from Service A will be rejected.
What steps can be taken to solve these problems?
The problems with the current architecture can be addressed by applying the following patterns:
Service Statelessness principle and State Repository pattern - This pattern allows Component A to defer the business document data to a state database while it waits for a response from Component B. This helps reduce the amount of runtime resources Service A uses to keep the data in memory and improves overall performance.
Service Autonomy principle and Service Data Replication pattern - This pattern allows Component B to access a dedicated replicated database instead of the shared Database A, which can improve response time.
Asynchronous Queuing pattern - This pattern allows Service A to use a message queue to communicate with Service Consumer A asynchronously. This means that Service Consumer A does not need to remain stateful while waiting for a response from Service A, which can improve overall performance and scalability.
Therefore, option B is the correct answer. Option A is incorrect because it suggests using the Compensating Service Transaction pattern to raise awareness of the eventual response rejection, which does not actually solve the problem. Option C is also incorrect because it suggests using multiple patterns, which may not be necessary and can add unnecessary complexity to the architecture.
Full Exam Access, Actual Exam Questions, Validated Answers, Anytime Anywhere, No Download Limits, No Practice Limits
Get All 17 Questions & Answers