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

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.

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

According to Salesforce OmniStudio Integration Procedures documentation, when working with deeply nested JSON, Integration Procedures are ideal. They allow developers to flatten and manipulate JSON data, especially when handling external responses.

C. Integration Procedure – This is correct. IPs provide Response Transformers, DataRaptor Transforms, and Response Actions to reshape and simplify nested data structures for consumption by front-end components.

Incorrect Options:

A. DataRaptor Transform is used inside IPs but cannot directly handle external HTTP calls or manage complex orchestration.

B. HTTP Action Element is used inside an Integration Procedure, but by itself, it does not process or simplify the data.

D. Guided Workflow is not a recognized OmniStudio component for data transformation.

OmniStudio Integration Procedures Guide → Handling Nested JSON

FlexCards can run outside Salesforce through OmniOut, where the activated FlexCard is downloaded or used as a Lightning Web Component and then added to the external OmniOut project. This means the external app must be set up to host and run the generated LWC-based component, typically through Lightning Web Runtime or the OmniOut application structure. Visualforce is not the right technology because the requirement is an external non-Salesforce web application. Calling the Salesforce API may retrieve data, but it does not render the FlexCard user interface. Wrapping the FlexCard inside a custom LWC first is also unnecessary because OmniStudio already generates the FlexCard as an LWC artifact for external use.

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

 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.

 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.

Invoke Mode Non-Blocking is the correct choice because the OmniScript still needs the Integration Procedure response, but the user interface should not be blocked while waiting. Salesforce describes Non-Blocking as running asynchronously while applying the response to the UI. Fire and Forget is different: it is used when the caller does not need a response returned to the OmniScript. Use Future is also asynchronous, but it is best when completion timing is not critical and no response is required. Toast Completion only controls a user notification style; it does not determine whether the OmniScript waits for the Integration Procedure response. Since the response must still come back as JSON while the user proceeds, Non-Blocking is the correct feature.

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

 The Send JSON Path syntax for accessing an element from an Integration Procedure structure is BlockName.ElementName. In this case, the BlockName is BlockX and the ElementName is ActionZ. The colon (:) is used to separate the input and output parameters, not the block and element names. The order of the block and element names should follow the hierarchy of the structure, from top to bottom. The Additional input parameter is not needed in this case, as it is already included in the Send JSON Path.

The correct approach is to use the responsive sizing properties available in the element Display configuration, such as Extra Small, Small, Medium, and Large. These settings align the element with the responsive grid model instead of forcing custom widths. Newport Design System styling is intended to provide consistent visual behavior across OmniScripts and FlexCards, so using framework-supported sizing is cleaner than hard-coding CSS. Option B can add utility classes, but it is not the primary standard grid-sizing property for the input element. Option D is weaker because custom CSS makes the layout harder to maintain. Option A is unrelated because Repeat CSS is not the standard way to control horizontal grid width.

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