The Architecture for Service a Displayed in the Figure Shows

question 13

Multiple Choice

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, B, and C is minimized?

• A) The Service Abstraction principle can be applied to hide the implementation details from the core service logic of Service A, thereby shielding this logic from changes to the implementation. In support of this, the Service Facade pattern can be applied to position Facade components between the core service logic and Service Consumers A and B. These Facade components will be designed to regulate the behavior of Service A . The Contract Centralization pattern can be applied to force Service Consumer C to access Service A via one of its existing service contracts.
• B) A third service contract can be added together with the application of the Contract Centralization pattern. This will force Service Consumer C to access Service A via the new service contract. The Service Facade pattern can be applied to position a Facade component between the new service contract and Service Consumer C in order to regulate the behavior of Service A . The Service Abstraction principle can be applied to hide the implementation details of Service A so that no future service consumers are designed to access any of Service A's underlying resources directly.
• C) The Service Facade pattern can be applied to position Facade components between the core service logic and the two service contracts. These Facade components will be designed to regulate the behavior of Service A . The Contract Centralization pattern can also be applied to force Service Consumer C to access Service A via one of its existing service contracts.
• D) None of the above.

---

Definitions:

Financial Statements

Official documentation of a company, individual, or entity's financial transactions and status, usually comprising the income statement, balance sheet, and statement of cash flows.

Internal Accounting Staff

Employees within an organization responsible for overseeing and managing financial records and transactions.

Chief Executive Officer

The highest-ranking executive in a company, responsible for making major corporate decisions, overseeing the overall operations, and acting as the main point of communication between the board of directors and corporate operations.

Generally Accepted Accounting Principles

The standard framework of guidelines for financial accounting used in any given jurisdiction; commonly abbreviated as GAAP.