S90-08 practice question 30 of 35
A service fa?ade component can be used to abstract the part of a service architecture that has negative coupling potential.
Full set: 100 questionsThe statement is correct. The primary purpose of the Service Façade design pattern is to introduce an intermediary component that provides a simplified and unified interface to a more complex underlying subsystem. In the context of a service architecture, this subsystem could be a collection of fine-grained services, a legacy system, or any part of the architecture with intricate logic and multiple interaction points. By abstracting this complexity behind a single, coarse-grained service contract, the façade effectively decouples service consumers from the backend implementation. This directly addresses and mitigates negative coupling potential, which arises from consumers being tightly bound to the specific details, protocols, or orchestration logic of the underlying components.
The alternative, "False," would be incorrect because it contradicts the fundamental definition and strategic goal of the Façade design pattern. The pattern is explicitly designed to manage complexity and reduce coupling by creating an abstraction layer. Stating that it cannot be used for this purpose would be a misunderstanding of its role in software and service-oriented architecture.
1. Erl, T. (2009). SOA Design Patterns. Prentice Hall. In Chapter 10, "Service Façade," the pattern is described as a mechanism to "abstract a collection of services and their interactions" (p. 296). The problem statement it solves is that "service consumers are required to interact with a group of services to complete a business task," which introduces undesirable coupling. The solution is to "establish an intermediary service that abstracts the underlying group of services" (p. 297).
2. Arcitura Education Inc. (2017). S90.02: SOA Technology Concepts Guide. In Module 5: SOA Design Principles, the principle of Service Abstraction is detailed. The Service Façade is a direct implementation of this principle, used to hide underlying complexity from the service consumer, thereby reducing the coupling between them.
3. Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley Professional. The Façade pattern is defined as providing "a unified interface to a set of interfaces in a subsystem... [it] promotes weak coupling between the subsystem and its clients" (p. 186). This foundational definition directly supports its use for abstracting parts of an architecture with high (or negative) coupling potential.
Keep practicing
Take the free S90-08 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other S90-08 practice questions
- Question 1Which of the following statements about the application of the Policy Centralization patt…
- Question 2If a service consumer program needs to get data from a service that is not available, it …
- Question 3Because the Service Broker pattern is part of the Enterprise Service Bus pattern, the Sch…
- Question 4Which of the following statements are false?
- Question 5Assuming you have technical service contracts for SOAP-based Web services, you can apply …
- Question 6By applying the Service Broker compound pattern, you establish an environment capable of …
