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

An app builder is loading data into Salesforce. To link the new records back to the legacy system, a field will be used to track the legacy ID on the Account object. For future data loads this ID will be used when upsetting records. Which two field attributes should be selected? Choose 2 answers

A. Required

B. Turn (encrypted)

C. Unique

D. External ID

C.   Unique
D.   External ID

Explanation:

This question tests how Salesforce identifies existing records during data imports and upserts. A legacy identifier should be stored in a field that Salesforce can use to match incoming records with existing records. Selecting External ID enables matching by the legacy identifier, while Unique prevents duplicate identifier values.

🟒 Correct Option: C. Unique
The Unique attribute prevents the same legacy ID from being assigned to multiple Account records. This helps maintain data integrity and avoids ambiguity when matching imported records. When Salesforce processes future data loads, each legacy identifier can consistently identify the intended Account. Although the Unique attribute does not itself enable external ID matching for upserts, it complements the External ID attribute by enforcing distinct values.

🟒 Correct Option: D. External ID
The External ID attribute allows Salesforce to use the legacy system's identifier to match incoming records with existing Account records during an upsert. If a matching record exists, Salesforce updates it; otherwise, Salesforce inserts a new record. This avoids relying on Salesforce generated record IDs and simplifies recurring data imports. Combining External ID with Unique ensures the legacy identifier can be used for matching without duplicate field values.

πŸ”΄ Incorrect Option: A. Required
The Required attribute forces users or data imports to provide a value for the field. However, it does not enable Salesforce to match incoming records using the legacy ID during an upsert, nor does it prevent duplicate values by itself.

πŸ”΄ Incorrect Option: B. Turn (encrypted)
Field encryption protects sensitive data by encrypting its stored value. It does not provide the record matching functionality needed for upserts or enforce uniqueness. Encryption is not necessary simply because a field stores a legacy identifier.

πŸ”§ Reference
β‡’ Salesforce Help: Custom Field Attributes
Confirms how External ID supports upsert matching and Unique prevents duplicate field values.

β‡’ Salesforce Help: Insert, Update, or Delete Data Using Data Loader
Explains how upsert matches existing records using an External ID or Salesforce record ID.

Cloud Kicks has created a custom object called Interests which is joined to Accounts by way of a junction object called Account Interest. What is the impact to users attempting to view an Account and the associated Account Interest records if they are without read access to the Interest object?

A. Users will be able to view the Account Interest records and will have read-only access to the Interest Records.

B. Users will be unable to view Account records that have a related Account Interest recor

C. Users will be unable to view the Account Interest records or the Interest records.

D. Users will be able to view the Account Interest record, but unable to view the field or any Information relating to the Interest recor

C.   Users will be unable to view the Account Interest records or the Interest records.

Explanation:

This question tests how record access flows through a junction object built with two master-detail relationships. In Salesforce, a junction record is only visible when the user has at least Read access to both parent records it links. Here, Account Interest joins Account and Interests, so missing Read access on Interests blocks visibility of the junction record itselfβ€”and, by extension, the related Interest information. The Account record may still open, but the junction and its Interest-side details will not be accessible.

βœ”οΈ Correct Option:

C. Users will be unable to view the Account Interest records or the Interest records.
A junction object with two master-detail relationships inherits access from both parents, and the most restrictive access wins. If the user lacks Read access on Interests, the Account Interest junction record cannot be displayed, even when the Account side is accessible. Without the junction record, the user also cannot see the Interest records through that relationship. This matches the standard Salesforce junction-object sharing behavior.

❌ Incorrect options:

A. Users will be able to view the Account Interest records and will have read-only access to the Interest Records.
This is wrong because missing Read access on Interests does not magically downgrade to read-only access on Interest records. Salesforce requires access to both master records before a junction record is visible. The user cannot view the junction record simply because the Account side is visible.

