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

Universal Containers is excited to launch a new app. The company wants to increase the adoption rate and guide users through different walkthroughs and targeted prompts.

What should the Platform App Builder recommend?

A. Build a screen flow.

B. Use In-App Guidance.

C. Use Dynamic Actions.

D. Upgrade to Dynamic Forms.

B.   Use In-App Guidance.

Explanation:

This question tests your knowledge of native user engagement and onboarding features within Salesforce. When launching a new application, organizations often need to drive user adoption, introduce new features, and provide contextual help directly inside the workspace without custom code or complex integrations. Salesforce provides built-in tools that allow administrators to create interactive walkthroughs, single-prompt banners, and floating callouts targeted at specific user groups or pages. Understanding when to use native engagement features versus process automation or layout enhancements is key to optimizing the overall user experience.

Correct Option:

Option B:
Using In-App Guidance is the ideal recommendation for increasing app adoption and guiding users through targeted prompts and multi-step walkthroughs. It enables administrators to create single prompts or step-by-step walkthroughs directly on Lightning pages to highlight new features, deliver training, or provide contextual onboarding tips to targeted user audiences without requiring any custom development.

Incorrect options:

Option A:
Building a screen flow allows administrators to create guided business processes and data collection wizards. While screen flows can guide users through step-by-step data entry tasks, they are designed for business logic automation rather than non-intrusive UI adoption prompts or contextual feature walkthroughs across pages.

Option C:
Using Dynamic Actions allows administrators to dynamically display or hide action buttons on a record page based on defined criteria. While this simplifies the page header and improves efficiency, it does not provide interactive user walkthroughs, banners, or targeted adoption prompts.

Option D:
Upgrading to Dynamic Forms improves user experience by breaking up record details into individual fields and field sets on Lightning App Builder pages with visibility rules. However, it focuses strictly on record layout customization and field visibility, not on user onboarding prompts or walkthroughs.

Reference:
→ Refer to In-App Guidance Overview on official Salesforce documentation, which confirms how prompt banners and walkthroughs guide users through application features and boost platform adoption.

Universal Containers has a new custom object for Invoices that includes an Invoice Number field. Before the Invoice object can be used, invoices will be migrated from an external system while maintaining their current Invoice Number. After the migration, each new Invoice created in Salesforce must have a unique Invoice Number.

How should the Platform App Builder configure the Invoice Number field?

A. Create an Auto Number field and migrate the Invoices in Invoice Number order.

B. Create a Text field and mark it as a Unique External ID field.

C. Create a Text field for the original Invoice Number and an Auto Number field for the Salesforce Invoice Number.

D. Create a Text field, then change it to Auto Number after the migration.

B.   Create a Text field and mark it as a Unique External ID field.

Explanation:

The question tests how to preserve legacy invoice numbers during migration while ensuring that every future Salesforce-created invoice has a unique number. A Text field configured as Unique and External ID supports both requirements.

✔️ Correct Option:

B. Create a Text field and mark it as a Unique External ID field.
✔️ A Text field can store the existing Invoice Number values imported from the external system. Marking it Unique prevents duplicate Invoice Numbers after migration, including for invoices created later in Salesforce. Marking it External ID also identifies it as the record identifier from the legacy system and enables matching during imports or upserts. This single field preserves the migrated values and enforces uniqueness going forward.

❌ Incorrect Options:

A. Create an Auto Number field and migrate the Invoices in Invoice Number order.
❌ An Auto Number field is system-generated and read-only, so Salesforce cannot directly load the existing Invoice Number values into it during migration. Migrating records in a particular order does not preserve the original external invoice numbers or guarantee that future Salesforce numbering matches the legacy numbering sequence.

C. Create a Text field for the original Invoice Number and an Auto Number field for the Salesforce Invoice Number.
❌ This creates two separate invoice-number values: the legacy number and a Salesforce-generated number. It preserves the original value, but it does not ensure that the same Invoice Number field is unique for all new invoices. The requirement is for each new Salesforce invoice to have a unique Invoice Number, not a second numbering system.

D. Create a Text field, then change it to Auto Number after the migration.
❌ Although a Text field can be changed to Auto Number, the conversion does not preserve the migrated values as editable Auto Number values. Existing records retain their text values, while Auto Number applies only to new records; this creates inconsistent data and does not reliably enforce uniqueness across all records.

🔧 Reference:
→ Salesforce Help — Custom Field Attributes
— Confirms that an External ID field stores identifiers from an external system and that marking it Unique prevents duplicate values.

→ Salesforce Help — Differences between the 'External ID' field and the 'Unique ID' field setting
— Confirms that External ID supports external-system matching and that Unique enforces value uniqueness.

An app builder wants to create a formula field on an Account to include data from related Contacts but is unable to find the relationship in the formula editor.
What is a limitation of formulas that could be causing the issue?

A. Control and Account objects: 0.00 or 1 have a Master-Detail Relationship.

B. Store Data: 3000 characters in the formula.

C. Formula field that reached on the Account object.

D. unable to reference the child records.

D.   unable to reference the child records.

Explanation:

Salesforce formula fields can reference fields on related parent records through supported relationship paths. However, they cannot directly reference fields from related child records, such as Contacts related to an Account. This limitation explains why the Contact relationship is unavailable in the Account formula editor.

🟢 Correct Option: D. Unable to reference the child records.
Formula fields support cross object references to parent records, allowing an Account formula to retrieve supported fields from a related parent. However, Contacts are child records of Account in a standard relationship, and a formula on Account cannot directly access individual child Contact fields. To use child record data, consider alternatives such as roll up summary fields where supported, record triggered flows, or other automation that stores the required value on Account.

