An Edit Block is specifically designed to allow users to dynamically add, edit, and remove repeating sets of information within an OmniScript. In this scenario, each car requires the same group of fields, and the number of cars is not known in advance. The Edit Block provides an efficient way to manage this variable-length collection of records while maintaining a clean user experience. A Formula element performs calculations but does not create repeatable input sections. A Step organizes navigation between pages of an OmniScript but does not provide dynamic row management. A Text Block displays static content and instructions only. Edit Blocks are a common OmniStudio design pattern whenever business requirements involve repeating data- entry structures such as vehicles, dependents, addresses, products, or beneficiaries.

Explanation
The OmniStudio tools that should be recommended to meet these requirements are single OmniStudio Action that invokes separate Omniscripts. OmniStudio Action can be used to conditionally launch different Omniscripts based on the record type of the contact. Omniscripts can be used to implement the verification processes for each type of contact. Specific FlexCards with Actions for each type of Contact would require creating redundant FlexCards and Actions for each record type. Multiple OmniStudio Actions that invoke separate Omniscripts would require creating redundant Actions for each record type. Single FlexCard with an Action to invoke an Omniscript would not allow for different verification processes based on the record type.

Explanation
The three OmniScript elements that the consultant should recommend to meet these requirements are:
DataRaptor Post Action, Multi-select Input, and HTTP Action. A DataRaptor Post Action is an action that can write data to a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Post Action to save the data back to Salesforce as a lead. A Multi-select Input is an element that can display a list of options for the user to choose from, such as energy products. A Multi-select Input allows multiple options to be selected at once, and can also have icons for each option. An HTTP Action is an element that can invoke a REST or SOAP service to retrieve data from an external system, such as current energy usage data. An HTTP Action can store the response data in a JSON object for further processing

* Define the script in the OmniScript Designer (D) - The first step in creating an OmniScript is to define it in the OmniScript Designer, where the consultant:
* Outlines the flow of the script (steps, inputs, actions).
* Adds UI elements (text fields, picklists, buttons).
* Configures integration points (DataRaptors, Integration Procedures).
* A. Create a new Salesforce application for the script - This is not required to build an OmniScript.
OmniScripts can be deployed within existing Salesforce applications.
* B. Deploy the script within a Salesforce application - Deployment happens after the script is built and tested, not as the first step.
* C. Test the script on multiple channels and devices - Testing is an important step after building and configuring the script.
Comprehensive and Detailed In-Depth Explanation:Why not the other options?? Salesforce OmniStudio Reference:
* OmniScript Designer Guide
* Creating OmniScripts