S90-18 practice question 12 of 15

The use of XML-Encryption supports the application of the Service Abstraction principle because the actual message remains hidden from the attacker.

Full set: 98 questions
Answer options
A: True
B: False
Correct Answer:
[FALSE]
Explanation

The statement incorrectly associates the purpose of XML-Encryption with the Service Abstraction principle. The Service Abstraction principle is an architectural design principle focused on hiding the underlying implementation details of a service from its consumers to promote loose coupling. Consumers interact with the service's public contract, not its internal logic. XML-Encryption, conversely, is a security mechanism. Its primary purpose is to ensure data confidentiality by encrypting message content, thereby protecting it from unauthorized parties, such as attackers. While both concepts involve "hiding" information, they do so for different reasons and from different entities. Service Abstraction hides implementation details from legitimate consumers for architectural benefit, whereas XML-Encryption hides message data from unauthorized attackers for security. Therefore, using XML-Encryption supports confidentiality, not the Service Abstraction principle.

Why Incorrect

The "True" option is incorrect because it conflates a security goal (confidentiality from an attacker) with an architectural design principle (abstraction from a consumer). The reason provided in the statement—"because the actual message remains hidden from the attacker"—is the justification for implementing confidentiality, which is a security measure, not a direct application of the Service Abstraction principle.

References

1. Erl, T. (2007). SOA Principles of Service Design. Prentice Hall. In Chapter 6, "Service Abstraction (Principle)," the principle is defined as reducing the information that is published in a service contract to the bare essentials, hiding the underlying implementation logic and technology from the service consumer to achieve loose coupling (pp. 135-137). The context is always the relationship between the service provider and the service consumer, not an attacker.

2. W3C Recommendation. (2013, April 11). XML Encryption Syntax and Processing Version 1.1. In Section 1.1, "Purpose," the specification's goal is explicitly stated as providing a standard for "the process for encrypting data and representing the result in XML" to ensure confidentiality. It is defined as a security mechanism.

3. Erl, T., et al. (2009). SOA Design Patterns. Prentice Hall. The "Data Confidentiality" pattern (p. 210) and "Data Origin Authentication" pattern (p. 214) explicitly categorize mechanisms like XML-Encryption and XML-Signature as security measures to protect the contents and integrity of messages from unauthorized access and tampering. This is treated as a separate concern from the fundamental architectural principles like Service Abstraction.

Scroll to Top