🔴 Incorrect Options:

A. Control and Account objects: 0.00 or 1 have a Master-Detail Relationship.
This option does not describe the relevant limitation. Salesforce supports multiple relationship types, and the issue is not whether the objects have a master detail relationship. The limitation is that formula fields cannot directly reference child records.

B. Store Data: 3000 characters in the formula.
The formula field character limit concerns the amount of text a formula can return, not whether a related child relationship appears in the formula editor. It does not explain why Contact fields cannot be referenced from Account.

C. Formula field that reached on the Account object.
The option is unclear and does not identify a recognized Salesforce formula limitation. Formula fields on Account can reference supported parent fields, but they cannot directly retrieve fields from related child Contact records.

🔧 Reference:
⇒ Salesforce Help: What Is a Cross-Object Formula?
Salesforce Help explains how formulas reference fields on related parent objects and the limitations of cross object formulas.

Universal Containers has a custom object called Project__c and a custom object called Time_Entry__c . A Time Entry must always be associated with a Project. However, the organization-wide default (OWD) sharing setting for Project__c is Public Read/Write, while Time_Entry__c records contain sensitive data and must be strictly Private to the user who created them.

Which relationship type should the Platform App Builder use to relate Time_Entry__c to Project__c ?

A. Lookup relationship

B. Hierarchical relationship

C. External lookup relationship

D. Master-detail relationship

A.   Lookup relationship

Explanation:

This question tests the understanding of how relationship types affect record sharing and ownership. A Time Entry must always be linked to a Project, but the two objects have conflicting sharing requirements: Project is Public Read/Write, while Time Entry must be strictly Private to its creator. The key concept is that a Master-Detail relationship forces the child record to inherit the parent's sharing and ownership, whereas a Lookup relationship allows the child object to maintain its own independent sharing settings.

✔️ Correct Option:

A. Lookup relationship
A Lookup relationship creates a loose association between Time_Entry__c and Project__c without enforcing sharing inheritance. Because Time_Entry__c requires its own strict Private OWD—so only the creator can see their records—a Lookup is the only relationship type that preserves this independence. The requirement that every Time Entry must have a Project can be enforced by marking the lookup field as Required on the page layout or via validation, without adopting Master-Detail's sharing control.

❌ Incorrect options:

B. Hierarchical relationship
A Hierarchical relationship is a special lookup only available for the User object, used to link a user to their manager. It cannot be used between custom objects like Time_Entry__c and Project__c, making it irrelevant to this scenario.

C. External lookup relationship
An External lookup relationship links a custom object to an external object (via Salesforce Connect), not to another standard or custom object within Salesforce. It does not apply to relating two internal custom objects like Project__c and Time_Entry__c.

D. Master-detail relationship
A Master-Detail relationship makes the child record's sharing and ownership controlled by the parent. Since Project__c is Public Read/Write, Time_Entry__c records would inherit that broad access, violating the requirement that Time Entries remain strictly Private to their creator. The sharing dependency cannot be overridden while using Master-Detail.

🔧 Reference:
→ Salesforce Help: Considerations for Object Relationships — Confirms Master-Detail children inherit the parent's sharing and ownership, while Lookup relationships allow independent sharing settings.

→ Trailhead: Data Modeling – Relationship Types — Explains that Lookup relationships do not affect record ownership or sharing, unlike Master-Detail.

Universal Containers (UC) is integrating Salesforce with an external data warehouse. UC wants to make sure that any user who has the Integration User permission set has Read access to all the fields on the Account object, including any new fields that are created, without updating permissions again in the future.

What should the Platform App Builder recommend?

A. Grant View All Data in System Permissions.

B. Change Account Object Permissions by using View All Records.

C. Create a permission set group.

D. Assign View All Fields in Account Object Permissions.

D.   Assign View All Fields in Account Object Permissions.

Explanation:

The requirement is to give users who hold the Integration User permission set Read access to every field on the Account object—including any fields created later—without needing to update permissions again. Traditional field-level security requires manual updates for new fields. Salesforce provides the object-level “View All Fields” permission precisely for this scenario: it grants visibility to all current and future fields on the chosen object when assigned through a permission set.

✅ Correct Option:

D. Assign View All Fields in Account Object Permissions.
Enabling View All Fields on the Account object inside the Integration User permission set automatically grants Read access to every existing Account field and to any new fields added later. No further permission maintenance is required. This permission is scoped to the object, respects the need for at least Read object access, and is the supported way to achieve permanent, broad field visibility for integration users.

❌ Incorrect options:

A. Grant View All Data in System Permissions.
View All Data is a powerful system-level permission that exposes all data across the entire organization. It far exceeds the stated need for Account fields only and does not specifically solve the future-field problem in a targeted way.

B. Change Account Object Permissions by using View All Records.
View All Records controls record-level visibility (overriding sharing) but does not grant access to fields. Field-level security still applies, so new fields would remain inaccessible without additional configuration.

C. Create a permission set group.
A permission set group simply combines multiple permission sets for easier assignment. It does not itself grant field access or solve the requirement for automatic inclusion of future fields.

🔧 Reference:
→ Salesforce Help: “View All” and “Modify All” Permissions Overview – Confirms View All Fields grants access to all fields (including future ones) on a specific object.

→ Salesforce Help: Delivered Idea – Allow Users to View All Fields for a Specified Object – States users are automatically granted access for any new fields created on the object.

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