S90-08 practice question 34 of 35

The Reliable Messaging pattern requires:

Full set: 100 questions
Answer options
A: the use of standardized service contracts in order to enable message atomic transaction details to be carried in the message header
B: a framework for temporarily persisting messages and issuing acknowledgements Correct answer
C: the application of the Official Endpoint pattern in order to enable acknowledgement features
D: a framework capable of bridging disparate messaging protocols in order to exchange schemas between compatible services
Correct Answer:
B. a framework for temporarily persisting messages and issuing acknowledgements
Explanation

The Reliable Messaging pattern is designed to guarantee the delivery of messages between services, even in the event of network or component failure. The core mechanism to achieve this guarantee is a framework that temporarily persists (stores) a message after it is sent. The message is only removed from this persistent store after the sender receives a positive acknowledgement from the recipient, confirming successful delivery. If an acknowledgement is not received within a specified time, the framework retransmits the message. This cycle of persistence, transmission, and acknowledgement is fundamental to the pattern's operation.

Why Incorrect

A. This confuses Reliable Messaging with the Atomic Service Transaction pattern. While they can be used together, reliable delivery does not inherently require atomic transaction details in the message.
C. The Official Endpoint pattern standardizes a service's entry point for governance reasons. It is not a prerequisite for implementing the acknowledgement features of reliable messaging.
D. This describes the functionality of a protocol bridging or data format transformation mechanism, which addresses interoperability between different systems, not the guaranteed delivery of a message.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall. In Chapter 15, the "Reliable Messaging" pattern is detailed. The solution section states, "A reliable messaging system is established that can guarantee the delivery of a message... This is generally accomplished by persisting a message until it has been successfully delivered... The receipt of the message is typically confirmed by the destination service via an acknowledgement." (p. 438). This directly supports the requirement for a framework that persists messages and uses acknowledgements.

2. Papazoglou, M. P. (2012). Web Services & SOA: Principles and Technology (2nd ed.). Pearson. Chapter 11, Section 11.3.2 on "Reliable Messaging" explains that standards like WS-ReliableMessaging work by introducing a reliable messaging processor (RMP) that stores messages in persistent storage and manages acknowledgements and retransmissions to ensure delivery. This confirms the need for persistence and acknowledgements.

Scroll to Top