Explanation/Reference:
Note:
Events allow one system (event emitter) to notify other systems (event sink) that something of interest has changed. There are two broad categories of event types:
* Business Event - A business event is an event that is of business relevance and would be readily understood by a business person.
* Technical Event - A technical event is an event that is relevant to IT but not directly relevant to the business.
As illustrated by the figure below, in this architecture all events are routed to the Business Process Layer and the appropriate business processes are executed for that event. Essentially this is a mechanism for a lower level in the architecture stack, the Connectivity Layer, to initiate actions that might include interactions with all other levels in the architecture. This is essential since the generated event will likely be backend system specific; therefore it is likely that the data must be normalized and some amount of custom logic may be required to convert the event into an event that is backend system agnostic.

Incorrect answers:
A: ESD (ORA and ETS) is a part of ITSO. ESD is not a subset of SOI.
B: This event handling approach is not suitable for very high volume events (e.g. stock ticker) since each event triggers a business process. Complex event processing (CEP) is not included in this architecture.
Additional capabilities not including in this architecture are required to handle CEP and high volume events C: This is not how the event handling works.
E: Handling high volumes is not the main benefit of the event-handling here.
Reference: Oracle Reference Architecture, Service-Oriented Integration, Release 3.0