1Z0-478 · Question #41
View the Exhibit. A user has configured Mediator M1 to receive and route product Information from System X into its internal applications in chronological order. For each product1 M1 receives one…
The correct answer is C. The given Mediator configuration does not address this sequencing requirement. From the exhibit we see: Resequence Level: component Resequence Mode: Best Effort It is important to note that the messages to outbound services of the Oracle Mediator service component configured for best effort resequencing are not guaranteed to arrive in order of a sequence…
Question
View the Exhibit. A user has configured Mediator M1 to receive and route product Information from System X into its internal applications in chronological order. For each product1 M1 receives one create number of "update" events from an AQ Queue via a JMS adapter. M1 can receive updates to the product at any time of day. The user claims that incoming messages for each product are received and processed in the correct chronological order 95% of the time. However, the messages are being processed out of order 5% of the time. This results in critical errors in the target systems. The user expects all messages pertaining to a product to be unconditionally processed In the order of arrival at M1. What causes this discrepancy?
Exhibit
Options
- AThe user is running on a four node SOA cluster and has not configured the inbound JMS adapter
- BThe user is running a single-node SOA environment but has configured the number of inbound
- CThe given Mediator configuration does not address this sequencing requirement.
- DThe user has configured resequencer worker threads to a value greater than 1 for the Mediator
How the community answered
(35 responses)- A9% (3)
- B17% (6)
- C71% (25)
- D3% (1)
Explanation
- From the exhibit we see: Resequence Level: component Resequence Mode: Best Effort * It is important to note that the messages to outbound services of the Oracle Mediator service component configured for best effort resequencing are not guaranteed to arrive in order of a sequence ID. At any given time, a snapshot of the available messages is taken and sequencing is performed only on those messages. Therefore, unlike a standard resequencer, it is not guaranteed that a message with a lesser sequence ID value is sent before a message that ha a greater sequence ID value but that arrived earlier. Messages with a lesser sequence ID value that arrive later might be processed in the following cycle when a snapshot of available messages is taken again and the messages are reordered.
Topics
Community Discussion
No community discussion yet for this question.