Salesforce Plat-Dev-210 Practice Exam Questions & Answers

According to theOmniScript Data JSONpage, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with six elements: ContactName, ContactPhone, ContactEmail, CaseNumber, CaseSubject, and CaseStatus. The DRGetContactDetails action is a DataRaptor Extract action that retrieves data from the Contact and Case objects in Salesforce. The BlkCases element is a Repeat Block that displays a list of cases related to the contact. Therefore, the JSON from the DRGetContactDetails action that would display all six values correctly shown is option A, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown.

The Integration Procedure needs three separate responsibilities: retrieve Salesforce data, process it with Apex, and return the final response. A Data Mapper Extract Action reads Salesforce data and returns selected records and fields to the Integration Procedure data JSON. A Remote Action calls an Apex class method or invocable action, which satisfies the requirement to process data through Apex. A Response Action then returns the final data to the caller. Data Mapper Post Action is wrong because it writes data to Salesforce rather than retrieving it. HTTP Action is wrong because it calls an external REST endpoint, not an Apex class. The correct Integration Procedure design is therefore Data Mapper Extract Action, Remote Action, and Response Action.

The data action should be placed where the step can retrieve the required data before the user needs to see or use it. Placing the Data Mapper Extract Action on the same relevant step keeps the data retrieval close to the UI elements that depend on it and avoids loading unrelated data globally in the Header. Placing the action after the data usage is obviously too late because the fields or options would already be rendered without the needed values. A Set Values element cannot execute a Data Mapper Extract; it only sets or changes values in the OmniScript data JSON. Salesforce's OmniScript action-element documentation explains that action elements are used to get, modify, and write data during the OmniScript process.

Updating Salesforce data from an OmniScript requires a write operation, so the correct tool is a Data Mapper Load. A Data Mapper Extract reads data from Salesforce; it cannot update the Contact record. A Data Mapper Transform only reshapes data between formats and does not perform the Salesforce database update. The Data Mapper Load should include the Contact identifier and the new Phone value so Salesforce can update the correct record. When upsert behavior is needed, the appropriate field mapping must identify the key used to determine whether the record already exists. The question asks specifically about changing a Contact phone number from an OmniScript, so the correct configuration is a Data Mapper Load with the RecordId/key and updated phone value.

The correct Output JSON Path is input:BasePrice. The required JSON places BasePrice inside the lowercase input node, so the path must preserve both the correct parent node and the exact field name casing. Option A is wrong because it uses dot notation and incorrectly lowercases BasePrice as baseprice. Option B is wrong because it uses Input with an uppercase I, while the JSON node is input. In JSON-based mappings, path and field names must match the expected output structure. Salesforce's Data Mapper Transform documentation states that the Output JSON Path defines the desired output path and that path levels are separated using colon syntax, for example Contact:LastName. Therefore, C is the only mapping that correctly targets the BasePrice node under input.

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.