S90-08 practice question 16 of 35

Which of the following is not a common impact of applying the Rules Centralization pattern?

Full set: 100 questions
Answer options
A: Access to a single rules service can create a processing bottleneck.
B: An increase in performance demands due to the need to access and evaluate business rules at runtime.
C: Conflicts when also applying the Decoupled Contract pattern. Correct answer
D: The need to adopt a business rules management product, which can create dependencies on vendor-specific technology.
Correct Answer:
C. Conflicts when also applying the Decoupled Contract pattern.
Explanation

The Rules Centralization pattern focuses on consolidating business rules into a shared, centrally managed service. The Decoupled Contract pattern focuses on separating a service's public contract from its underlying implementation logic. These two patterns are not in conflict; in fact, they are complementary. A centralized rules service would itself expose a service contract, and applying the Decoupled Contract pattern to this service would be a standard best practice to reduce consumer-to-provider coupling. Therefore, creating a conflict with the Decoupled Contract pattern is not a common impact of applying Rules Centralization.

Why Incorrect

A. A centralized rules service acts as a single point of invocation for all consumers, which can lead to contention and become a performance bottleneck under high concurrent access.
B. Instead of executing rules locally, services must make remote calls to the central rules service, which introduces network latency and processing overhead, thereby increasing performance demands.
D. Implementing a sophisticated, centrally managed rules repository often necessitates a specialized Business Rules Management System (BRMS), which can introduce a dependency on a third-party vendor's technology.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall.

Chapter 14: Service Composition Patterns, Section: Rules Centralization: This section details the pattern's application and consequences. It explicitly lists "Performance bottleneck" and "Dependency on business rules management product" as potential impacts (p. 455). It also implicitly supports the performance overhead by describing the remote invocation model. The text does not mention any conflict with the Decoupled Contract pattern.

2. Josuttis, N. (2007). SOA in Practice: The Art of Distributed System Design. O'Reilly Media.

Chapter 6: The Principles of Service Design: This chapter discusses service design principles, including contract decoupling. The principles outlined are generally applicable and complementary to implementation patterns like Rules Centralization, highlighting that separating interface from implementation is a foundational concept that does not inherently conflict with centralizing a specific type of logic.

Scroll to Top