B. Users will be unable to view Account records that have a related Account Interest record.
This overstates the restriction. The Account record is the parent on one side of the junction, and the user's Account access is evaluated separately. Lacking access to Interests does not automatically hide the Account record itself. The limitation applies to the junction record and the Interest-side data, not the entire Account.

D. Users will be able to view the Account Interest record, but unable to view the field or any Information relating to the Interest record.
This is incorrect because the junction record cannot be viewed at all when the user lacks Read access to one of the two master records. Salesforce does not partially display the junction record while hiding only the Interest-related fields. Access to the junction record is blocked outright.

πŸ”§ Reference:
β†’ Salesforce Help: Custom Object Security Overview β€” Confirms that junction object access requires access to both master records and that the most restrictive sharing setting applies.

β†’ Trailhead: Data Modeling and Management β€” Covers relationship types and their impact on record access, including junction-object behavior.

A Platform App Builder would like to simplify the user experience with customized, intuitive record pages that change based on field input.

What should the app builder consider?

A. Create multiple Page Layouts dependent on the user.

B. Save a Filtered Related List for users to update records.

C. Leverage Screen Flows for user input.

D. Migrate to Dynamic Forms and create visibility rules.

D.   Migrate to Dynamic Forms and create visibility rules.

Explanation:

The question tests how to create record pages that adapt dynamically based on field values to improve usability. Traditional page layouts are static and assigned by profile or record type. Dynamic Forms let admins break the Record Detail component into individual Field and Field Section components in the Lightning App Builder. Visibility rules can then show or hide those components based on the values of other fields on the record, delivering a context-aware, simplified experience without needing multiple layouts.

βœ… Correct Option:

D. Migrate to Dynamic Forms and create visibility rules.
Dynamic Forms move fields and sections from the page layout into configurable components on the Lightning record page. Visibility rules can then be applied so fields or entire sections appear or disappear based on the value of another field (or other criteria such as user or device). This directly supports record pages that change based on field input, reduces the need for multiple page layouts, and gives users a cleaner, more intuitive interface focused only on relevant information.

❌ Incorrect options:

A. Create multiple Page Layouts dependent on the user.
Page layouts are assigned statically by profile, permission set, or record type. They do not change dynamically based on the value of a field the user enters on the record itself. Multiple layouts increase maintenance overhead and cannot deliver the field-value-driven behavior described in the requirement.

B. Save a Filtered Related List for users to update records.
Filtered Related Lists control which related records appear in a list view based on filter criteria. They do not affect the main record detail fields or allow the overall page layout to change based on field input. This option addresses list visibility, not dynamic record page customization.

C. Leverage Screen Flows for user input.
Screen Flows guide users through multi-step data collection or processes. While useful for structured input, they do not transform the existing record page into a dynamic layout that shows or hides fields based on values already present on the record. Flows operate outside the standard record page experience.

πŸ”§ Reference:
β†’ Salesforce Help: Break Up Your Record Details with Dynamic Forms – Confirms Dynamic Forms enable placement of fields/sections with visibility rules based on record data so users see only relevant content.

A Platform App Builder is asked to make a custom, standalone Lightning component accessible to sales reps. The component should be accessed directly from the navigation bar of the custom " Sales Operations " Lightning App. What is the best approach to achieve this?

A. Add the Lightning component to the Utility Bar of the Lightning App.

B. Embed the Lightning component into a dashboard and add the dashboard to the navigation menu.

C. Create a Web Tab and point the URL to the Lightning component ' s generated endpoint.

D. Create a Lightning Component tab and add that tab to the Lightning App ' s navigation menu.

D.   Create a Lightning Component tab and add that tab to the Lightning App ' s navigation menu.

Explanation:

A  Lightning Component tab is the standard and best approach to make a custom, standalone Lightning component accessible directly from the navigation bar of a Lightning app. By creating a tab for the component and adding it to the navigation menu of the "Sales Operations" Lightning App, users can access the component with a single click from the navigation bar. This provides a seamless, native Salesforce experience and is the recommended method for exposing standalone Lightning components to users.

