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.

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

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

Setting the Timeout property on the HTTP Action in the Integration Procedure allows the developer to specify how long to wait for a response from the external system before timing out. Checking the Chain on Step Check on the HTTP Action in the Integration Procedure allows the developer to chain multiple HTTP Actions together and execute them sequentially. Configuring a Remote action with timeout settings of 120000 is not necessary, as it is already done by default in OmniStudio. Checking the Chainable checkbox on the integration procedure Action in the OmniScript has no effect on calling an external system.

A Data Mapper Extract Action is the correct choice when an OmniScript must retrieve many fields from a Salesforce record. Data Mapper Extracts are built specifically to read Salesforce data, select the required fields, apply filters, and return the data in JSON, XML, or another configured output structure. A Lookup element is appropriate for retrieving or selecting a single record or field value, but it is not the best tool for pulling many fields. HTTP Action is for calling external HTTP endpoints, not directly querying Salesforce records. Select is a user-input element, not a Salesforce data retrieval tool. For a multi-field Salesforce record retrieval requirement, Data Mapper Extract provides the correct declarative query and mapping capability.

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

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 best answer is D because the requirement combines two constraints: the OmniScript must be embedded on a third-party website and it must be prefilled using URL-passed data. An Experience Cloud page can host the OmniScript, and the third-party website can embed that page in an iFrame while passing URL parameters. Salesforce documentation confirms that OmniScript URL parameters can prefill fields and must use the c__ prefix in URL query-string format. Option A describes the parameter style, but by itself it does not explain how the OmniScript is embedded on the third-party website. Option C is the standard off-platform LWC/OmniOut-style idea, but the question specifically emphasizes URL-based prefill, which fits the Experience Cloud/iFrame pattern more directly.

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

 Using two separate Calculation Steps with the Conditional Step property selected allows the developer to specify different formulas based on different conditions. The ISTRUE(isCustomer) and NOT(ISTRUE(isCustomer)) functions are used to evaluate the Boolean variable in the Condition syntax. The other options are either missing the Conditional Step property, using incorrect comparison operators, or using an IF statement instead of separate Calculation Steps.

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

From OmniStudio Best Practices for Modular Script Design, OmniScript Actions are the preferred mechanism to invoke another OmniScript within a parent OmniScript. This approach enables reusability and modularization, especially when a function (like updating billing information) is common across many interactions.

A. OmniScript Action – This is the correct and standard method for embedding or launching one OmniScript from another. It allows developers to reuse common scripts without duplicating logic.

Incorrect Options:

B. Custom Action requires custom Apex or LWC development, which is unnecessary for this use case.

C. Lightning Action is typically used to invoke OmniScripts from Lightning pages, not within OmniScripts themselves.

OmniStudio Developer Guide → OmniScript Actions

The best practice is to create a separate child FlexCard for the related-contact display. A child FlexCard gives the team a reusable UI component that can be embedded in other FlexCards without copying layout elements, actions, fields, and styling each time. Duplicating the elements would create maintenance problems because later changes must be repeated everywhere. A global CSS class can standardize appearance, but it does not make the component logic reusable. A Data Mapper can retrieve or transform data, but it is not a display component. Salesforce documentation confirms that FlexCards can be embedded inside other FlexCards and can use either their own data source or the parent FlexCard’s data, which supports modular reuse.

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