Salesforce Certified OmniStudio Developer Plat-Dev-210 Exam Questions

Answer : A

The requirement is element-level visibility: only one Overdue status block must appear when Account Balance is greater than zero. The correct FlexCard configuration is a rendering condition directly on the Block element. FlexCard element conditions are designed to show relevant information based on field values from the card's data source. Creating a separate Card State is excessive because the whole card layout does not need to change; only one block must be conditionally visible. A Setup tab filter controls data retrieval, not the display of a specific UI block after data is returned. A Flyout action is also unrelated because it opens additional content after user interaction. The verified implementation is to add a rendering condition to the Block element.

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

Answer : C

The Conditional View property on the Step elements is the correct client-side control. The branching depends on a value selected earlier in the OmniScript, and the constraint explicitly says not to use server-side logic. Conditional View can hide or show elements, blocks, or steps based on conditions in the OmniScript data JSON. Pub/Sub on FlexCard elements is unrelated because this is an OmniScript step-visibility problem, not inter-component messaging. An Integration Procedure conditional block would push the path decision to server-side logic, violating the requirement. A Data Mapper does not control UI step visibility. Salesforce documentation states that Conditional View hides an element or group of elements in a block or step based on specified conditions, which fits this scenario precisely.

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

Answer : A

Navigation button labels such as Next are controlled through OmniScript setup-level label mapping/custom label configuration, not by editing each Step element or creating Navigate Actions. The Next button is part of the OmniScript framework navigation, so changing it globally for the script belongs in the setup configuration where element names and labels can be mapped. A Navigate Action is used to navigate to another page or component; it is not the framework Next button. LWC Component Override is for replacing component rendering behavior with a custom LWC, which is excessive and incorrect for a simple label change. Salesforce documentation describes OmniScript setup configuration and custom label references for OmniScript properties, supporting the setup-label approach.

Answer : D

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.

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

Answer : C

For an active OmniScript, the correct practice is to create a new version, make the change in that new version, test it, and activate it only when it is ready. Editing the active version directly is risky because users can be affected immediately, and in-flight users may experience inconsistent behavior. Cloning creates a separate component and is useful when the new script must be independent, but it is not the best approach for a minor controlled change to the same OmniScript. Waiting for a Salesforce release is irrelevant because this is a configuration lifecycle issue, not a platform-release dependency. Salesforce's OmniStudio versioning guidance supports using versions so changes can be validated before replacing the active version used by end users.

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

Answer : C

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.

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

Answer : A

The correct exam answer is A, but the wording needs care. An OmniScript must have an active version before it can run for users. Salesforce documentation confirms that OmniScripts are activated from the OmniScript designer and that the active version is the runnable version. If a deployment path moves the component definition but does not leave the desired version active or compiled correctly, the final required step is to activate the deployed OmniScript version in the target org. Response Action is an Integration Procedure concept and is not required merely to launch an OmniScript. Remote Site Settings matter only for external callouts. Cache Duration affects performance behavior, not whether the OmniScript itself is runnable. Note: IDX Workbench can auto-activate in some managed-package deployment flows, so the safest interpretation is non-auto-activated deployment.