A Text Block element allows the developer to display read-only text in a table format, using merge codes to dynamically include data from the data JSON. A Rich Text Area element is used to display formatted text with images and links. A Text Area element is used to display editable text in a single line or multiple lines. An Edit Block element is used to display editable fields in a form layout.

The correct answer is Option B, which shows a FlexCard with a header, a body, and a footer. The header contains the title and the icon of the FlexCard. The body contains a Data table element that displays the records from the parent FlexCard. The footer contains a navigation Action that invokes an OmniScript.
Option A is incorrect because it shows a FlexCard with only a header and a body, and no footer.

OmniStudio provides deployment tooling (such as the Industries CLI or the OmniStudio Deployment Manager) that allows developers to package and migrate OmniStudio components as metadata between orgs, since core components are stored as custom object records requiring specialized tooling beyond standard Change Sets.

According to Salesforce OmniStudio Integration Procedures documentation, when working with deeply nested JSON, Integration Procedures are ideal. They allow developers to flatten and manipulate JSON data, especially when handling external responses.
* C. Integration Procedure - This is correct. IPs provide Response Transformers, DataRaptor Transforms, and Response Actions to reshape and simplify nested data structures for consumption by front-end components.
Incorrect Options:
* A. DataRaptor Transform is used inside IPs but cannot directly handle external HTTP calls or manage complex orchestration.
* B. HTTP Action Element is used inside an Integration Procedure, but by itself, it does not process or simplify the data.
* D. Guided Workflow is not a recognized OmniStudio component for data transformation.
:
OmniStudio Integration Procedures Guide # Handling Nested JSON

The Invoke Mode Fire and Forget feature enables the OmniScript to invoke the Integration Procedure without waiting for a response. This is useful when the response is not needed for the user to proceed