Salesforce OmniStudio-Developer - Salesforce Certified OmniStudio Developer Plat-Dev-210

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.

================

A FlexCard is the correct front-end component for a single, focused view on a Contact record page. The data may come from Salesforce and an external grant management system, and an Integration Procedure can be used behind the scenes to aggregate that data. However, the question asks which OmniStudio tool should retrieve and display the combined information in a compact record-page view. A Data Mapper Transform reshapes data but does not provide the visual record-page card. A Calculation Procedure performs calculation logic, not case-manager display. OmniScript is better for guided multi-step processes, not quick contextual viewing. Salesforce documentation confirms that FlexCards can be configured with data sources, including Salesforce or external databases, and can display contextual information on record pages.

================

The merge code syntax for accessing a node from an Integration Procedure output is {{ProcedureName:NodeName}}. In this case, the ProcedureName is HTTPGetCaseDetails and the NodeName is CaseData. The % sign is used for single-value merge codes, not node merge codes. The $ sign is used for variables, not merge codes.

The child OmniScript must receive specific nodes from the parent OmniScript’s data JSON, so the developer should pass them through Additional Input key/value pairs on the child OmniScript element. Additional Input is used to pass named values into an action or embedded component when the child process needs specific data from the current script context. ContextId would pass only a record identifier, not full Address and Contact JSON nodes. PreFill is used to populate data into an OmniScript, but the question asks which property on the child OmniScript element should be used to pass parent nodes. LWC Component Override is unrelated because it replaces rendering behavior rather than mapping parent script data. Therefore, Additional Input is the correct configuration.

================

Runtime OmniScript access alone is not always enough when the OmniScript executes Data Mappers, Integration Procedures, or Remote Actions that rely on Apex-backed services. Salesforce has OmniStudio security checks for Apex class access, and its documentation specifically describes configuring Apex class permission checkers so users require explicit access to the Apex class that administers a Remote Action. Save Options do not control Lightning component authorization. Multi-language settings affect labels and translations, not runtime component permissions. FlexCard permissions are not the most likely cause because the error occurs while launching an OmniScript and the scenario already confirms OmniScript runtime access. The developer should therefore investigate missing Apex class access behind the OmniScript’s actions.

================

 According to the OmniScript Data JSON page, 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 three elements: Step, Block, and Telephone. The Step element is an empty object, the Block element is an object with two properties: Text and Telephone, and the Telephone element is a string. Therefore, the JSON code that correctly represents the step in the OmniScript Structure panel shown is option C, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

The correct answer is JSON. Vlocity Build Tool, also called the OmniStudio Build Tool in newer documentation, exports and deploys OmniStudio/Vlocity DataPacks in a source-control-friendly structure. A Data Mapper, FlexCard, OmniScript, or Integration Procedure is represented as DataPack metadata, and the component definition is stored in JSON-based files, while job or manifest configuration can use YAML. DOCX is a document format and has no role in OmniStudio deployment metadata. CSV can hold tabular data, not a full component definition. XML is used in some Salesforce metadata contexts, but DataPacks for OmniStudio deployment are not typically represented as XML component files. Therefore, JSON is the correct deployment metadata format.

================

The correct configuration is the Knowledge Articles property on the Step element. OmniScript supports Salesforce Knowledge integration through Knowledge Options configured on a Step. This lets the developer display or filter Knowledge content where the user needs it in the guided process, such as a complex product-information step. A Knowledge Action is not the standard OmniScript element used for step-level help article display. Messaging Framework is unrelated because it handles messaging behavior, not Knowledge article rendering. A custom LWC could be built, but that would be unnecessary custom development when OmniScript already provides Knowledge configuration on the step. The requirement is step-specific, context-sensitive article display, so the Step element’s Knowledge Articles configuration is the correct answer.

================

The PREVIEW tab in OmniScript allows the developer to test the DataRaptor Extract by providing a record ID and viewing the output data. This is a quick and easy way to troubleshoot whether the DataRaptor Extract is retrieving data correctly.

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.

================