Pass the Salesforce Developer OmniStudio-Developer Questions and answers with ExamsMirror

The child Integration Procedure must return the full generated payload, so the Response Action must point to the full/root response instead of a narrowed child node or single response parameter. Setting the Response JSON Path to the root node is the explicit configuration in the given answer set. A Data Mapper Transform can reshape data, but it does not define the final return payload of the Integration Procedure. A single Response Parameter named Output with %AllData% is not the standard configuration. Leaving parameters blank can be acceptable in some caller configurations when the default behavior returns all data, but the question asks what to configure on the child Response Action, and the explicit root Response JSON Path is the strongest answer.

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

Two separate Group elements with mutually exclusive conditions provide the cleanest declarative control. One Group should execute only when updateBillingAddress is true and updateShippingAddress is false. The other Group should execute only when updateShippingAddress is true and updateBillingAddress is false. This enforces that only one address update path runs. A single OR condition would allow either or both flags to be true, so it cannot prevent simultaneous updates. A Try-Catch Block reacts after an error occurs; it is not the right way to express business-rule branching. An HTTP Action would add unnecessary external dependency. Integration Procedure blocks and groups are designed to run related steps conditionally, so mutually exclusive Group conditions are the correct structure.

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

 Option D is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have the same key/value pairs as Input Data, and the value should be set to {{InputData.key}} for each key. This will pass the value of Input Data for each key to Additional input.

The verified answer is A, not the mock-highlighted C. FlexCard States display based on conditions configured on the state. For this scenario, the Active, Warning, and Critical states should each have a condition that evaluates the RiskLevel value. For example, Active can evaluate RiskLevel = Low, Warning can evaluate RiskLevel = Medium, and Critical can evaluate RiskLevel = High. At runtime, OmniStudio evaluates the state conditions, and the matching state is displayed. A Set State Action on a button is user-driven and does not automatically evaluate RiskLevel. “Conditional State Logic on the Base FlexCard” is not the precise configuration item used here. A main Block state variable is also not what controls card-level state selection.

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

 The Params node contains the data that is passed from the parent FlexCard to the child FlexCard. The developer should use {Params.postalcode} to refer to the contact’s postal code in the child FlexCard.

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

In OmniScripts, if you need to apply a function (like COUNTIF) to dynamic data and show the result immediately, the Formula element is the correct choice.

B. Formula element – The Formula element supports real-time calculation using OmniStudio expression functions (like COUNTIF, SUM, etc.) and updates values instantly on the screen without the need for server calls.

Incorrect Options:

A. Set Values element is used to set static or conditional values but doesn’t support formula evaluation.

C. Range element is used for value comparisons and conditions, not for calculations.

Salesforce OmniStudio Developer Guide → OmniScript Formula Element

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

A DataRaptor Transform can be used to transform data from one format to another, such as JSON, XML, or CSV. The developer can specify the input and output paths for each field in the Transform tab. The developer can also use formulas to manipulate data in the Formula tab1. To transform contact data into a JSON array, the developer can use either of these methods:

Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab. This will create a list of contact objects from the input JSON and output it as a JSON array.

Set the Input JSON Path as Contact, the Output JSON Path as Contact, and the Output Data Type as List. This will output each contact object as an element of a JSON array.

A DataRaptor Load Action can be used to retrieve data from a Salesforce object by specifying the object name, fields, and filter criteria. A Lookup Input Element can be used to retrieve data from a Salesforce object by allowing the user to search for a record using a lookup field