To retrieve (read) data from Salesforce objects:
A). Data Mapper Extract Action ?Correct. A DataRaptor Extract is specifically used to retrieve data from Salesforce, based on input parameters or context.
C). Lookup Input Element ?Correct. This is used within OmniScripts to look up a record by matching input data, essentially performing a read operation.

A DataRaptor Transform can be used to transform data from one format to another, such as JSON, XML, or CSV. The developer can specify the input and output paths for each field in the Transform tab. The developer can also use formulas to manipulate data in the Formula tab1. To transform contact data into a JSON array, the developer can use either of these methods:
* Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab. This will create a list of contact objects from the input JSON and output it as a JSON array.
* Set the Input JSON Path as Contact, the Output JSON Path as Contact, and the Output Data Type as List. This will output each contact object as an element of a JSON array.

Turbo Extract is a high-performance mode for DataRaptor Extracts that improves query efficiency and response time, particularly useful when retrieving large datasets.

In OmniStudio Integration Procedures, when referencing data from a prior step in the HTTP Action URL, the correct merge code syntax is:
* %ElementName.PropertyName%
So, referencing a value called Date from a step named SetValues must be written as:
* %SetValues.Date%
This is the format recognized by the OmniStudio Merge Language (OML) for dynamic value substitution in URLs or headers.
Incorrect Options:
* A. Invalid syntax - not recognized by OmniStudio merge logic.
* B. {{SetValues.Date}} is used in FlexCards, not in Integration Procedures.
* D. %SetValues: Date% is incorrect merge syntax due to space and colon use.
:
Salesforce OmniStudio Documentation # Merge Code Syntax for Integration Procedures

An Integration Procedure Action can execute an Integration Procedure that contains multiple elements, such as DataRaptor Actions, HTTP Actions, or other Integration Procedure Actions. This can be used to save data to multiple systems, such as Salesforce and AWS Order Management, in one OmniScript element.