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?
Answer and explanation
Correct answer: B
This is the optimal solution. Process Abstraction establishes a parent orchestration service to centrally control the flow. A State Repository is essential for persisting the state of the long-running transaction. Compensating Service Transactions are required to ensure the entire process can be reliably reversed if any step fails, which is critical for processes that cannot use atomic transactions.
Question 2
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?
Answer and explanation
Correct answer: A
This option provides the correct classification. Entity services (GetCustomerDetails, UpdateShipmentStatus) encapsulate specific business entities. The Task service (OrchestrateBookingProcess) coordinates other services to execute a business process. Utility services (CalculateShippingRate, ValidateAddressFormat, GenerateInvoicePDF) provide reusable, business-agnostic functions that can support multiple processes.
Question 3
Multiple answers
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)
Answer and explanation
Correct answers: A, B
Question 4
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?
Answer and explanation
Correct answer: B
The core problem is the synchronous coupling between a fast REST service and a slow batch system. Asynchronous Queuing decouples the two, allowing the claims service to post a request and move on immediately, thus resolving the timeout. The Protocol Bridging pattern is then applied by the ESB to handle the translation from the message in the queue (e.g., JSON over JMS) to the required FTP file transfer, bridging the technology gap.
sequenceDiagram
participant C as Claims Service
participant ESB
participant M as Mainframe
Note over C, M: Before (Synchronous Call)
C->>+ESB: ProcessClaim(REST)
ESB->>+M: GenerateFile(FTP)
Note right of M: Takes 5+ minutes
M-->>-ESB: File Ready
ESB-->>-C: Response (Timeout Occurs)
Note over C, M: After (Asynchronous Queuing)
C->>ESB: SendClaim(JMS)
ESB-->>C: Acknowledged
ESB->>M: GenerateFile(FTP)
Note right of M: Takes 5+ minutes
M-->>ESB: File Ready
Question 5
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.
Answer and explanation
Correct answer: A
The fundamental purpose of the Policy Centralization pattern is to externalize policy logic from service implementations. This allows policies (such as security, auditing, or SLA monitoring) to be managed, updated, and applied consistently across multiple services without requiring changes to the services themselves, thus promoting loose coupling and agility.
Question 6
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?
Answer and explanation
Correct answer: C
Cross-Service Data Composition is the correct pattern. It involves designing a composition controller (or the 'Product' service itself) to retrieve data from both the 'Product' and 'Inventory' services at runtime and combine them into a single data structure for the consumer. This avoids replicating inventory data within the 'Product' service's database, thereby ensuring the data is always current.
Question 7
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?
Answer and explanation
Correct answer: A
Service Composability dictates that services should be designed as effective composition members. A large, coarse-grained service that combines multiple distinct business functions (payment, inventory, shipping) cannot be easily reused. For example, a different business process that only needs to check inventory cannot reuse this service without invoking the unwanted payment and shipping logic. Breaking it down into smaller, more granular services (e.g., Payment Service, Inventory Service) would promote composability and reuse.
Question 8
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?
Answer and explanation
Correct answer: A
The State Deferral pattern is specifically designed for this scenario. Before making the unreliable, long-running service call, the orchestration engine persists the current state of the process instance to a database (State Repository). It then makes the call asynchronously. When the response arrives (or a timeout occurs), a separate process retrieves the state and resumes the orchestration. This frees up the engine's active threads, preventing them from being blocked and thereby improving scalability and resilience.
Question 9
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?
Answer and explanation
Correct answer: B
Creating an Entity Service layer is the correct approach. An Entity Service is specifically designed to represent and manage a business entity and its corresponding data. By creating a set of Entity Services (e.g., Customer Service, Product Service) that are the sole gatekeepers to the legacy database, you encapsulate the data access logic. All other services must go through these Entity Services, which enforces loose coupling, standardizes data access, and provides a clear path for future modernization of the data layer.
Question 10
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?
Answer and explanation
Correct answer: C
The Rules Centralization pattern is the ideal solution. It involves externalizing the business rules into a dedicated Business Rules Engine (BRE). The orchestration service would pass the relevant data (like the credit score) to the BRE, which then returns a decision (e.g., 'Instant Approval'). This decouples the process flow from the business logic, allowing business analysts to update the rules in the BRE's repository without changing and redeploying the orchestration service code.
