Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers

The correct answer is C. A delegated approver is the recommended Salesforce feature when the assigned approver is unavailable, such as during vacation. Salesforce documentation confirms that users can identify a delegate in approval settings, and delegated approvers can approve or reject approval requests.

This ensures the closed-won Opportunity can still be reviewed before the leaderboard is updated, even though the owner’s manager is away.

Why others are incorrect:

A is not the best recommended setup because relying on an assistant to reassign requests is manual and reactive.

B is incorrect because forwarding approval requests is not the standard solution for planned approver absence.

D is incorrect because assignment rules do not assign delegated approvers for approval processes.

===========

The correct answer is D. For use on the utility bar.

For a custom Lightning web component to appear as an available component in the utility bar, it must be exposed in its metadata configuration with the lightning__UtilityBar target. Salesforce developer documentation states that lightning__UtilityBar enables a component to be used as a utility item in an app’s utility bar, and the component must be exposed with the appropriate target.

B. For use in Lightning App Builder is broader and not enough by itself for utility-bar availability. C. For use on record pages exposes the component for record pages, not the utility bar. A. For use in App Manager is not the correct component target wording.

===========

The correct validation rule is:

AND(

ISNEW(),

ISBLANK(Lead.Owner:User.Id)

)

This rule prevents a new Campaign Member from being created when the related Lead does not have a User as owner. Leads can be owned by either a user or a queue, and Salesforce queues can own Lead records.

Salesforce validation rules block a save when the formula evaluates to True. The ISNEW() function checks whether the record is being created, and ISBLANK() checks whether the Lead owner’s User Id is empty.

For owner fields in cross-object formulas, Salesforce requires being explicit about the owner type, such as Owner:User or Owner:Queue .

Why not others:

A is wrong because Lead.Owner.Id is normally populated whether the owner is a user or queue.

B and D focus on queue ownership, but the best exam answer checks that the Lead has an actual User owner when the Campaign Member is created.

The correct bulk-safe Flow pattern is to modify each current Case with an Assignment element and add the modified record to a record collection variable. After the Loop finishes, one Update Records element should update the complete collection. Salesforce explicitly warns against putting Get Records, Create Records, Update Records, or Delete Records elements inside loops because repeated SOQL or DML operations can quickly exceed governor limits. Trailhead ' s recommended pattern is to retrieve records before the loop, use assignments while iterating, store changed records in a collection, and perform one database update after the loop. A Collection Filter does not replace the collection used to stage modified records. An Update Records element inside the loop defeats the stated requirement for one database operation. Therefore, Assignment plus a collection variable is the correct architecture.

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

The correct answers are A. Create a child record, C. Update a related record, and D. Send an email alert.

Process Builder was designed to automate repetitive business actions. Salesforce documentation describes Process Builder as a tool for automating tasks, emails, and record updates.

Process Builder can improve productivity by performing actions such as:

Create a child record — Process Builder can create a record when criteria are met.

Update a related record — Process Builder can update the record that started the process or related records.

Send an email alert — Salesforce documentation specifically states that a process can send an email by using an email alert.

B is incorrect because “Start an additional message” is not a standard Process Builder productivity capability.

E is incorrect because Process Builder does not delete related records as a standard declarative action.

===========

The correct answer is A. Record-triggered flow.

The app builder needs automation to run when a child record is deleted and then update a field on the related parent record. Salesforce states that a record-triggered flow can automatically perform actions when a record is created, updated, or deleted, without user interaction.

Autolaunched flow can perform logic, but it does not run automatically on record deletion unless invoked by another automation. Validation rule only prevents invalid data entry. Quick action requires user interaction and is not suitable for automatic updates after deletion.

===========

The required metric is the total monetary value of won Opportunities for each Account. Salesforce supports roll-up summary fields on Account that aggregate Opportunity Amount and apply filtering criteria so that only qualifying child records are included. The appropriate configuration therefore uses SUM on Opportunity Amount with a filter restricting the calculation to Opportunities whose Stage represents Closed Won. Option C would incorrectly include open and lost Opportunities. COUNT-based options calculate the number of records rather than total sales value, and the roll-up belongs on the Account because that is where the summarized result must appear. Salesforce ' s current documentation specifically gives the example of an Account roll-up displaying total Opportunity amount and filtering the aggregation to only won Opportunities.

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

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.

===========

The correct sandbox type is Partial Copy.

A Partial Copy sandbox is built for testing with a subset of production data. Salesforce lists Partial Copy sandboxes with 5 GB data storage and a 5-day refresh interval, which supports the requirement to refresh it every weekend.

Why the other options are wrong:

Developer and Developer Pro sandboxes are mainly for development and do not copy a produc tion data subset in the same way. A Full sandbox can copy all production data, but its refresh interval is longer and it is unnecessary for a subset under 5 GB.

===========

The correct answers are A. Enable Feed Tracking on Opportunities and D. Use a record-triggered flow on Opportunity and a Chatter post action.

Feed Tracking is the correct configuration to track field changes on the Opportunity record feed. Salesforce states that feed tracking detects changes to tracked record fields and posts updates to the feed for users who follow the record. Salesforce also allows admins to enable feed tracking for an object and select tracked fields.

A record-triggered flow with a Chatter post action handles the automatic notification requirement. The flow can detect when the Opportunity Close Date changes and post to Chatter, such as mentioning the sales manager or a manager group. Salesforce supports posting to a record’s Chatter feed through automation when feed tracking is enabled.

B is incorrect because an outbound message sends data to an external endpoint, not a manager notification on the Opportunity. C is incorrect because Historical Trending is mainly for reporting on changes over time, not automatic manager notification on the record.