The most direct and lowest-risk method is to use the Clone button in the Data Mapper Designer. Cloning preserves the original Data Mapper configuration and creates a separate copy that can be modified for the new requirement. Manual copy-and-paste is inefficient and error-prone because mappings, formulas, filters, and output paths can easily be missed. Using SFCLI or deployment tooling to duplicate JSON is possible for advanced source-control workflows, but it is not the most straightforward designer-based approach. Creating an Integration Procedure to call the old Data Mapper does not create a new independent Data Mapper and would not let the developer safely change the mapping logic for the new requirement. Cloning is the intended starting point for this scenario.

The Additional Input property allows the developer to specify additional input parameters to be sent to the Integration Procedure element. The input parameters can be specified as a JSON object or as a list of key- value pairs. If the developer checked Send Only Additional Input, then only the input parameters specified in Additional Input are sent, and the SEND/RESPONSE TRANSFORMATIONS are ignored. Therefore, the developer needs to specify the same input parameters as in the SEND/RESPONSE TRANSFORMATIONS in Additional Input. Option C shows how to do this using a JSON object with two properties: "DBExtractAction:
Account" and "DBExtractAction:SecondaryAccount". The values of these properties are the same as in the SEND/RESPONSE TRANSFORMATIONS.

The correct answer is D, but with one serious qualification: the Data Mapper must be configured with the proper security controls. Data Mapper Load is the OmniStudio component used to write JSON, XML, or custom input data to Salesforce objects. For secure storage, the save operation should rely on Salesforce object access, field-level security, sharing, and OmniStudio security settings rather than storing sensitive values in temporary session variables or assuming the UI framework handles everything automatically.
Validation rules help data quality, not full access control. Session Variables are not the correct place to persist sensitive business data. Therefore, Data Mapper Load is the correct saving mechanism, supported by Salesforce security configuration.

The DataRaptor Formula tab allows the developer to define formulas using functions and operators to manipulate data. The TOINTEGER function converts a string value to an integer value. The developer can use this function to output the field value as an integer and use the formula as output

The correct tool is the Test Data and Parameters panel in the FlexCard Designer. The requirement is specifically to test the FlexCard directly in its designer with different JSON inputs before deployment. The OmniScript Test Console is for OmniScript logic, not FlexCard data rendering. IDX Workbench is a migration
/deployment tool, not the FlexCard's built-in data-testing panel. A Data Mapper Turbo Extract preview only tests the Data Mapper query output; it does not validate how the FlexCard processes different JSON structures and renders states, fields, or conditional elements. Salesforce documentation for FlexCard testing describes adding test parameters in the FlexCard Designer and previewing/debugging the card using those values, which directly supports option C.