S90-18 practice question 7 of 15

Which of the following approaches represents a valid means of utilizing generic security logic?

Full set: 98 questions
Answer options
A: When required, generic security logic can be embedded within a service. The close proximity to the service logic maximizes the chances that the security logic will be consistently executed without interference from attackers.
B: When required, generic security logic can be abstracted into a separate utility service. This allows for reuse.
C: When required, generic security logic can be abstracted into a service agent. This allows for reuse and the security logic can be executed in response to runtime events.
D: All of the above. Correct answer
Correct Answer:
D. All of the above.
Explanation

The question asks for valid methods to utilize generic security logic. All three options represent legitimate, albeit different, architectural approaches within a service-oriented environment.
Option A: Embedding security logic directly within a service is a valid, though often less desirable, approach. It can be suitable for service-specific security rules but hinders reusability.
Option B: Abstracting security logic into a reusable utility service is a fundamental SOA pattern. This centralizes security functions (e.g., authentication, authorization), promoting reuse and consistent application.
Option C: Using a service agent (an event-driven interceptor) is an advanced pattern for applying cross-cutting concerns like security. It allows security policies to be enforced transparently without altering the core service logic. Since all three are recognized implementation patterns, "All of the above" is the correct choice.

Why Incorrect

A, B, C (Individually): These options are not incorrect in themselves, but they are incomplete. Each describes only one of several valid approaches, while the question asks for any valid means.

References

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

For Option C: The Service Agent pattern is described as an event-driven program used for tasks like monitoring and policy enforcement, which directly applies to security logic. (p. 311, Chapter 12).

For Option B: The Utility Abstraction pattern advocates for creating separate, non-business-specific utility services to promote reuse. Security services are a primary example of this pattern. (p. 201, Chapter 9).

2. Erl, T. (2007). SOA Principles of Service Design. Prentice Hall.

For Option B: The principle of Service Reusability emphasizes designing services to be reusable. Abstracting generic security logic into a dedicated service is a direct application of this principle. (Chapter 6, pp. 127-154).

For Option A: The principle of Service Autonomy implies that a service has control over its own execution environment and logic. This includes the security logic embedded within it, making it a valid, self-contained implementation choice, even if it compromises reusability. (Chapter 8, pp. 181-210).

Scroll to Top