Event-Driven Architectures (EDA) provide real-time responsiveness and resilience by:
Real-time data processing # Immediate reaction to business events (e.g., order creation, stock changes).
Decoupling of components # Producers and consumers are independent, allowing flexible scaling.
Fault tolerance # Failures in one component do not propagate due to event buffering and loose coupling.
Incorrect options:
A # Batch processing delays responsiveness.
C # EDA minimizes manual intervention.
D # Tight coupling is opposite to EDA principles.

In SAP Cloud Integration (part of Integration Suite), error handling within integration flows is implemented using:
Exception Subprocesses # Dedicated subprocesses triggered by an Error Start Event to handle unexpected runtime exceptions.
These allow logging, error notifications, or compensating logic.
Other options:
Try-Catch subprocesses # Not a modeling construct in SAP CPI.
Exception handler integration flow elements # Not a standard artifact; error handling is done with exception subprocesses.
Status code checks # Useful for response validation but not full error handling.
Thus, the correct answer is Exception-handling subprocesses.

To configure a SOAP adapter for asynchronous processing, you must set the message exchange pattern to one-way and the process settings to WS standard. The message exchange pattern defines how the sender and receiver communicate with each other using SOAP messages. The one-way pattern means that the sender sends a message to the receiver without expecting a response. The process settings define how the SOAP adapter handles errors and acknowledgements during message processing. The WS standard setting means that the SOAP adapter uses WS-ReliableMessaging protocol to ensure reliable delivery of messages and WS-Addressing protocol to identify the endpoints and actions of messages. Reference: Configure the SOAP (SOAP 1.x) Sender Adapter | SAP Help Portal, Configure the SOAP (SOAP 1.x) Receiver Adapter | SAP Help Portal

To activate Event Mesh (EMIS) capability in SAP Integration Suite, the required role collections are:
Integration_Provisioner # Allows provisioning of new capabilities (including Event Mesh) in Integration Suite.
Subaccount Administrator # Grants permission to manage and configure subaccount-level entitlements and service activations.
Other options:
Integration_Administrator, API_Manager, Monitoring_Viewer # Used for operational tasks, not provisioning.
Process_orchestrator # Refers to on-premise PI/PO, not BTP roles.
Security_Auditor # Auditing role, not activation.
Thus, the correct roles are Integration_Provisioner and Subaccount Administrator.

A product in the API Management capability within SAP Integration Suite is a bundle of one or more API proxies that are grouped together for a specific business scenario or use case. A product is a separate artifact that can be deployed to the API business hub enterprise, which is a centralized platform for discovering, consuming, and managing APIs. A product can have its own metadata, such as name, title, description, quota limits, and so on. A product can also have its own policies that apply to all the APIs included in it. Reference: Create a Product | SAP Help Portal, API Business Hub Enterprise | SAP Help Portal