During a design review for a new enterprise-wide service inventory, an architect proposes a data model that strictly enforces a canonical format for all business entities. Another architect argues this approach will create excessive transformation logic for services that use domain-specific variations of these entities. Which two service-orientation principles are most directly in tension in this scenario? (Select TWO)
Answer and explanation
Correct answers: A, B
The principle of Service Reusability, particularly through the application of a Standardized Service Contract, encourages the use of a canonical data model to ensure consistency and interoperability across the enterprise. However, this can conflict with Service Autonomy, which posits that services should have significant control over their own logic and resources. Forcing a service to conform to a rigid, enterprise-wide model can limit its ability to evolve independently and may require it to contain complex, non-native transformation logic, thus reducing its autonomy.
Question 2
A financial services company is building a loan origination process as a service composition. The process involves a credit check service, an underwriting service, and a funding service. To ensure data consistency, the entire process must be atomic; if the funding service fails, the credit check and underwriting actions must be rolled back. However, the credit check service is a third-party API that does not support two-phase commit (2PC) transactions. Which design pattern is most appropriate for managing this long-running, distributed transaction?
Answer and explanation
Correct answer: B
The Saga pattern is designed to manage data consistency across microservices in distributed transaction scenarios without relying on traditional locking mechanisms like two-phase commit (2PC). It sequences a series of local transactions. If any transaction fails, the saga executes a series of compensating transactions to revert the preceding transactions. This is ideal for the described scenario where a participating service does not support 2PC.
Question 3
An architect is designing a service that retrieves customer profiles. The initial design exposes a rich data model directly from the underlying CRM database. A senior architect flags this as a violation of the Service Abstraction principle, specifically citing that it leaks implementation details. Which meta abstraction type is primarily being violated by exposing the raw database model?
Answer and explanation
Correct answer: B
Technology Abstraction is concerned with hiding the specific technologies used to implement a service. By exposing a data model that directly mirrors the CRM database schema, the service contract is tightly coupled to the underlying database technology (e.g., its table structure, column names, and data types). This violates Technology Abstraction because changes to the CRM database schema would directly impact service consumers.
Question 4
True or False: The application of the Service Discoverability principle is solely concerned with publishing a service's technical endpoint (WSDL or OpenAPI specification) to a central registry.
Answer and explanation
Correct answer: B
This statement is false. Service Discoverability goes beyond simply publishing a technical endpoint. It requires supplementing services with communicative metadata that allows them to be effectively discovered and interpreted. This includes business-level information, quality-of-service details (SLAs), versioning information, and usage policies, not just the technical contract.
Question 5
A logistics company needs to provide a real-time package tracking service to its partners. The underlying system is a legacy mainframe application that processes data in batches every 15 minutes. Direct, real-time queries to the mainframe are not possible. The company wants to expose a modern, stateless REST API for tracking. Which combination of design patterns is the best approach to bridge this gap?
Answer and explanation
Correct answer: C
This is the most comprehensive solution. A Service Agent runs on a schedule (e.g., every 15 minutes) to perform a Data Transfer from the mainframe batch system. The retrieved data is then stored in a cache (State Caching). The modern REST API (a Service Façade) then serves requests by querying this cache, providing a real-time experience to consumers while decoupling them from the legacy system's batch nature.
Question 6
An organization has successfully implemented several autonomous, reusable services. However, business analysts are struggling to create new processes because they don't have a clear, consolidated view of the available business capabilities. The service contracts are highly technical and spread across different repositories. Which design principle has been inadequately applied, leading to this problem?
Answer and explanation
Correct answer: D
The core issue is that business-level stakeholders cannot find and understand the available services. Service Discoverability addresses this by requiring services to be supplemented with communicative metadata. This includes not just technical contracts but also business-centric descriptions, capabilities, and usage policies that enable both technical and non-technical users to effectively find, interpret, and compose services.
Question 7
A sub-controller service capability is distinct from a regular service capability primarily because it is designed to be both a service consumer and a composable part of a larger service composition. It encapsulates a specific, reusable piece of composition logic. Which of the following is the BEST example of a sub-controller's function?
Answer and explanation
Correct answer: D
This is a perfect example of a sub-controller. It encapsulates a specific piece of composition logic (checking internal and external sources) that is reusable within larger processes (like 'New Customer Onboarding' or 'Loan Application'). It consumes other services (internal records, external bureau) and is itself designed to be composed by a parent controller service.
Question 8
A development team is building a set of microservices that will be deployed in containers managed by Kubernetes. To handle cross-cutting concerns like logging, monitoring, and security, the lead architect suggests using a pattern where these functions are implemented in a separate, attached container within the same pod. Which pattern is being described?
Answer and explanation
Correct answer: C
The Sidecar pattern involves deploying components of an application into a separate process or container to provide isolation and encapsulation. In a Kubernetes context, a sidecar is a container that runs alongside the main application container in the same Pod. This is commonly used for cross-cutting concerns like logging, monitoring, security, or as part of a service mesh.
Question 9
A retail company is migrating its monolithic e-commerce platform to a microservices architecture. They need a centralized way to handle requests from various clients (web, mobile, partner APIs), providing routing, authentication, and protocol translation. Different clients may require different data compositions from the backend services. Which architectural pattern should be implemented at the edge of the system to fulfill these requirements?
Answer and explanation
Correct answer: C
An API Gateway is a server that acts as a single entry point into the system. It is responsible for request routing, composition, and protocol translation. It can also handle cross-cutting concerns like authentication, SSL termination, and rate limiting. This pattern is ideal for microservice architectures as it decouples clients from the internal service topology and provides a tailored API for each client type.
Question 10
Case Study:
Company Background: GlobalExpress Logistics (GEL) is a large shipping company with a mix of modern and legacy IT systems. Their core shipment processing is handled by a 20-year-old mainframe system that is reliable but difficult to integrate with. GEL wants to provide a new 'Premium Partner Portal' that allows key corporate clients to integrate their own systems directly with GEL's for creating shipments, getting quotes, and tracking packages.
Current Situation: The mainframe exposes its functionality via a proprietary socket-based protocol and processes requests in a stateful manner, requiring a persistent connection for each partner session. The data formats are based on fixed-width text files. GEL's internal development teams have some experience with REST and SOAP but not with the mainframe's protocol. The business demands that the new partner portal be highly available and scalable, and that new partners can be onboarded within days, not months.
Requirements:
Expose GEL's shipping capabilities via standardized, stateless web services (REST/JSON is preferred).
Decouple the partner-facing services from the mainframe's proprietary protocol and stateful nature.
Ensure the solution does not require any modification to the existing mainframe application code.
Provide a consistent data contract (a canonical model) for all partners, regardless of the mainframe's internal data formats.
Which architectural approach best meets all of GEL's requirements?
Answer and explanation
Correct answer: C
This solution correctly addresses all requirements. The Service Façade provides the standardized REST/JSON interface (Req 1). It decouples partners from the mainframe (Req 2). Protocol Bridging is the specific pattern for translating between the modern HTTP and legacy socket protocols without modifying the mainframe (Req 3). Data Model Transformation handles the conversion to a canonical model (Req 4). This is the most complete and pattern-oriented SOA solution.
