Setting the Timeout property on the HTTP Action in the Integration Procedure allows the developer to specify how long to wait for a response from the external system before timing out.
Checking the Chain on Step Check on the HTTP Action in the Integration Procedure allows the developer to chain multiple HTTP Actions together and execute them sequentially. Configuring a Remote action with timeout settings of 120000 is not necessary, as it is already done by default in OmniStudio. Checking the Chainable checkbox on the integration procedure Action in the OmniScript has no effect on calling an external system.

The Timeout property on the HTTP Action in the Integration Procedure specifies how long to wait for a response from the external system before throwing an error. The Chain On Step checkbox on the HTTP Action in the Integration Procedure indicates that the next action should be executed only if the current action is successful. These two configurations should be used to implement the call to the external system given its known performance issues.

In OmniStudio, the Edit Block element is purpose-built for allowing users to dynamically add, edit, or delete rows of related data, such as dependents under a policy. To save these changes, Remote Actions (typically backed by Apex or API) are used to process each record operation (Create/Update/Delete).
* A. Use an Edit Block element configured with Remote Actions - Correct. This is the recommended and most scalable way to support CRUD operations in OmniScripts for collections (e.g., dependents).
The Edit Block provides UI-level support, while Remote Actions handle back-end interaction with Salesforce or external systems.
Incorrect Options:
* B. Text Block is for display purposes and cannot manage data input or backend actions.
* C. Input Block elements do not support row-level add/edit/delete functionality as Edit Blocks do.
* D. SOQL is a read-only query language and cannot be used to update or delete records directly within an OmniScript.
:
Salesforce OmniStudio Guide # OmniScript Edit Block Element
OmniStudio Best Practices # CRUD Operations in OmniScripts

Using two separate Calculation Steps with the Conditional Step property selected allows the developer to specify different formulas based on different conditions. The ISTRUE(isCustomer) and NOT(ISTRUE (isCustomer)) functions are used to evaluate the Boolean variable in the Condition syntax. The other options are either missing the Conditional Step property, using incorrect comparison operators, or using an IF statement instead of separate Calculation Steps.

In OmniStudio, the Invoke Mode: Fire and Forget setting allows an OmniScript to call an Integration Procedure asynchronously, meaning it does not wait for the response to complete before continuing user interaction.
* C. Invoke Mode Fire and Forget - This is the correct setting. It's designed specifically for use cases where the user experience should not be blocked by backend processing.
Incorrect Options:
* A. Use Future is not a valid OmniScript configuration option.
* B. Invoke Mode Non-Blocking is not an official setting in OmniStudio terminology.
* D. Toast Completion is a UI notification setting and does not impact execution behavior.
:
OmniStudio Developer Guide # Integration Procedure Actions in OmniScripts