❌ Why Other Options Are Incorrect

A. Add the Lightning component to the Utility Bar of the Lightning App – This is incorrect because the Utility Bar is a persistent toolbar at the bottom of the screen designed for frequently used tools such as quick actions, notes, and recent items. It is not the appropriate place for a standalone, full-page component that should be accessed from the navigation bar. The Utility Bar is better suited for compact, always-available utilities rather than primary navigation.

B. Embed the Lightning component into a dashboard and add the dashboard to the navigation menu – This is incorrect because dashboards are designed primarily to display reports and charts, not to provide standalone access to Lightning components. Although a Lightning component can be added to a dashboard in supported contexts, this is a workaround and restricts the component to the dashboard context. A Lightning Component tab is the direct solution for navigation-bar access.

C. Create a Web Tab and point the URL to the Lightning component's generated endpoint – This is incorrect because Web Tabs are intended to display external web content within Salesforce, not to expose internal Lightning components. Using a generated endpoint would add unnecessary complexity and is not the standard Salesforce approach. A Lightning Component tab provides direct and native access to the standalone component from the app navigation menu.

πŸ“š References

Salesforce Help – Lightning Component Tabs – Explains that Lightning Component tabs allow custom Lightning components to be added to an app's navigation menu, making them directly accessible to users.

At Universal Containers, two record-triggered flows run after an Opportunity is updated. One calculates a custom discount amount, and the other sends an email notification that references the calculated discount. The Platform App Builder must guarantee that the discount-calculation flow runs before the notification flow, while keeping the two flows separate for ownership reasons. How should the app builder meet this requirement?

A. Configure the notification flow to run asynchronously after the save so it executes after other recordtriggered flows on Opportunity.

B. Add a scheduled path with a zero-minute interval at the start of the notification flow to delay its execution.

C. Move both flows ' logic into a single before-save record-triggered flow on Opportunity to control execution order natively.

D. Set the trigger order in Flow Trigger Explorer for each flow so the discount-calculation flow has a lower trigger order value than the notification flow.

D.   Set the trigger order in Flow Trigger Explorer for each flow so the discount-calculation flow has a lower trigger order value than the notification flow.

Explanation:

The  Flow Trigger Explorer is specifically designed to manage the execution order of multiple record-triggered flows on the same object. By assigning a  lower trigger order value to the discount-calculation flow and a  higher trigger order value to the notification flow, the App Builder can ensure that the discount flow runs first, followed by the notification flow that references the calculated discount. This allows the flows to remain separate for ownership and maintenance while controlling their execution order.

❌ Why Other Options Are Incorrect

A. Configure the notification flow to run asynchronously after the save so it executes after other record-triggered flows on Opportunity – This is incorrect because asynchronous execution does not guarantee that the discount flow runs first. It runs the notification logic in a separate transaction after the original save transaction, but it is not the mechanism used to explicitly control the order of multiple record-triggered flows.  Flow Trigger Explorer provides the appropriate trigger-order configuration.

B. Add a scheduled path with a zero-minute interval at the start of the notification flow to delay its execution – This is incorrect because a scheduled path is not the appropriate mechanism for controlling the order of two record-triggered flows. A scheduled path introduces time-based execution rather than establishing a guaranteed trigger order. The requirement is to control which flow runs first, which is handled directly through  Flow Trigger Explorer.

C. Move both flows' logic into a single before-save record-triggered flow on Opportunity to control execution order natively – This is incorrect because the requirement explicitly states that the two flows must remain  separate for ownership reasons. Combining them into one flow would violate that requirement. In addition, before-save flows are intended primarily for updating fields on the triggering record and are not the appropriate place for sending email notifications.

πŸ“š References

* Salesforce Help – Flow Trigger Explorer – Explains how Flow Trigger Explorer allows administrators to view and set the execution order, or trigger order, for multiple record-triggered flows on the same object.

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