Last Updated On : 17-Nov-2026


Salesforce Certified Platform App Builder - Plat-Admn-202 Practice Test

Prepare with our free Salesforce Certified Platform App Builder - Plat-Admn-202 sample questions and pass with confidence. Our Platform-App-Builder practice test is designed to help you succeed on exam day.

349 Questions
Salesforce 2026

Cloud Kicks wants customer care agents to follow a guided, multi-step form directly on the Case record page to capture a product return. The form takes the agent through verifying the order, choosing a return reason, and confirming a refund method, collecting input at each step.

Which type of flow should the Platform App Builder use?

A. Record-triggered flow

B. Autolaunched flow

C. Screen flow

D. Schedule-triggered flow

C.   Screen flow

Explanation

This question tests which flow type suits a guided, multi-step process where a user enters information on each page. The agent works on the Case record page and moves through verification, return reason, and refund method one step at a time. The Platform App Builder must choose the flow type that can display screens and wait for user input.

✅ C. Screen flow
A screen flow uses Screen elements to show pages that collect input from the user. The flow pauses on each screen until the agent clicks Next, then continues down its path. It can also be embedded on a Lightning record page, so agents can verify the order, choose a return reason, and confirm a refund method without leaving the Case.

❌ A. Record-triggered flow
A record-triggered flow runs automatically in the background when a record is created, updated, or deleted. It has no screens and cannot pause to collect input from an agent. It suits behind-the-scenes automation, such as updating related records, but not a guided form where the agent enters data at each step.

❌ B. Autolaunched flow
An autolaunched flow runs without user interaction and is started by something else, such as another flow, Apex, or a process. It cannot display screens, so it cannot guide an agent through each step of the return. It suits reusable background logic, not a step-by-step form on the record page.

❌ D. Schedule-triggered flow
A schedule-triggered flow runs automatically at a set time and frequency, for example processing a batch of records each night. It has no user interface and does not wait for input. Because the agent needs an on-demand form during a live case, a scheduled flow does not fit.

🔧 Reference
🔗 Get Started with Screen Flows – Salesforce Trailhead → confirms that a screen flow with Screen elements collects user input, waits on each screen until the user continues, and can be embedded on a Lightning record page for support agents.

A Platform App Builder needs to create a flow that can be invoked by a custom Lightning Web Component. The app builder wants to create a variable that can accept an input parameter so that values can be passed from the component into the flow.

How should the app builder create this variable?

A. Use a global variable like $Record.

B. Inputs can be passed through the Constant resource type in Flow.

C. Define public properties in the component that can be referenced by the flow.

D. Create a Variable resource type in Flow with Available for Input checked.

D.   Create a Variable resource type in Flow with Available for Input checked.

Explanation:

The question tests how a custom Lightning Web Component passes values into an invocable Flow. The Flow must expose a variable as an input resource so the component can initialize it when starting the Flow interview.

✔️ Correct Option:

D. Create a Variable resource type in Flow with Available for Input checked.
✔️ In Flow Builder, create a Variable resource with the required data type, then select Available for Input. This makes the variable available at the start of the Flow interview. The Lightning Web Component can pass a value to it through the flow-input-variables attribute of lightning-flow. Salesforce states that variables passed from a component must allow input access; otherwise, the value is ignored.

❌ Incorrect Options:

A. Use a global variable like $Record.
❌ Global variables such as $Record are system-provided resources and cannot be created as custom input parameters. $Record is available in record-triggered Flows and provides context about the triggering record; it is not the mechanism for a custom LWC to pass arbitrary values into a Flow.

B. Inputs can be passed through the Constant resource type in Flow.
❌ A Constant stores a fixed value that does not change while the Flow runs. It is not designed to receive dynamic values from a Lightning Web Component at Flow start, and it cannot be configured as an input parameter for this purpose.

C. Define public properties in the component that can be referenced by the flow.
❌ Public properties in the LWC can hold values in the component, but the Flow cannot directly reference them. The component must explicitly pass those values into Flow input variables using flowInputVariables; therefore, the Flow-side requirement is still a Variable resource marked Available for Input.

🔧 Reference:
→ Salesforce Help — Create an Identity Resolution Ruleset
— Confirms that a variable marked Available for Input can be set when a Flow starts from a Lightning page or component.

→ Salesforce Developer Documentation — Set Flow Input Variables
— Confirms that a custom LWC passes values through flow-input-variables, and the target Flow variables must allow input access.

Cloud Kicks streams loyalty data from an external system into Data 360 as a Data Model Object (DMO). When a loyalty member ' s tier in that DMO changes to Diamond, the company wants Salesforce automation to run automatically in near real time. The trigger is a change to the DMO in Data 360, not a change to a Salesforce record.

Which type of flow should the Platform App Builder use?

A. Template-triggered prompt flow

B. Schedule-triggered flow

C. Data 360-triggered flow

D. Record-triggered flow

C.   Data 360-triggered flow

Explanation:

This question tests your knowledge of advanced automation capabilities leveraging external data sources integrated through Data 360. When core Salesforce automation needs to respond instantly to changes happening within external data model objects rather than traditional CRM records, standard record-triggered flows cannot be used. Salesforce provides specialized flow triggers designed specifically to listen for changes in external data model objects or calculated insights. Understanding these cross-platform integration triggers enables architects to orchestrate seamless, near-real-time business workflows across unified data ecosystems.

