Free Plat-Dev-210 sample questions

Correct answer: Create two distinct Card States within the same FlexCard, adding a condition to each state (e.g., Status = 'Active' vs Status = 'Lapsed').

While conditional view on elements works, the 'most efficient' and best-practice method for entirely different layouts or action sets based on data values is to use **Card States**. This keeps the canvas clean and allows for distinct UI arrangements and actions for each data scenario without cluttering a single state with hidden elements.

Correct answer: OmniStudio Data Mapper (DataRaptor)

OmniStudio Data Mappers (formerly DataRaptors) automatically respect Salesforce Field Level Security (FLS) and Sharing Rules. SOQL queries in FlexCards do not inherently enforce FLS on the fields returned unless explicitly checked in code, making Data Mapper the secure choice for declarative configuration.

Correct answer: Type Ahead Block configured with a Data Mapper Turbo Extract.

The Type Ahead Block is designed for this specific filtered search scenario. Pairing it with a **Data Mapper Turbo Extract** (formerly DataRaptor Turbo) provides the best performance because Turbo Extract is optimized for single-object queries with simple field retrieval, avoiding the overhead of standard extracts.

Correct answer: Use a Loop Block with a Try-Catch Block inside it. Configure the 'Failure Response' on the Try-Catch to return a partial error without failing the IP.

To process items individually and handle failures gracefully per item, you place the logic inside a **Loop Block**. Inside the loop, you wrap the risky action (API call) in a **Try-Catch Block**. This ensures that if the API throws an error for one iteration, the Catch block handles it, and the Loop continues to the next item.

Correct answer: In the Extract tab, defining filter conditions on the primary Account object step.

In a Data Mapper Extract, criteria for retrieving records are defined in the **Extract** tab. You add filter conditions (e.g., `Active__c = 'Yes'` and `CreatedDate >= LAST_N_DAYS:30`) directly on the object step that retrieves the Accounts.

Correct answer: Configure the 'Response Action' in the Integration Procedure to use the 'Send JSON Path' property to return ONLY the required fields.

The bottleneck is the data volume being transferred to the client browser. By configuring the **Response Action** in the Integration Procedure to prune the data (using `Send JSON Path` or `Additional Output`), you ensure only the necessary 5 fields are sent to the OmniScript, significantly reducing payload size and browser processing time.