S90-08A Free Sample Questions

A healthcare provider is architecting a new patient onboarding process that involves multiple, long-running activities: identity verification via an external service, an insurance eligibility check with a partner system, and internal patient record creation. The entire process can take several hours to complete, and its state must be maintained reliably. Which combination of patterns provides the most suitable solution for managing the long-running, stateful nature of this business activity while maintaining central control over the process flow?

**Company Background:** GlobalLogistics Inc. is modernizing its legacy shipping platform using SOA principles. Their primary goal is to establish a highly reusable service inventory that can be consumed by various front-end applications and external partners. **Current Situation:** The existing system is a large monolith where components for quoting, booking, tracking, and invoicing shipments are tightly coupled. Business logic is frequently duplicated across different modules, making maintenance difficult and hindering the rapid development of new features. **Architectural Requirements:** The new architecture must support diverse consumer types, including a public web portal, a mobile application for drivers, and API integrations for corporate partners. Key requirements include enforcing a clear separation of concerns, maximizing the reuse of business logic and data, and isolating core business entities from process-specific logic. The architects have mandated the use of a layered service architecture. **Identified Services:** - `GetCustomerDetails` - `UpdateShipmentStatus` - `CalculateShippingRate` - `OrchestrateBookingProcess` - `ValidateAddressFormat` - `GenerateInvoicePDF` As the lead architect, you must classify these services into the correct service layers. Which option correctly categorizes the proposed services into Entity, Task, and Utility layers to meet the design goals?

A financial services company is implementing a cross-border money transfer process. The process involves three distinct, autonomous services: `DebitSourceAccount`, `PerformCurrencyConversion`, and `CreditDestinationAccount`. The entire operation must be treated as a single logical unit of work. However, because it involves services that could be owned by different entities and may experience delays, a traditional two-phase commit (2PC) atomic transaction is not feasible. The architect has decided to use the Compensating Service Transaction pattern. Which TWO actions are essential for the successful implementation of the Compensating Service Transaction pattern in this scenario? (Select TWO)

An insurance company is integrating its modern, REST-based claims processing service with a legacy mainframe system that only communicates via fixed-width text files over FTP. The integration point is an Enterprise Service Bus (ESB). The initial design simply wraps the FTP transfer in a synchronous service call. During testing, the claims service frequently times out because the mainframe batch process takes over five minutes to generate and place the file on the FTP server. What combination of patterns should an architect introduce into the ESB to resolve the timeout issue and create a more robust, decoupled integration?

True or False: Applying the Policy Centralization pattern requires that all business logic related to policy enforcement be removed from individual service implementations and managed by a dedicated policy enforcement agent or service.

An architect is designing a service inventory for an e-commerce platform. A key non-functional requirement is to minimize data replication between services to ensure strong consistency. The 'Product' and 'Inventory' services are separate, but the 'Product' service needs to display real-time stock levels. Which design pattern directly addresses this requirement by avoiding data replication and ensuring the 'Product' service always has the most current inventory data?

While reviewing a proposed service-oriented architecture, you notice that a single, large 'Order Management' service is responsible for validating orders, processing payments, checking inventory, and arranging shipping. This design violates the 'Service Composability' principle. What is the primary negative consequence of this design flaw?

A development team is building an orchestration that involves calling a partner's web service. The partner service is known to be unreliable and sometimes takes an excessively long time to respond, causing threads in the orchestration engine to be blocked. To improve the resilience and scalability of the orchestration, the architect wants to prevent the engine's threads from being consumed by these unreliable calls. Which pattern should be applied?

A retail company is migrating from a monolithic application to a service-oriented architecture. They have a large, complex legacy database that is accessed by many parts of the old application. The architects want to avoid having multiple new services directly access this shared database, as it would create tight coupling and contention. Which pattern provides a standardized way to encapsulate access to this legacy data source?

During the design of a service composition, an architect needs to decide where to place complex business rules that determine which services to invoke based on the content of an incoming message. For example, if a loan application has a credit score above 750, it should be routed to the 'Instant Approval' service; otherwise, it should go to the 'Manual Review' service. To maximize agility and allow business analysts to modify these rules without requiring developer intervention, which pattern should be applied in conjunction with an orchestration?