Correct Option:

Option C:
A Data 360-triggered flow is the exact automation tool designed to execute Salesforce processes when specific conditions are met within a Data Model Object (DMO). Because the loyalty data streams from an external system into Data 360 and updates a DMO rather than modifying a standard Salesforce object record, this flow type listens to those changes in near real time. It allows organizations to seamlessly bridge external data insights with core CRM actions without custom middleware.

Incorrect options:

Option A:
A template-triggered prompt flow is utilized to handle generative AI prompts and customize responses leveraging prompt builder frameworks. It is designed for conversational AI context and prompt template generation, not for processing external data model object stream updates or running logic based on customer loyalty tiers.

Option B:
A schedule-triggered flow runs at specified periodic intervals—such as daily or hourly—rather than responding instantly in near real time. Because the requirement demands that automation execute immediately when the external loyalty tier changes in the streaming data source, a scheduled batch approach is inappropriate.

Option D:
A record-triggered flow executes automatically when a standard or custom object record is created, updated, or deleted within the core Salesforce database. Since the loyalty updates originate externally and map directly into a Data 360 DMO rather than updating a native Salesforce CRM record, a standard record-triggered flow cannot detect or capture these external modifications.

Reference:
→ Refer to Trigger Flows with Data 360 Data on official Salesforce documentation, which explains how flows start when conditions are met in data model objects.

Cloud Kicks wants a visual representation to track delivery status.

Which component should a Platform App Builder recommend?

A. Related List

B. Path

C. Details

D. Related Record

B.   Path

Explanation:

The question tests Salesforce Lightning record page components used to visualize progress through a business process. The Path component displays the stages or steps of a process in a visual sequence, helping users track delivery status and understand the current stage and next steps.

🟢 Correct Option: B. Path
The Path component provides a visual representation of progress through defined stages, such as order processing, dispatch, shipment, and delivery. Cloud Kicks can configure a suitable picklist field to represent delivery stages and display them through Path on the relevant record page. Users can quickly identify the current status and view guidance for progressing to the next stage, improving visibility into the delivery process.

🔴 Incorrect Options:

A. Related List
A Related List displays records associated with the current record, such as related orders or delivery records. It helps users access related information but does not visually represent progress through delivery stages.

C. Details
The Details component displays record field information. Although it can show the current delivery status stored in a field, it does not provide a visual sequence of stages or progress indicators.

D. Related Record
The Related Record component displays information from a related record and can allow users to update supported fields. It does not provide a visual representation of progress through a delivery process.

🔧 Reference:
⇒ Salesforce Help: Path Settings
Salesforce Help explains how to configure Path to display stages, key fields, and guidance for users as they progress through a business process.

⇒ Salesforce Trailhead: Guide Users Through Your Business Processes with Path
Salesforce Trailhead demonstrates how Path visually guides users through stages and helps them track record progress.

Universal Containers wants to build a screen that gives the user the ability to edit all Order Line Items related to a specific Order. The user should also be able to add new Order Line Items.

Which screen component should the Platform App Builder use to achieve the requirements?

A. Section

B. Repeater

C. Data Table

D. Slider

B.   Repeater

Explanation:

This question tests the selection of the correct Screen Flow component for bulk editing and creating related records on a single screen. The requirement is to allow users to edit all existing Order Line Items for a specific Order and add new Order Line Items at the same time. The Repeater component is specifically designed for this scenario: it can display existing records and let users add new ones, all within one screen interface .

✔️ Correct Option:

B. Repeater
The Repeater component enables users to rapidly enter and update chunks of data on a single screen. It supports displaying a collection of existing records (prepopulated items) while also allowing users to click Add to create new instances of fields . Salesforce release notes confirm that the Repeater can now update existing record collections, not just create new ones, making it the exact fit for editing all Order Line Items while also adding new ones . The component outputs collections such as Added, All, Prepopulated, and Removed Items for downstream processing .

❌ Incorrect options:

A. Section
The Section component is a layout tool used to organize screen components into multiple columns. It has no capability to display a collection of records, edit them inline, or allow users to add new records dynamically. It only controls visual arrangement .

C. Data Table
While a Data Table can display a collection of records, its primary purpose is to show records for viewing or selection (e.g., choosing which records to relate). It does not natively support inline editing of multiple records or adding new records directly within the table on the same screen without additional custom logic . The standard Data Table component is not designed for the edit-and-add workflow described.

D. Slider
A Slider is an input component for selecting a numeric value within a range. It has no relationship to displaying, editing, or creating multiple records. It is entirely irrelevant to the requirement.

🔧 Reference:
→ Salesforce Help: Collect User Input to Modify a List of Records from a Screen — Confirms the Repeater component can update existing record collections and handle added items on a single screen.

→ Trailhead: Create and Update Records With a Repeater — Confirms the Repeater displays existing records and lets users add new ones on the same screen.

Platform-App-Builder Exam Questions - Home Previous
Page 4 out of 70 Pages