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
Cloud Kicks wants to efficiently increase the company ' s adoption of Salesforce while simultaneously
moving away from its reliance on spreadsheets. A Platform App Builder is given a spreadsheet everyone is
sharing that needs to be added to Salesforce. The object with fields needs to be created and the data inserted
simultaneously.
Which tool should the app builder use?
A. Schema Builder
B. Data Loader
C. Lightning Object Creator
D. Import Wizard
Explanation
Lightning Object Creator allows users to create a custom Salesforce object, define its fields, and import spreadsheet data simultaneously. It converts spreadsheet columns into Salesforce fields and automatically creates records from the spreadsheet data. This makes it ideal for organizations moving from spreadsheets to Salesforce.
Correct Option
🟢 C. Lightning Object Creator
Lightning Object Creator is designed to simplify the transition from spreadsheets to Salesforce. Users can upload an Excel or CSV file, review the suggested object and field names, make necessary adjustments, and create the custom object along with its records in a single process.
Incorrect Options
🔴 A. Schema Builder
Schema Builder provides a visual interface for creating and modifying objects, fields, and relationships. However, it does not import spreadsheet data and create records simultaneously.
🔴 B. Data Loader
Data Loader is used to insert, update, upsert, delete, and export Salesforce records. It requires the target object and fields to exist before importing data.
🔴 D. Import Wizard
Data Import Wizard helps users import records into existing Salesforce objects. It does not create a new custom object and its fields from a spreadsheet during the same process.
Reference
Salesforce Help – Lightning Object Creator
Universal Containers has a requirement that an email notification needs to be sent to an Account owner
automatically 5 days before a related Contract ' s end date.
Which flow type and element combination should the Platform App Builder use?
A. Schedule-triggered flow with a Get Records element and a Send Email action
B. Record-triggered flow with a Send Email action, using a scheduled path
C. Screen flow with a Send Email action and a Date element
D. Autolaunched flow with a Wait element and a Send Email action
Explanation:
This question tests an app builder's capability to configure time-based automated workflows linked to specific record dates in Salesforce. When an action—such as sending an email notification—must occur dynamically relative to a date field on a record (e.g., 5 days before a Contract's end date), administrators should use scheduled paths within record-triggered flows. Scheduled paths allow processing to pause efficiently until the calculated timeframe, executing high-volume time-based actions automatically without needing manual intervention or complex schedule querying scripts.
Correct Option:
Option B: Record-triggered flow with a Send Email action, using a scheduled path
Record-triggered flows support scheduled paths, which allow actions to be dynamically scheduled based on a specific date or date/time field on the triggering record. By defining a scheduled path set to run 5 days before the Contract End Date, Salesforce automatically queues the path execution for that record. When the scheduled offset is reached, the flow resumes and executes the Send Email core action to notify the Account owner natively and efficiently.
Incorrect options:
Option A: Schedule-triggered flow with a Get Records element and a Send Email action
Schedule-triggered flows run on a fixed recurring schedule (such as daily) across specified record sets. While possible, using a daily batch flow with a Get Records element introduces unnecessary query overhead and complex date filter formulas compared to leveraging native, record-specific scheduled paths configured directly on Contract records.
Option C: Screen flow with a Send Email action and a Date element
Screen flows require user interaction via dynamic user interface screens. They cannot run automatically in the background to send scheduled, time-based email notifications relative to record date fields without explicit user invocation.
Option D: Autolaunched flow with a Wait element and a Send Email action
Autolaunched flows cannot trigger automatically from record events without another invoking process. While Wait elements exist in autolaunched flows, managing time-based record triggers is far more efficiently handled using standard scheduled paths directly within a record-triggered flow framework.
Reference:
→ Salesforce Help - Record-Triggered Flow Scheduled Paths confirms that scheduled paths run flow actions at specified offsets relative to record date fields.
Northern Trail Outfitters wants to initiate a daily backup of its Salesforce org.
Which tool should an app
builder recommend for this task?
A. Refresh full copy sandbox
B. Add/Change package
C. Data Export Service
D. Support expert
Explanation
Salesforce Data Export Service allows administrators to export org data for backup purposes. It supports scheduled exports, including weekly or monthly options depending on the org’s settings. For a daily backup requirement, the app builder should verify whether the org’s available export scheduling options meet the requirement.
🟢 Correct Option: C. Data Export Service
Data Export Service is a built in Salesforce tool for downloading org data as CSV files in a ZIP archive. Administrators can configure exports through Setup and use the exported files as backups for recovery or record keeping. However, standard Data Export Service scheduling may not support daily exports in every org, so a strict daily backup requirement may need an alternative supported backup solution.
🔴 Incorrect Options
🔴 A. Refresh full copy sandbox
A Full Copy sandbox is primarily used for testing and development with a copy of production data and configuration. Refreshing a sandbox is not a dedicated daily backup process.
🔴 B. Add/Change package
Packages are used to distribute and deploy Salesforce metadata and application components. They are not intended to create scheduled backups of an org’s business data.
🔴 D. Support expert
Salesforce Support can help resolve technical issues, but it is not a backup tool. Administrators should use an appropriate export or backup solution to meet the organization’s backup requirements.
🔧 Reference
⇒ Salesforce Help: Export Backup Data with Data Export Service
Salesforce Help explains how administrators can export org data and configure available export schedules.
An app builder at Universal Containers has been asked to add the Chatter feed to a custom object record page.
Which approach should the app builder use?
A. Add the standard related first component.
B. Add the Chatter feed component from the AppleChange.
C. Add the standard Chatter feed component.
D. Add a custom Chatter feed component.
Explanation:
This question tests the basic procedure for adding Chatter functionality to a Lightning record page. To display a Chatter feed on a custom object record page, the app builder uses Lightning App Builder and drags the standard Chatter Feed component onto the page layout. A prerequisite is that Feed Tracking must be enabled for the custom object; otherwise, the Chatter components will not appear in the component panel . Once enabled, the standard Chatter Feed component can be added directly without custom development.
✔️ Correct Option:
C. Add the standard Chatter feed component.
Salesforce provides a built-in Chatter Feed component in Lightning App Builder. After enabling Feed Tracking for the custom object in Setup, the component becomes available in the panel. The app builder drags it onto the record page, configures the feed type (e.g., record feed), saves, and activates the page . This is the standard, declarative approach for displaying Chatter posts and updates on a record page.
❌ Incorrect options:
A. Add the standard related first component.
This option appears to contain a typo ("related first" likely means "Related List"). A Related List component displays child records in a tabular format; it does not render Chatter posts, comments, or feed updates. It cannot fulfill the requirement to add the Chatter feed.
B. Add the Chatter feed component from the AppleChange.
"AppleChange" is not a valid Salesforce term—likely a typo or garbled text. Chatter components are not obtained from an AppExchange package; they are native components available directly in Lightning App Builder once Feed Tracking is enabled . No external installation is required.
D. Add a custom Chatter feed component.
Building a custom Chatter feed component is unnecessary and not the standard approach. Salesforce already provides a standard Chatter Feed component that requires no code. Creating a custom component would introduce development overhead and maintenance burden for functionality that is available out-of-the-box.
🔧 Reference:
→ Salesforce Help: Chatter Components Not Available in Lightning App Builder — Confirms the standard Chatter Feed component is added in Lightning App Builder after enabling Feed Tracking for the object.
→ Salesforce Help: Create a Lightning Record Page for Alerts — Demonstrates dragging the standard Chatter Feed component onto a record page in Lightning App Builder.
Universal Containers (UC) has several large customers that sell their products through dealers. UC identifies and works with a single individual at each customer and at each dealer. Separate bills are sent to each customer and each dealer. These details need to be stored in a format that clearly displays the business entities and their appropriate representatives. How should an app builder implement these requirements?
A. Create both customer and dealer as accounts, create account teams on each account and associate the dealer records with the parent account.
B. Create a single account record, add each rep as a contact and create a custom dealer object.
C. Create a single parent record, add each rep as a contact to the parent account and add each dealer as a child record.
D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.
Explanation
This question tests how to model business entities, their single representatives, and the relationship between customers and their dealers using standard objects. Each customer and each dealer is billed separately, so each needs its own record. The Platform App Builder must keep contacts tied to the right entity and show how dealers relate to customers.
✅ D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.
Accounts represent companies, so customers and dealers each get their own account, which supports separate billing. The single representative at each entity is added as a contact on that account. Setting the customer as the Parent Account on each dealer builds an account hierarchy that clearly shows how dealers relate to customers, using only standard features.
❌ A. Create both customer and dealer as accounts, create account teams on each account and associate the dealer records with the parent account.
Customers and dealers are correctly created as accounts, but account teams are made up of Salesforce users who work on the account, not the customer’s or dealer’s representatives. The representatives need to be stored as contacts. This option leaves the individuals at each business entity without a proper place in the data model.
❌ B. Create a single account record, add each rep as a contact and create a custom dealer object.
A single account cannot hold separate billing for each customer and each dealer, and it blurs the individual business entities. A custom dealer object also duplicates what accounts already do for companies, and it loses standard account functionality. This design does not clearly display each entity with its own representative.
❌ C. Create a single parent record, add each rep as a contact to the parent account and add each dealer as a child record.
Placing all representatives as contacts on one parent account does not link each rep to the correct business entity. Dealers as child records, rather than accounts, also lack their own billing and contact structure. The result mixes customers and dealers, so the entities and their representatives are not clearly displayed.
🔧 Reference
🔗 Understand Account and Contact Relationships – Salesforce Trailhead → confirms that accounts represent companies with their contacts as people, and that setting a Parent Account on related accounts lets Salesforce display an account hierarchy.
| Page 1 out of 70 Pages |