Updated Jun-2026 Test Engine to Practice Plat-Dev-210 Test Questions
Plat-Dev-210 Real Exam Questions Test Engine Dumps Training With 107 Questions
Salesforce Plat-Dev-210 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
NEW QUESTION # 23
Which two of these options can a developer use to retrieve data from a Salesforce object?
Choose 2 answers
- A. Data Mapper Post Action
- B. Data Mapper Extract Action
- C. Lookup Input Element
- D. Data Mapper Load Action
Answer: B,C
Explanation:
To retrieve (read) data from Salesforce objects:
* A. Data Mapper Extract Action - Correct. A DataRaptor Extract is specifically used to retrieve data from Salesforce, based on input parameters or context.
* C. Lookup Input Element - Correct. This is used within OmniScripts to look up a record by matching input data, essentially performing a read operation.
Incorrect Options:
* B. DataRaptor Post is not a valid DataRaptor type.
* D. DataRaptor Load Action is used for writing/updating data, not retrieving it.
:
Salesforce OmniStudio Guide # DataRaptor Types and Lookup Input Element Usage
NEW QUESTION # 24
A customer sets up to LWC Omniscripts, one embedded into another. Account is set in a Set Values element in the parent Omniscript.
The AccountId set in the parent Omniscript is used to another Set Values element ContextAccountid in the embedded OmniScript. The embedded Omniscript is activated.
While previewing the OmniScript flow from the parent, it is found that Account is set correctly in the parent OmniScript. However. ContextAccountId in the embedded OmniScript is not set with the AccountId from parent Omniscript. On previewing the embedded OmniScript individually, it is found that ContextAccountId is set correctly.
What is the reason for this? Refer to the exhibit below.
- A. Both parent and embedded OmniScripts have the same element name for the Set values element.
- B. The LWC PubSub Message flag in the Set Values action of the parent has not been set.
- C. The flag pass Data JSON in the parent OmniScript in not configured correctly.
- D. A developer failed to include a Navigation Element to pass data from the parent OmniScript.
Answer: D
Explanation:
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.
NEW QUESTION # 25
Refer to the exhibit below. What is the merge code needed for this Integration Procedure structure to pass a CaseData node from the HTTP Action's output to the DataRaptor Transform Action?
- A. {{CaseData}}
- B. {{ HTTPGetCaseDetails:CaseData}}
- C. %DRXformCaseData: CaseData%
- D. %HTTPGetDetails:CaseData%
Answer: B
Explanation:
The merge code syntax for accessing a node from an Integration Procedure output is {{ProcedureName:
NodeName}}. In this case, the ProcedureName is HTTPGetCaseDetails and the NodeName is CaseData. The
% sign is used for single-value merge codes, not node merge codes. The $ sign is used for variables, not merge codes.
NEW QUESTION # 26
A developer is configuring an integration Procedure Action in an OmniScript. The Omniscript needs a JSON response from the Integration Procedure but does not need to wait for the response for the user to proceed.
Which feature should the developer enable?
- A. Invoke Mode Fire and Forget
- B. Use Future
- C. Toast Completion
- D. Invoke Mode Non-Blocking
Answer: A
Explanation:
The Invoke Mode Fire and Forget feature enables the OmniScript to invoke the Integration Procedure without waiting for a response. This is useful when the response is not needed for the user to proceed
NEW QUESTION # 27
Refer to theexhibit below. In this integration production structure, what Send JSON Path would be used to send the Output of the Action1 element to a Remote Action?
- A. BlockA: BlockB. Action 1
- B. Action1: BlockB. Block A
- C. Action1. BlockB. Block A
- D. BlockB:BlockB. Action1
Answer: B
Explanation:
The correct syntax for the Send JSON Path is ActionName: BlockName, where ActionName is the name of the action element and BlockName is the name of the block element that contains the output data. The other options are either missing the colon or using incorrect names.
NEW QUESTION # 28
An integration Procedure uses an HTTP action to makea REST API call. The response from the REST API must be converted into a specific XML structure before sending it as an input to another external wen service.
How should the developer configure the Integration Procedure to meet this requirement?
- A. Use a DataRaptor Transform to convert JSON to XML
- B. Use a Remote Action that calls the XMLStreamReader class
- C. Use a Remote Action that calls the XMLStreamWriter class
- D. Use a DataRaptor Extract and check the XML checkbox on the Output JSON Path.
Answer: A
Explanation:
According to the OmniStudio Developer Guide, "DataRaptor Transform actions can convert JSON to XML and vice versa." Therefore, the correct answer is C.
NEW QUESTION # 29
Refer to the exhibit.
All inputs to the Calculation Matric are set correctly.
The Calculation Matrix has the following input:
What is the output?
- A. 12.99
- B. 13.99
- C. 12.99,13.99
- D. Null
Answer: B
Explanation:
According to the Calculation Matrix Overview page, a Calculation Matrix is "a lookup table that takes an input and returns an output". In this case, the input is the ProductCode and the output is the Price. The exhibit shows a Calculation Matrix with four rows, each with a different ProductCode and Price. The input given is ProductCode: HRA3320, which matches the second row of the matrix. Therefore, the output is Price: 13.99, which is the value in the same row.
NEW QUESTION # 30
Refer to the exhibit.
A developer creates an OmniScript display FirstName, LastName, and BirthDate of a contact using a Type Ahead Block. The DataRaptor used in the Type Ahead has been tested and fetches the correct data.
When previewing Omniscript, the developer enters a name in the Type Ahead and makes a selection of a contact from the list. However, the text fields FirstName. LastName, and BirthDate are not getting populated with the data.
What is the reason that the fields fail to display the fetched data?
- A. Use Data JSON is not selected in the properties of the Type Ahead Block.
- B. The Typeghead ley is not in the correct format
- C. FirstName, LastName, and Birthdate are not placed inside the Type ahead Block.
- D. Lookup Mode is not selected in the properties of the Type A Head Block.
Answer: C
Explanation:
The FirstName, LastName, and BirthDate fields should be placed inside the Type Ahead Block, so that they can receive the data from the selected record in the Type Ahead list. The Type Ahead Block has a Data JSON Path property that specifies the path to the data node that contains the record fields. For example, if the Data JSON Path is set to Contact, then the FirstName field should have a Value property set to {{Contact.
FirstName}}.
NEW QUESTION # 31
Refer to the exhibit below. A developer has configured an integration Procedure element with Additional input.
Alternatively, how could the developer configure SEND/RESPONSE TRNSFORMATION to send exactly the same data? Assume the developer has un-checked Send Only Additional input.
- A.
- B.
- C.
- D.
Answer: A
Explanation:
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.
NEW QUESTION # 32
What should a developer's first step be when troubleshooting whether a DataRaptor Extract is retrieving data?
- A. Go to the PREVIEW tab In OmniScript to test.
- B. Deactivate the card and layout, and go to the PREVIEW tab for the card to test.
- C. Add a key/value pair in the DataRaptor to test it.
- D. Go to the Lightning Console and reload the page to test.
Answer: A
Explanation:
The PREVIEW tab in OmniScript allows the developer to test the DataRaptor Extract by providing a record ID and viewing the output data. This is a quick and easy way to troubleshoot whether the DataRaptor Extract is retrieving data correctly.
NEW QUESTION # 33
A developer needs to create a list of cases for an account in a single Datable in a FlexCard. Like the one shown below.
How can the developer configure the FlexCard to display the case records in this way?
- A. Select the Repeatable Mode property on the data table elements
- B. Disable the Repeat Record feature on the FlexCard setup tab
- C. Enable the record Looping feature on the data table elements
- D. Enable the Repeat Records feature on the FlexCard Setup tab
Answer: A
Explanation:
The Repeatable Mode property on the data table elements allows the developer to display multiple records in a single data table. The Repeat Records feature on the FlexCard Setup tab is used to display multiple FlexCards for each record in a data source. The Record Looping feature on the data table elements is used to iterate over a list of records and perform actions on each record. The Overwrite Target for all Null input checkbox on the Account id field is used to overwrite the existing value in the target object with null if the input value is null.
NEW QUESTION # 34
A developer is building an OmniScript and needs to save to Salesforce and to an AWS Order Management system.
Which OmniScript element could save all of this data?
- A. Integration Procedure Action
- B. DataRaptor Load Action
- C. HTTP Action
- D. DataRaptor Post Action
Answer: A
Explanation:
An Integration Procedure Action can execute an Integration Procedure that contains multiple elements, such as DataRaptor Actions, HTTP Actions, or other Integration Procedure Actions. This can be used to save data to multiple systems, such as Salesforce and AWS Order Management, in one OmniScript element.
NEW QUESTION # 35
Refer to the exhibit.
The card layout uses an integration Procedure as a data source. The cards use the layout data source.
Which JSON data structure supports this card layout and follows best practices?
- A.
- B.
- C.
Answer: C
Explanation:
The JSON data structure in option C supports the card layout and follows best practices. It has a list of objects, each representing a product, with the properties "ProductCode", "ProductName",
"ProductDescription", and "ProductPrice". These properties match the fields in the card layout. The JSON data structure also follows the naming convention of using camel case for property names. The JSON data structures in options A and B do not match the fields in the card layout and do not follow the naming convention.
NEW QUESTION # 36
Refer to the exhibit.
A developer has configured an integration Procedure element with SEND/RESPONSETRANFORMATIONS as shown.
Alternatively, how could the developer configure Additional input to send exactly the same data? Assume that the developer checked Send Only Additional input.
- A.
- B.
- C.
Answer: C
Explanation:
Option C is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have a key/value pair for each field in Input Data, and the value should be set to
{{InputData.field}} for each field. This will pass the value of Input Data for each field to Additional input.
NEW QUESTION # 37
A developer writes an OmniScript that includes a DataRaptor that updates the Account status based on information provided from the OmniScript. The information must be updated only if the Account record already exists. Otherwise, a new account must be created.
How should the developer accomplish this task?
- A. Check the Upsert Key checkbox on the Account Status field
- B. Check Overwrite Target for All Null Inputs checkbox on the Account Id field
- C. Check the Upsert Key and Is Required for Upsert checkboxes on the Account Id field
- D. Populate the Lookup Object and Lookup Fields
Answer: C
Explanation:
The Upsert Key checkbox indicates that the field is used as a key for upserting records. The Is Required for Upsert checkbox indicates that the field is mandatory for upserting records. The developer needs to check both checkboxes on the Account Id field to update the Account status only if the Account record already exists. Otherwise, a new account will be created.
NEW QUESTION # 38
A developer needs to configure a DataRaptor to retrieve data from a single object. The structure of the output data does not need to be changed.
Following best practices, which type of DataRaptor should the developer use?
- A. DataRaptor Transform
- B. DataRaptor Extract
- C. DataRaptor Load
- D. DataRaptor Turbo Extract
Answer: D
Explanation:
A DataRaptor Turbo Extract is a simplified version of a DataRaptor Extract that can retrieve data from a single object without changing the structure of the output data. It is suitable for this scenario because the developer does not need to transform or load the data
NEW QUESTION # 39
The OmniScript must retrieve device details stored in the Asset object and then call an external system to send troubleshooting commands via REST API to the device.
Which two OmniScript element should the developer use to configure this functionality?
- A. HTTP Action
- B. DataRaptor Extract Action
- C. SOQL Action
- D. REST API Action
- E. Navigation Action
Answer: A,B
Explanation:
According to the OmniScript Action Elements page, a DataRaptor Extract Action can be used to "get data from one or more Salesforce records" and an HTTP Action can be used to "get, save, or delete data through a web application programming interface (API)".
NEW QUESTION # 40
A developer creates an Integration Procedure with a Set values and a DataRaptor Extract Action that requires Accountld as a key. When the developer previews the Integration Procedure, the developer enters the Accountld correctly and executes the preview. The developer sees the dataextracted by the DataRaptor in the Debug Log, but the response is empty.
What is the likely cause of this issue?
- A. The Accountld used for the preview is invalid.
- B. The DataRaptor Action did not have the Add Response To Response JSON property set to true.
- C. A Response Action was not added to the Integration Procedure.
- D. The Response cannot be previewed directly.
Answer: B
Explanation:
The Add Response To Response JSON property on the DataRaptor Action indicates that the output of the DataRaptor should be added to the response JSON of the Integration Procedure. If this property is not set to true, the response will be empty even if the DataRaptor extracts data successfully.
NEW QUESTION # 41
An integration procedure contains a Remote Action element that calls a method of an APEX class. The method requires two fields are input: Account id and Product Id. The integration Procedure data JSON contains the following nodes:
How should the Remote Action element be configured to pass the data correctly to the method?
- A. Check the Send Only Additional Input checkbox, and the following/ value pairs to Additional input:
- B. Check the DataRaptor Transform checkbox, and add the following Key/Value pairs to Output JSON Path:
- C. Set Return Only Additional Output to true, and add the following Key/Value pairs to additional input.
- D. Add the following to Send JSON Path: accountId: %Accountd% ProductId% Details Products%
Answer: A
Explanation:
Checking the Send Only Additional Input checkbox allows the Remote Action element to send only the key
/value pairs specified in Additional input to the Apex method. The Additional input should have the same keys as the method parameters, and the values should be set to {{InputData.node}} for each node. For example, AccountId: {{InputData.AccountId}} and ProductId: {{InputData.Details.Products}}.
NEW QUESTION # 42
A developer creates an OmniScript to update billing information. After analyzing the different types of customer interactions that occur at the company, the developer determines updating billing information should be included in the majority of customer interactions, which are represented by more than 20 different FlexCards.
What is the most efficient way for the developer to configure the action that invokes the OmniScript?
- A. As an OS Action
- B. As an OmniStudio Action
- C. As a Custom Action
- D. As a Lightning Action
Answer: A
Explanation:
An OS Action is the most efficient way to configure the action that invokes the OmniScript, as it allows the developer to reuse the same OmniScript across multiple FlexCards without creating separate actions for each one. A Custom Action is used to invoke a custom Apex class or Lightning web component. An OmniStudio Action is used to invoke an Integration Procedure or a Calculation Procedure. A Lightning Action is used to invoke a Lightning component or a Visualforce page.
NEW QUESTION # 43
A healthcare company wants to enable its subscribers to add, edit, or delete dependents related to their policy via their Community portal. The developer on the project decides to use an OmniScript.
How should the developer configure the OmniScript to provide this functionality?
- A. Use an Edit Block element configured with Remote Actions.
- B. Use an Input Block element and a Data Mapper Post Action element.
- C. Use an Edit Block element configured with SOQL statements.
- D. Use a Text Block element and a Remote Action element.
Answer: A
Explanation:
In OmniStudio, the Edit Block element is purpose-built for allowing users to dynamically add, edit, or delete rows of related data, such as dependents under a policy. To save these changes, Remote Actions (typically backed by Apex or API) are used to process each record operation (Create/Update/Delete).
* A. Use an Edit Block element configured with Remote Actions - Correct. This is the recommended and most scalable way to support CRUD operations in OmniScripts for collections (e.g., dependents).
The Edit Block provides UI-level support, while Remote Actions handle back-end interaction with Salesforce or external systems.
Incorrect Options:
* B. Text Block is for display purposes and cannot manage data input or backend actions.
* C. Input Block elements do not support row-level add/edit/delete functionality as Edit Blocks do.
* D. SOQL is a read-only query language and cannot be used to update or delete records directly within an OmniScript.
:
Salesforce OmniStudio Guide # OmniScript Edit Block Element
OmniStudio Best Practices # CRUD Operations in OmniScripts
NEW QUESTION # 44
A developer is configuring an Integration Procedure Action in an OmniScript. The OmniScript needs a JSON response from the Integration Procedure but does not need to wait for the response for the user to proceed.
Which feature should the developer enable?
- A. Invoke Mode Fire and Forget
- B. Use Future
- C. Toast Completion
- D. Invoke Mode Non-Blocking
Answer: A
Explanation:
In OmniStudio, the Invoke Mode: Fire and Forget setting allows an OmniScript to call an Integration Procedure asynchronously, meaning it does not wait for the response to complete before continuing user interaction.
* C. Invoke Mode Fire and Forget - This is the correct setting. It's designed specifically for use cases where the user experience should not be blocked by backend processing.
Incorrect Options:
* A. Use Future is not a valid OmniScript configuration option.
* B. Invoke Mode Non-Blocking is not an official setting in OmniStudio terminology.
* D. Toast Completion is a UI notification setting and does not impact execution behavior.
:
OmniStudio Developer Guide # Integration Procedure Actions in OmniScripts
NEW QUESTION # 45
......
Plat-Dev-210 Actual Questions Answers PDF 100% Cover Real Exam Questions: https://www.practicematerial.com/Plat-Dev-210-exam-materials.html
Plat-Dev-210 Exam questions and answers: https://drive.google.com/open?id=16EgBivMGTk1MsWX-AHlg3JwPjTpIbS3_
