S90-18 practice question 4 of 15

A service that was previously using a shared identity store is now given its own dedicated identity store instead. What are the likely impacts (positive or negative) that will result from this change?

Full set: 98 questions
Answer options
A: The service's autonomy is increased. Correct answer
B: The operational responsibility is increased due to the need to keep the dedicated identity store in synch with a parent identity store. Correct answer
C: The potential to apply the Service Abstraction principle is increased.
D: The service will no longer be dependent on a certificate authority.
Correct Answer:
A. The service's autonomy is increased.; B. The operational responsibility is increased due to the need to keep the dedicated identity store in synch with a parent identity store.
Explanation

Moving a service from a shared to a dedicated identity store is a significant architectural decision with direct trade-offs. The primary positive impact is an increase in Service Autonomy (A). The service is no longer dependent on a shared resource that could be a point of contention or be governed by policies unsuited to the service's specific needs. It gains exclusive control over its security context. Conversely, this increased autonomy comes at the cost of increased operational responsibility (B). The service's owner is now responsible for the management, maintenance, security, and availability of the dedicated identity store. In many enterprise environments, this also includes the complex task of federating or synchronizing the dedicated store with a central or parent identity store to ensure consistency, which adds to the operational burden.

Why Incorrect

C. The potential to apply the Service Abstraction principle is not directly affected. Abstraction is about hiding implementation details behind a contract, a principle that can be applied regardless of the identity store's architecture.
D. A dedicated identity store does not eliminate the need for a Certificate Authority (CA). CAs are used for issuing digital certificates (e.g., for TLS/SSL), which is a separate security function from identity and access management.

References

1. Erl, T. (2008). SOA: Principles of Service Design. Prentice Hall.

Page 123, Section 6.2, Service Autonomy Principle: The text explains that service autonomy is achieved when a service has a high degree of control over its underlying execution environment. Moving to a dedicated identity store is a direct implementation of this, as the service now controls its own security resource, thus increasing autonomy.

Page 131, Section 6.2, Service Autonomy (Trade-offs and Considerations): This section discusses the trade-offs of increased autonomy, which include "increased design effort and complexity" and "higher maintenance and evolution costs." This directly supports the concept of increased operational responsibility.

2. Papazoglou, M. P. (2012). Web Services & SOA: Principles and Technology (2nd ed.). Pearson.

Chapter 11, Section 11.5.2, Security Management: This section discusses identity management and federation in SOA. It highlights that while federated identity (which often requires synchronization between stores) provides benefits, it introduces "management and administration overhead," corroborating the increased operational responsibility described in option B.

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

Chapter 4, SOA Basics, Autonomy: The author states, "Autonomy means that a service is as independent as possible from other services... This includes its own data, its own logic, and its own platform." A dedicated identity store is a form of "its own data," directly supporting option A. The chapter also implicitly supports option B by discussing the costs and complexities associated with achieving such independence.

Scroll to Top