Pass the Salesforce App Builder Platform-App-Builder Questions and answers with CertsForce

The Full sandbox is the appropriate environment for final User Acceptance Testing when realistic production-scale data is required. Salesforce describes a Full sandbox as a replica of the production organization containing metadata and production data and identifies it as suitable for testing, staging, load testing, and UAT. The app builder should therefore move the developed components from the Developer sandbox to the Full sandbox, allow sales operations users to validate the commission calculations against representative Opportunity data, and deploy to production only after successful testing. Conducting UAT directly in production creates unnecessary operational risk. A Developer sandbox contains metadata but does not automatically contain production data at the required scale. Therefore, D follows the proper Salesforce application lifecycle and testing model.

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

A schedule-triggered flow is appropriate when Salesforce must periodically identify records approaching a date and perform an automated action. Salesforce documents schedule-triggered flows as automation that runs at a specified time and frequency for batches of records. A daily scheduled flow can use Get Records to identify Contracts whose End Date is five days away, obtain the related Account information, and invoke Send Email for the Account owner. Salesforce provides the same architectural pattern for expiration reminders, where a daily schedule-triggered flow checks records and sends notifications a specified number of days before expiration. Screen Flow requires user interaction, while an autolaunched flow does not independently provide the required recurring schedule.

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

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

The correct answer is C. Configure Campaign Hierarchies and Campaign statistics.

To understand return on investment for an advertising buy, Universal Containers should use Salesforce Campaigns, especially Campaign Hierarchies and campaign reporting/statistics. Salesforce campaign hierarchy documentation explains that child campaign metrics roll up to the parent campaign, and Salesforce campaign reports can include campaign-hierarchy statistics for aggregate values.

The private security model does not require changing the whole org to public. The business need is marketing ROI tracking, so Campaigns are the correct feature.

A is incorrect because an opportunity pipeline report does not directly track advertising campaign ROI.

B is incorrect because Account Hierarchies and roll-up summaries are not the standard solution for campaign ROI.

D is incorrect because changing to a public security model is unnecessary and weakens data security.

===========

The correct answer is A. Create a lookup relationship on Asset Inventory to Asset. Add the Asset Inventory related list to the Asset page layout.

To show Asset Inventory records as a related list on Asset, the child object must contain the relationship field pointing to the parent object. In this scenario, Asset Inventory is the child/detail-style object, and Asset is the parent record where the related list should appear.

Salesforce relationship fields connect records between objects, and related lists can then be added to the parent object’s page layout. Salesforce documentation for related lists confirms that related lists are managed from the object’s page layout.

Why others are incorrect:

B is incorrect because a roll-up field does not create the relationship or related list.

C is incorrect because the relationship direction is wrong; the relationship field should be created on Asset Inventory, not on Asset.

D is incorrect because a junction object is only needed for many-to-many relationships. Here, Asset Inventory records simply need to relate to Asset records.

===========

Salesforce requires installation records to be directly associated with Opportunities, and sales reps need visibility of all installations tied to their Opportunities. A Master-Detail relationship is the correct solution because:

The Installation object (detail) inherits sharing and security from the Opportunity (master), ensuring sales reps see only their related installations.

Enables roll-up summaries on Opportunity if needed.

Salesforce documentation confirms that Master-Detail relationships provide parent-controlled ownership and access, making them ideal for enforcing related record visibility. (Salesforce Help)

B. Hierarchical is only available for User object.

C. Many-to-Many requires a junction object; not needed here.

D. Lookup allows optional, independent access; would not automatically enforce visibility.

===========

The validation rule must fire when two things are true:

Job_Accepted__c is already populated

Hire_Date__c is being changed

Salesforce’s ISCHANGED() function returns true when a field’s value changes from its previous value, and formula functions can be used in validation rules.

So this formula prevents users from changing the hire date after the candidate has accepted the offer:

NOT(ISBLANK(Job_Accepted__c)) & & ISCHANGED(Hire_Date__c)

Why others are incorrect:

The other options either use the wrong logical operator or validate the opposite condition. A validation rule must return TRUE only when Salesforce should block the save.

===========

A scheduled path on an after-save record-triggered flow is specifically intended to execute automation at a dynamically calculated time after an individual record-triggering event. The flow should trigger when Project__c.Status transitions to On Hold and schedule the email seven days after that update. Salesforce states that scheduled paths are available for record-triggered flows optimized for Actions and Related Records and can use “When Record Is Created or Updated” as their time source. Using CreatedDate would calculate the delay from record creation rather than when the project became On Hold. A daily schedule-triggered flow could poll records, but it is less precise and unnecessary when Salesforce can queue a per-record scheduled action directly. Thus, C matches the required independent seven-day timer.

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

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 C. App Manager.

To add components to the Utility Bar of an existing Lightning app, the app builder edits the app from Setup → App Manager, then uses the app’s Utility Items configuration. Salesforce Help specifically states that to edit or add a utility bar to an existing app, use App Manager and click Edit for the app.

Why others are incorrect:

A is close, but the entry point for editing an existing app’s utility bar is App Manager, not directly Lightning App Builder.

B is wrong because a Lightning Record Page is for record page layout/components, not app-level utility bar configuration.

D is wrong because App Menu is for launching apps, not configuring them.

===========