Get Salesforce Plat-Dev-210 Exam Practice Questions - Real and Updated

Answer : B, C

This scenario relates to FlexCard preview behavior and data mapping issues.

B . There is no Salesforce record for the FlexCard based on the RecordId in the layout's Test Data Source Settings -- If the test record does not exist, the FlexCard will not display any data during preview. This is a common setup mistake.

C . The Data Node field for the FlexCard is empty -- The Data Node field must be set correctly to match the JSON node where the expected data resides. If it is empty or incorrect, the FlexCard won't bind data to UI elements.

Incorrect Options:

A . Even if the RecordId is from a different record type, as long as the data structure aligns, it would still render; it's not a definitive reason for the card failing to display.

D . Attributes are not required to display field values directly; they are used for passing data between cards or from context, not for direct field rendering.

:

Salesforce OmniStudio FlexCard Data Source Setup & Troubleshooting

Answer : B

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.

Answer : D

The correct answer is D. Data Mapper Turbo Extract, based on best practices in the official OmniStudio documentation.

From the OmniStudio Developer Guide DataRaptors Turbo Extract:

DataRaptor Turbo Extract is a lightweight, high-performance extract designed specifically for retrieving data from a single Salesforce object, where no data transformation or complex joins are required.

It is recommended over DataRaptor Extract for performance reasons when only one object and minimal transformation is needed.

Why not the others?

A . DataRaptor Load is used for writing data to Salesforce, not retrieving.

B . DataRaptor Transform is used when you need to transform data, not simply extract it.

C . DataRaptor Extract can be used, but Turbo Extract is preferred for the use case of single object, no transformation --- per best practices.

:

Salesforce OmniStudio Developer Guide DataRaptor Turbo Extract Best Practices

OmniStudio Certification Study Guide 'When to use Turbo Extract'

Answer : A, D

An OmniScript and a Child FlexCard are both valid components that can be embedded in a flyout. An Integration Procedure and a DataRaptor are not components, but actions that can be performed within an OmniScript or a FlexCard.

Answer : A

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.