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
The Recruiting team at AW Computing captures the job acceptance and date of hire of A candidate on the Job Application custom object. Once the candidate accepts The recruiter ' s job offer, the date of hire should be entered and not be changed on Subsequent record edits. Which validation formula should the app builder use?
A. (ISBLANK (Job Accepted_c) || NOT (INCHANGED (Hi_Date_=))
B. NOT (LABLANK (Job hocepted_c)) FRISCHANGED (Hire_Date
C. NOT (ISBLANK (Job_Accepted_c)) 11 ISCHANGED (Hire_Date c)
D. (ISBLANK (Job_Accepted_c) NOT (ISCHANGED (Hire_Date_0})
Explanation:
The requirement is to allow the Hire Date to be entered when the job is accepted, but prevent any later changes to that date once the Job Accepted field has a value. A validation rule formula evaluates to true when an error should be shown. The correct formula checks two conditions together: the Job Accepted field is no longer blank, and the Hire Date field is being modified on the current save.
✅ Correct Option:
C. NOT (ISBLANK (Job_Accepted_c)) && ISCHANGED (Hire_Date__c)
This formula returns true (and blocks the save) only when both conditions are met: Job Accepted is populated and the user is attempting to change the Hire Date. It allows the Hire Date to be set for the first time when the offer is accepted, but locks the field against subsequent edits.
❌ Incorrect options:
A. (ISBLANK (Job Accepted_c) || NOT (ISCHANGED (Hire_Date__c)))
This formula is the logical opposite of what is needed. It would allow changes in many situations where the Hire Date should be locked and would not reliably prevent later edits.
B. NOT (ISBLANK (Job_Accepted_c)) || ISCHANGED (Hire_Date__c)
Using OR instead of AND means the rule fires too broadly. It would block saves even when the Hire Date is not being changed, creating unnecessary errors.
D. (ISBLANK (Job_Accepted_c) && NOT (ISCHANGED (Hire_Date__c)))
This combination does not protect the Hire Date after acceptance. It evaluates in ways that fail to stop unauthorized changes once Job Accepted is filled.
🔧 Reference:
→ Salesforce Help: ISCHANGED – Documents the ISCHANGED function used in validation rules to detect field modifications and prevent unwanted updates.
Due to the complexity of Universal Containers ' sandbox release schedule and requirements, its deployment
process requires that change sets are used to migrate from one environment to another.
Which item is a Platform App Builder able to move when using a change set?
A. Custom objects
B. Standard fields
C. Lightning page assignments
D. Users
Explanation:
Change sets migrate supported configuration metadata between connected Salesforce orgs, such as from a sandbox to production. Custom objects are explicitly listed as a directly selectable change-set component, whereas users are data records and cannot be deployed through a change set.
✔️ Correct Option:
A. Custom objects
Custom objects are org-specific configuration components created in Setup and are supported as direct components in an outbound change set. A Platform App Builder can add a custom object to a change set, include its dependent components such as custom fields, page layouts, and record types, and deploy it to another affiliated org. Salesforce documentation explicitly lists Custom Object among the component types that can be added to a change set.
❌ Incorrect Options:
B. Standard fields
Standard fields are part of Salesforce-provided standard objects and are not listed as directly selectable change-set components. While standard field permissions can be included through permission sets or profile settings, the standard field definition itself cannot be migrated as a standalone component.
C. Lightning page assignments
A Lightning page is a supported change-set component, but its assignment to an app, profile, or form factor is deployment configuration rather than a directly selectable component type. Salesforce’s supported-component list includes Lightning Page, not “Lightning page assignments.”
D. Users
Users are individual data records, and change sets do not contain data such as records. Change sets are intended to move org customizations and metadata, not to create or migrate user records between environments.
🔧 Reference:
→
Salesforce Help — Components Available in Change Sets
— Confirms that Custom Object is a directly selectable component type for change sets.
→
Salesforce Help — Change Sets
— Confirms that change sets move customizations and do not contain data such as user records.
An inventory management system outside Salesforce publishes a secure messaging notification whenever an item goes out of stock. The Platform App Builder needs to design a process in Salesforce that listens for this specific message payload and instantly creates a Task for the procurement team. Which flow type is designed to execute immediately upon receiving this external message structure?
A. Record-triggered flow
B. Autolaunched flow with no trigger
C. Screen flow
D. Platform event-triggered flow
Explanation
This question tests which flow type can listen for a message sent from an outside system and run as soon as it arrives. The inventory system publishes a notification with a defined payload, so Salesforce needs a flow that subscribes to that message structure. The question checks whether you can tell event driven automation apart from flows started by record changes, users, or other processes.
✅ D. Platform event-triggered flow
A platform event triggered flow subscribes to a specific platform event and launches whenever a matching message is received. The external inventory system can publish the out of stock message through the API, and the flow reads its values from the event record. It can then create a Task for the procurement team immediately, without a user or record change starting it.
❌ A. Record-triggered flow
A record triggered flow starts when a record is created, updated, or deleted in Salesforce. The external system sends a message, not a record change, so nothing would start this flow. It could only run if the message first created a record, which adds an unnecessary step and does not listen for the message directly.
❌ B. Autolaunched flow with no trigger
An autolaunched flow with no trigger does not start on its own. It must be called by another process, such as Apex, an API call, or another flow. It cannot subscribe to an external message, so it would not execute automatically and immediately when the inventory system publishes the notification.
❌ C. Screen flow
A screen flow needs a user to open and complete it through a screen, such as from a button, page, or tab. It is built for guided interaction, not for background automation. It cannot listen for an external message or run instantly without a person, so it does not suit the procurement notification.
Reference
🔗 Subscribe to Platform Event Messages with Flows - Salesforce Developer Documentation → confirms that a flow can launch automatically when a platform event message is received.
🔗 What Is a Platform Event-Triggered Flow? - Salesforce Admin Blog → confirms that messages published through APIs or other processes launch the flow, and that it can create a task.
At Universal Containers, a Platform App Builder is building a record-triggered flow on Opportunity. When a
new Opportunity is created, the flow must set the Stage field to a default value based on the related Account '
s Industry. The app builder wants the most efficient configuration.
Which flow configuration should the app builder use?
A. An after-save record-triggered flow with an Assignment element that sets the Opportunity Stage based on Record.Account.Industry .
B. A before-save record-triggered flow with an Assignment element that sets the Opportunity Stage based on Record.Account.Industry .
C. An after-save record-triggered flow with an Update Records element that sets the Opportunity ' s Stage based on the Account ' s Industry.
D. A before-save record-triggered flow with an Update Records element that sets the Opportunity ' s Stage based on the Account ' s Industry.
Explanation:
This question tests an app builder's understanding of record-triggered flow optimization and execution order in Salesforce. Specifically, it evaluates when to utilize fast field updates (before-save flows) versus actions and related records updates (after-save flows). When modifying the field values of the triggering record itself during creation or update, administrators must choose the most performant flow configuration that updates fields in memory before committing to the database.
Correct Option:
Option B: A before-save record-triggered flow with an Assignment element that sets the Opportunity Stage based on Record.Account.Industry .
Before-save record-triggered flows (Fast Field Updates) execute up to 10 times faster than after-save flows because they update values in memory right before the record is saved to the database. When updating fields on the triggering record itself—such as setting the Opportunity Stage based on the parent Account's Industry—using an Assignment element on $Record in a before-save flow is the most efficient method because it requires no extra database DML statements or Update Records elements.
Incorrect options:
Option A: An after-save record-triggered flow with an Assignment element that sets the Opportunity Stage based on Record.Account.Industry .
After-save flows run after the initial record save operation is committed to the database. Simply assigning a value to $Record using an Assignment element in an after-save flow will not persist the change to the database unless followed by an explicit update element, which creates unnecessary performance overhead.
Option C: An after-save record-triggered flow with an Update Records element that sets the Opportunity ' s Stage based on the Account ' s Industry.
Using an after-save flow with an Update Records element forces an extra database transaction and triggers secondary save events (such as re-evaluating validation rules and triggers). For updating the triggering record's own fields, this approach is significantly slower and less efficient than a before-save flow.
Option D: A before-save record-triggered flow with an Update Records element that sets the Opportunity ' s Stage based on the Account ' s Industry.
In a before-save flow, an Update Records element is not needed to modify fields on the triggering record. Using an Assignment element directly on $Record automatically applies field updates before the database write, making an explicit Update Records element redundant and inefficient.
Reference:
→ Salesforce Help - Record-Triggered Flow Optimization confirms that before-save flows with Assignment elements provide the most efficient performance for same-record field updates.
At Universal Containers, a Platform App Builder has built a record-triggered flow on Opportunity that
updates several related records when the Stage changes to Closed Won. The flow must also block the save
and show the user an inline error message on the Stage field when the related Account does not have a
Contract record. The error must surface in the Lightning UI exactly as a validation rule error would.
Which Flow Builder element should the app builder add?
A. Screen element that displays the error message before the save completes
B. Fault path leading to an Assignment element that sets an error message variable
C. Custom Error element with a configured error message and field-level placement on Stage
D. End element placed on the path where no Contract record is found so the flow stops processing
Explanation:
This question tests how a record-triggered flow can prevent a record from being saved and display an error directly on a specific field. The Custom Error element stops the flow transaction, rolls back its changes, and displays the configured message at the selected field or page level, similar to a validation rule error.
🟢 Correct Option: C. Custom Error element with a configured error message and field-level placement on Stage
The Custom Error element allows a record-triggered flow to stop a record save when a required condition is not met. It displays a configured error message directly on the specified field, such as Opportunity Stage, or at the top of the page. This behavior resembles a validation rule error and prevents the Opportunity from being saved when the related Account has no Contract record.
🔴 Incorrect Options:
A. Screen element that displays the error message before the save completes
Screen elements are not supported in record-triggered flows. They are used in Screen Flows to collect input or display information interactively. Therefore, a Screen element cannot provide the required inline error on the Opportunity Stage field during a record save.
B. Fault path leading to an Assignment element that sets an error message variable
An Assignment element can set variable values, but it cannot independently block a record save or display a validation-style inline error on a field. A Custom Error element is specifically designed to enforce this behavior in record-triggered flows.
D. End element placed on the path where no Contract record is found so the flow stops processing
An End element stops further flow execution but does not automatically prevent the triggering record from being saved. It also cannot display a custom inline error on the Stage field, so it does not satisfy the requirement.
🔧 Reference
⇒ Salesforce Help: Custom Error Element
Salesforce Help. Confirms that the Custom Error element can block a record change, roll back the transaction, and display an inline error on a specified field.
⇒ Salesforce Trailhead: Roll Back Changes After an Error
Salesforce Trailhead. Explains how Custom Error works in record-triggered flows to prevent changes and display custom error messages.
| Platform-App-Builder Exam Questions - Home | Previous |
| Page 10 out of 70 Pages |