Salesforce Plat-Dev-210 Exam Dumps

According to theOmniStudio Developer Guide, ''To upsert a record, select the Upsert Key checkbox for the field that contains the unique identifier for the record. If you want to create a new record when no match is found, select Is Required for Upsert.'' Therefore, the correct answer is B.

The LWC PubSub Message flag in the Set Values action of the parent OmniScript enables the parent OmniScript to send data to the embedded OmniScript using a custom event. If this flag is not set, the data will not be passed to the embedded OmniScript.

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.

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

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.

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

A Try-Catch Block is the correct element because the requirement is controlled error handling. The Data Mapper Load can fail because of a validation rule, but the Integration Procedure must keep running and return a user-friendly error message rather than immediately terminating. A Group element organizes or conditionally executes steps, but it does not provide exception handling by itself. A Set Values element can prepare the friendly message after the error is caught, but it cannot catch the failure. A Response Action returns the final payload, but it should not wrap the risky operation. Salesforce Integration Procedure guidance specifically identifies Try-Catch Blocks as the mechanism for handling errors inside Integration Procedures.

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