S90-08 practice question 31 of 35

In the message exchange framework established by the application of the Reliable Messaging pattern, what roles are typically fulfilled by service agents?

Full set: 100 questions
Answer options
A: service agents can process positive acknowledgements Correct answer
B: service agents can process negative acknowledgements Correct answer
C: service agents can load balance messages
D: service agents can route messages based on their content
Correct Answer:
A. service agents can process positive acknowledgements; B. service agents can process negative acknowledgements
Explanation

The Reliable Messaging pattern introduces an intermediary, typically a service agent, to guarantee message delivery between a service consumer and provider. This agent's primary responsibility is to manage the message lifecycle until successful delivery is confirmed. To do this, it must process acknowledgements. It processes positive acknowledgements (ACKs) to confirm a message was successfully received, at which point it can cease retry attempts. It also processes negative acknowledgements (NACKs) or handles timeouts to recognize delivery failures, trigger retry logic, or escalate the failure as required.

Why Incorrect

C. service agents can load balance messages This describes the primary function of the Service Broker or Load Balancer patterns, which focus on distributing workloads, not guaranteeing message delivery.
D. service agents can route messages based on their content This is the specific purpose of the Content-Based Router pattern, which directs messages to different endpoints based on their content, a separate concern from reliability.

References

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

Chapter 15, Reliable Messaging Pattern: The pattern description explicitly details the role of a reliable messaging agent. The solution section states, "The reliable messaging system is responsible for persisting messages it receives and continuing to attempt delivery of a message until it receives an acknowledgement from the service that the message was successfully received." This confirms the processing of positive acknowledgements (A). The pattern's logic for handling delivery failures and retries inherently involves processing negative acknowledgements or timeout events (B).

Chapter 15, Content-Based Router Pattern: This pattern is presented separately and is dedicated to the problem described in option D.

Chapter 15, Service Broker Pattern: This pattern addresses logic for message distribution and load balancing, as described in option C.

Scroll to Top