Platform-App-Builder Exam Dumps - Salesforce Certified Platform App Builder (Plat-Admn-202)

The correct answer is D. Component visibility filter.

In Lightning App Builder, component visibility rules can control whether a component appears based on context, including the device/form factor. Salesforce Trailhead specifically describes creating a visibility rule so a component appears only when the page is viewed on a phone, which matches restricting a Lightning component to mobile users.

A is incorrect because form factor settings are generally used for page/device availability or preview behavior, not the best feature for hiding or showing one specific component on a single Lightning record page.

B and C are incorrect because the Highlights Panel and Related List Quick Links are page components, not conditional visibility tools.

===========

A Salesforce validation rule prevents a record from being saved when its formula evaluates to TRUE. The rule therefore must return TRUE when the Account is locked and the current user ' s profile is not System Administrator. $Profile.Name is the appropriate global variable for testing the current user ' s profile. Salesforce documents $Profile global merge fields for accessing profile properties, including $Profile.Name , and provides validation-rule examples using profile-name comparisons to exempt authorized profiles. Option A tests the user ' s role, but System Administrator is a profile, not a role. Option C introduces an unrelated Opportunity Stage condition. Option D reverses the logic and would block the System Administrator instead of exempting that profile. Therefore, B correctly implements the stated lock exception.

================

A criteria-based sharing rule can identify Project records according to the Department field and share matching records with the appropriate public group. Salesforce documents that criteria-based sharing rules determine which records are shared based on field values and can grant access to public groups. Administrators can therefore maintain departmental public-group membership as employees change roles. When an employee leaves one department, removing that user from its public group removes the sharing path to those departmental Projects after sharing recalculation. Permission sets and profiles control object and field permissions but are not targets for criteria-based record-sharing rules. Account Teams apply specifically to Account collaboration and are unrelated to a custom Project object. With Project OWD set to Private, public groups plus criteria-based sharing provide the required controlled departmental visibility.

================

The correct answer is B. Geolocation.

Salesforce geolocation fields are used to identify locations using latitude and longitude and can support distance calculations.

Because Universal Containers delivers containers to remote construction sites and customers provide crossroads or location markers, the app builder should use a Geolocation field to capture location-based information rather than a number, reference, or external lookup field.

Why others are incorrect:

A. Number stores numeric values only.

C. Reference is not the correct field type for capturing physical location.

D. External Lookup is used to relate Salesforce records to external object records, not to store site location details.

===========

The correct answer is D. Approval process.

The requirement is to automate travel request form submission and enforce an internal approval policy. Salesforce approval processes are specifically designed to automate how records are submitted, reviewed, approved, rejected, recalled, and acted upon. Salesforce Trailhead explains that an approval process defines the criteria a record must meet before submission, the approval steps, approvers, and the actions taken when the record is approved or rejected.

This exact scenario also aligns with Salesforce’s travel approval training example, where a Travel Approval object uses an approval process to route travel requests to the employee’s manager and, when needed, to another approver.

A is incorrect because assignment rules route leads or cases, not approval requests.

B is incorrect because validation rules prevent invalid saves but do not manage approval routing.

C is incorrect because Apex is unnecessary when a standard declarative approval process fits the requirement.

===========

A Screen Flow is Salesforce ' s interactive flow type and is specifically intended to guide users through a business process while collecting input. The app builder can create multiple Screen elements representing troubleshooting steps, display instructions and questions, store the representative ' s responses, and then use Create Records to generate the follow-up Case at the end of the process. Salesforce explicitly distinguishes Screen Flows from background automation because Screen Flows require user interaction and support screens, choices, and other interactive components. Schedule-triggered, record-triggered, and platform event-triggered flows execute automatically in the background and therefore do not provide the required multi-step wizard interface. The combination of guided navigation, data capture, and record creation makes Screen Flow the appropriate declarative solution.

================

Collection Sort is designed to reorder a collection and optionally reduce the number of records retained after sorting. Salesforce documents that the Collection Sort element can sort a record collection by a selected field in ascending or descending order and can specify the maximum number of items to keep afterward. The flow should therefore sort the Opportunity collection by Amount in descending order and retain only five records. A Collection Filter selects records based on Boolean-style criteria, but it does not identify the top N records based on ranking. A Decision controls execution paths rather than restructuring a collection. Transform maps data between structures but is not intended to rank and limit records. Collection Sort directly implements both requirements—highest Amount first and only five records retained.

================

A roll-up summary field requires a master-detail relationship. Since Galaxy__c and Star__c currently have a lookup relationship, the app builder cannot create a standard roll-up summary field to count related Star__c records. The lookup must be converted to master-detail first, with Galaxy__c as the master and Star__c as the detail. Salesforce Trailhead confirms that roll-up summary fields display values on the master record based on directly related detail records in a master-detail relationship.

===========