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.
Salesforce 2026
At Universal Containers, the finance team requires every Expense_Report__c record to be approved first by
the employee ' s manager and then, if the total amount is greater than $5,000, by the Chief Financial Officer
(CFO). The team wants a single declarative process that routes the request to each approver in sequence,
tracks each response, and updates the Expense Report ' s Status field after final approval.
Which Salesforce feature should the Platform App Builder use?
A. A record-triggered flow with a Decision element that routes to different paths based on the Expense Report amount.
B. A validation rule on Expense_Report__c that blocks the save until a custom Approved_By__c field is populated.
C. A flow approval process with sequential approval steps for the manager and CFO.
D. A screen flow that prompts the manager and CFO to enter their decisions when launched from the Expense Report record page.
Explanation:
This question tests your knowledge of advanced approval routing and business process automation in Salesforce. When an organization requires multi-tiered reviews—such as an initial manager sign-off followed by an executive review conditional on a financial threshold—standard approval processes provide the native architecture to handle these workflows. They securely lock records during review, send automated email alerts, route requests sequentially, and execute automated field updates (like changing the Status field) upon final approval.
Correct Option:
Option C:
A flow approval process with sequential approval steps for the manager and CFO is the correct choice because it natively supports multi-step review chains. The first step routes the record to the employee's manager, while the second step can be configured with a conditional entry criteria (Total Amount > $5,000) to route the request to the CFO only when applicable. Furthermore, it automatically updates the Expense Report's Status field upon final approval and maintains full tracking history.
Incorrect options:
Option A:
Record-triggered flows with Decision elements are designed to automate background data updates and record modifications based on field changes. They do not provide the native interactive response tracking, audit history, secure record locking, or multi-step approval routing capabilities built into approval processes.
Option B:
Validation rules are strictly used to evaluate data upon save and block invalid record creation or updates. They cannot route review requests to different users, send approval emails, track sequential responses, or manage multi-tier business workflows.
Option D:
A screen flow that prompts users manually when launched lacks the automated routing, notification triggers, record locking, and formal audit trail required for compliance-driven corporate expense approvals.
Reference:
→ Refer to Approval Processes Overview on official Salesforce documentation, which explains how to configure sequential approval steps, entry criteria, and automated field updates.
A services manager wants to make sure the team enters case priority consistently.
Which feature should a Platform App Builder use to accomplish this?
A. In-App Guidance
B. Path
C. Flow
D. Next Best Action
Explanation
Path guides users through important stages of a record’s lifecycle and can display key fields and guidance for each stage. For Case Priority, it can help the team follow consistent data entry practices by showing relevant guidance while working with cases.
🟢 Correct Option: B. Path
Path provides a visual, step by step guide on a record page, helping users understand what information matters at each stage. For a support team entering case priority, the app builder can configure key fields and guidance to encourage consistent practices. Path improves visibility and helps users follow the expected process, although it does not independently enforce valid priority values.
🔴 Incorrect Options
🔴 A. In-App Guidance
In-App Guidance displays prompts and walkthroughs to help users learn Salesforce features and processes. It does not provide the record stage based guidance that Path offers for consistent case handling.
🔴 C. Flow
Flow automates business processes, collects information, and can update records. It could enforce or guide priority entry if designed for that purpose, but Path is the more direct feature for showing contextual guidance on a record page.
🔴 D. Next Best Action
Next Best Action recommends actions to users based on configured strategies. It is intended to suggest relevant actions, not provide stage based guidance for consistent Case Priority entry.
🔧 Reference
⇒ Salesforce Help: Path
Salesforce Help explains how Path displays key fields and guidance to help users work through record stages.
⇒ Salesforce Trailhead: Guide Users with Path
Salesforce Trailhead describes configuring Path to provide users with contextual guidance and key fields.
Universal Containers ' Human Resources application requires that when a new Employee record is created, a
welcome Task must be generated immediately. Additionally, if the onboarding status is still Pending five
days before the start date, a reminder email must be sent.
How should the Platform App Builder configure a single record-triggered flow to handle both timelines?
A. Build a schedule-triggered flow that runs every five days.
B. Add a Scheduled Path alongside the Run Immediately path.
C. Configure a Pause element within a Screen Flow.
D. Place an Asynchronous Path inside a Loop element.
Explanation:
This question tests the ability to handle two different timelines within a single record-triggered flow. When a new Employee record is created, a welcome Task must be generated immediately, and a reminder email must be sent five days before the start date if onboarding is still Pending. A record-triggered flow supports both needs through its Start element: the Run Immediately path executes synchronously when the record is created (for the Task), while a Scheduled Path can be added to run later, offset from a date field on the record (for the reminder) .
✔️ Correct Option:
B. Add a Scheduled Path alongside the Run Immediately path.
The Run Immediately path handles the immediate Task creation upon record creation. The Scheduled Path is configured with the Employee's Start Date as the Time Source and an offset of 5 Days Before, so it runs five days ahead of the start date . Entry conditions on the scheduled path can check that Onboarding Status is still Pending, ensuring the reminder only fires when appropriate . This single-flow design satisfies both timeline requirements without building separate automations.
❌ Incorrect options:
A. Build a schedule-triggered flow that runs every five days.
A schedule-triggered flow runs on a fixed clock schedule (e.g., every five days) and processes records in batches, not relative to each individual record's Start Date . It cannot generate a Task immediately upon Employee creation, failing the first requirement entirely.
C. Configure a Pause element within a Screen Flow.
Screen Flows require user interaction and are not triggered automatically by record creation. A Pause element pauses a running flow, but a Screen Flow must first be launched by a user, making it unsuitable for background automation on Employee creation. It also cannot generate the immediate Task without user initiation.
D. Place an Asynchronous Path inside a Loop element.
A Loop element iterates over a collection of records and cannot contain a Start-element path. Asynchronous Paths are configured on the Start element, not inside Loop elements. This option describes an invalid flow structure that cannot be built in Flow Builder.
🔧 Reference:
→ Trailhead: Add a Scheduled Task to Your Flow — Confirms Scheduled Paths run actions at a specified time offset from a record field, alongside the immediate path.
→ Salesforce Dictionary: Scheduled Action — Confirms a record-triggered flow can have an immediate path plus scheduled paths, each running in a separate asynchronous transaction.
Universal Containers ' global support team routes complex milestone approvals based on the region of the
submitting user. They need the flow to dynamically assign the approval task to a specific regional queue
instead of a statically hard-coded user ID.
How should the Platform App Builder store and reference the queue assignments inside the Flow Builder
logic?
A. Hard-code individual user profile IDs into a Screen element, then use a Get Records element.
B. Use a formula variable that evaluates the queue ' s DeveloperName , then use a Get Records element.
C. Launch an asynchronous path that ignores the record owner field.
D. Map the approval request to a custom text field on the Task object.
Explanation
This question tests how to assign work to a queue in a flow without hard-coding IDs. Record IDs differ between sandboxes and production, so a fixed ID can break after deployment. The Platform App Builder must derive the correct regional queue at run time and look up its ID in the flow.
✅ B. Use a formula variable that evaluates the queue’s DeveloperName, then use a Get Records element.
A formula can return the right queue DeveloperName based on the submitting user’s region. A Get Records element then queries the Group object, filtered by that DeveloperName and Type equal to Queue, and returns the queue ID. The flow assigns the approval task to that ID. DeveloperName stays consistent across environments, so nothing is hard-coded and region changes need little rework.
❌ A. Hard-code individual user profile IDs into a Screen element, then use a Get Records element.
Hard-coding IDs is exactly what the requirement avoids, and profile IDs identify profiles, not queues, so they cannot route a task to a regional queue. A Screen element is also meant for user interaction, not back-end routing, and fixed IDs break when the flow moves between orgs.
❌ C. Launch an asynchronous path that ignores the record owner field.
An asynchronous path controls when logic runs, not who receives the work. Ignoring the owner field does not identify a regional queue or return a queue ID. The flow would still lack a dynamic way to choose the correct queue by region, so the routing requirement would not be met.
❌ D. Map the approval request to a custom text field on the Task object.
A custom text field only stores text. It does not make the Task owned by a queue, and it does not look up the queue’s ID. Task assignment depends on the Owner field holding a valid queue ID, which still requires a lookup of the Group record.
🔧 Reference
🔗 Group – Salesforce Object Reference → confirms that queues are stored on the Group object, identified by the Queue type, and that DeveloperName is a unique name that can be used to find a queue.
A Platform App Builder at Cloud Kicks is creating a flow approval process for travel requests. The
requirement is to assign the approval to a specific user who will be determined at runtime based on other data
in the flow.
How must the app builder configure the approver for the approval step?
A. Use a Formula resource to define the approver directly in the Approver Type field.
B. Set the Approver Type to " User " and select a specific user from the list.
C. Set the Approver Type to " Resource " and select the text variable containing the username.
D. Set the Approver Type to " Queue " and assign the queue that contains the dynamic user.
Explanation:
This question tests the configuration of dynamic approvers in a Flow Approval Process when the approver's identity is determined at runtime rather than being hard-coded. The requirement is to assign the approval to a specific user whose username is calculated during the flow's execution based on other data. Salesforce provides the Resource assignee type specifically for this purpose, allowing a text variable to supply the approver's username dynamically at runtime.
✔️ Correct Option:
C. Set the Approver Type to " Resource " and select the text variable containing the username.
Salesforce documentation confirms that the Resource assignee type is designed for dynamic approval assignment. You create a Text variable that holds the username of the target approver, populate it during flow execution using an Assignment element, and then configure the approval step to use this variable as the Resource. This approach is also the only assignee model that supports deployment and packaging across orgs, unlike hard-coded User selections. The text variable must contain the exact Username string (e.g., approver@example.com), not a record ID.
❌ Incorrect options:
A. Use a Formula resource to define the approver directly in the Approver Type field.
There is no "Approver Type" field that accepts a Formula resource directly. The correct mechanism is the Resource assignee type paired with a Text variable, not a Formula resource. Formulas cannot serve as the assignee container in Flow Approval Processes.
B. Set the Approver Type to " User " and select a specific user from the list.
Selecting a specific user hard-codes the approver at design time. This fails the requirement that the approver be determined at runtime based on other flow data. Hard-coded User selections also cannot be deployed across orgs because user record IDs are not portable.
D. Set the Approver Type to " Queue " and assign the queue that contains the dynamic user.
A Queue is a static collection of users, not a mechanism for selecting a single dynamically determined user. Assigning to a Queue would route the approval to all members of that queue, not to the specific user identified at runtime. The requirement demands a single approver determined by flow data, which the Queue type cannot achieve.
🔧 Reference:
→ Salesforce Help: Simplify Flow Approval Processes with Easier Resource Assignment — Confirms the Resource assignee type uses a text variable containing the username at runtime.
→ Salesforce Help: Revenue Cloud Advanced Approvals: Cannot deploy or package Flow Orchestration with User, Group, or Queue assignee type — Confirms the text variable must hold the Username string, not a record ID, and that this is the supported pattern for dynamic assignment.
| Platform-App-Builder Exam Questions - Home |
| Page 2 out of 70 Pages |