S90-19 practice question 2 of 15

Because of a new security requirement, all messages received by Service A need to be logged. This requirement needs to be expressed in a policy that is part of Service A's service contract. However, the addition of this policy must not impact existing service consumers that have already formed dependencies on Service A's service contract. How can this be accomplished?

Full set: 83 questions
Answer options
A: The policy can be centralized and isolated into a separate policy document that is linked to the service contract.
B: The policy can be expressed using a digital certificate that is added to the service contract.
C: The policy can be expressed using an ignorable policy assertion that is added to the service contract. Correct answer
D: None of the above.
Correct Answer:
C. The policy can be expressed using an ignorable policy assertion that is added to the service contract.
Explanation

The primary challenge is to update a service contract with a new policy without breaking existing consumer dependencies. An ignorable policy assertion is a standard mechanism within policy frameworks (like WS-Policy) designed for this exact purpose. By marking the new logging policy assertion as "ignorable," the service provider (Service A) signals that consumers who do not understand this assertion can safely ignore it. This ensures that existing consumers continue to function without modification, while new or updated consumers can recognize and potentially adapt to the new policy. The logging itself is a provider-side concern, and the ignorable assertion simply advertises it without mandating consumer compliance.

Why Incorrect

A. Centralizing a policy does not inherently prevent impact. If the linked policy is mandatory, it will still break existing consumers that do not understand or support it.
B. A digital certificate is a security token used for authentication and establishing trust. It is not a mechanism for expressing an operational policy like message logging.
D. This is incorrect because option C provides a valid and standard-based solution to the problem described.

References

1. W3C, "Web Services Policy 1.5 - Framework," W3C Recommendation, 04 September 2007.

Section 4.3.3, Ignorable Assertions: "To facilitate evolution, policy assertions may be marked as ignorable... An ignorable assertion allows consumers to ignore an assertion that they do not understand. This is particularly useful when a new assertion is introduced and deployed in a policy-aware infrastructure. Marking the new assertion as ignorable allows legacy consumers to ignore the new assertion." This directly supports the use of ignorable assertions for backward compatibility.

2. Erl, T., "SOA: Principles of Service Design," Prentice Hall, 2007.

Chapter 6, Service Contracts (Standardization and Design): The text discusses the importance of managing contract evolution. It explains that policies can be designed to be optional or ignorable to allow for "loose coupling between a service contract and its consumers," which prevents breaking changes when policies are added or updated. (Specific discussion on policy evolution and loose coupling can be found in sections related to contract governance).

3. Papazoglou, M. P., "Web Services: Principles and Technology," Pearson Prentice Hall, 2008.

Chapter 10, Advanced Web Services Technologies and Standards: This chapter details WS-Policy and its role in expressing non-functional requirements. It describes how policy assertions can be marked as optional or ignorable to support versioning and prevent tight coupling between service providers and consumers, ensuring that older clients are not impacted by new, non-critical policy additions.

Scroll to Top