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

The correct answers are B. Apex and C. AppExchange.

Cloud Kicks needs to count related Case records on Account based on open and closed status. Standard roll-up summary fields work only in supported roll-up relationships, mainly master-detail relationships. Salesforce documentation states that lookup relationships do not support roll-up summary fields.

Because Cases are related to Accounts through a lookup-style relationship, native roll-up summary fields are not the best available option in this answer set. The app builder can meet the requirement by using:

Apex — Apex triggers can run before or after record changes such as insert, update, or delete, allowing custom logic to recalculate the open and closed Case counts on the Account.

AppExchange — AppExchange roll-up tools, such as lookup roll-up packages, can summarize records across lookup relationships without building custom code.

Why others are incorrect:

Validation Rule prevents invalid data entry; it does not calculate related record counts.

Approval Process routes records for approval; it does not summarize Case counts.

===========

The correct answer is D.

Universal Containers wants the Account Region value to appear on related Contact records and stay in sync whenever the Account value changes. A cross-object formula field on Contact is the best declarative solution because it dynamically references the parent Account field. Salesforce Trailhead explains that a cross-object formula can pull information from a parent object through a lookup relationship, such as showing Account information on Contact.

Because Account Region is a picklist, the formula must convert the picklist value to text using the TEXT() function. Trailhead gives the same pattern with Account Industry on Contact: TEXT(Account.Industry) .

B is incorrect because ISPICKVAL() checks whether a picklist equals a specific text value and returns true/false; it does not display the picklist value.

A and C are incorrect because creating a copied field and trying to update it through a relationship is unnecessary when a formula field can stay synchronized automatically.

===========

This question is testing the classic Salesforce Process Builder automation best practice , not a generic Flow-only rule. Salesforce’s official process design guidance states that an org should have only one record-change process per object . The reason is simple: every time a record is created or updated, Salesforce evaluates the record-change processes for that object. If an object has multiple record-change processes, the automation becomes harder to predict, harder to troubleshoot, and more likely to hit governor limits. Salesforce specifically explains that consolidating automation into one record-change process gives admins a single view of all criteria and actions for that object, reduces duplicated automation overhead, and allows the app builder to control the order of criteria evaluation.

A is not the best exam answer here. In modern Flow architecture, “one Flow per object” is often discussed as a design pattern, but it is not the exact best-practice wording being tested by this Platform App Builder-style question. Salesforce Flow design is more nuanced today because record-triggered flows can vary by trigger timing and event. B is wrong because validation rules should be separated by validation requirement, not forced into one rule per object. C is wrong because invocable processes are reusable modular processes, not the main record-change automation container.

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.

===========

Global actions are designed to be available broadly, not only from one object’s record page. Salesforce Trailhead states that global actions can be placed anywhere actions are supported and can let users send email without leaving the page they are on.

This fits the requirement because users need a Send New Email action available from Leads, Contacts, and Accounts in the Salesforce mobile app.

Why others are incorrect:

A is incorrect because a global action layout does not automatically clone the default page layout.

B is incorrect because the Lightning Component Library is not the reason to use global actions.

C is incorrect because global actions are not record-specific; object-specific actions are record-specific.

===========

In-App Guidance is Salesforce ' s native capability for contextual onboarding, feature adoption, prompts, and guided walkthroughs directly inside Lightning Experience. Salesforce documents that administrators can create prompts and walkthroughs, determine the target audience, and specify where and when that guidance appears. Targeted prompts can highlight a specific page element, while walkthroughs connect multiple prompts into a step-by-step guided experience. This aligns directly with Universal Containers ' goals of increasing adoption and guiding users through a newly launched application. A Screen Flow is appropriate when collecting information or executing an interactive business process, but it is not the dedicated adoption feature. Dynamic Actions control which actions appear, while Dynamic Forms controls field and section presentation. Neither provides structured onboarding walkthroughs.

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

The correct answer is D.

Salesforce allows converting a master-detail relationship to a lookup relationship only when there are no roll-up summary fields on the master object that summarize the detail records. Salesforce documentation states that after a roll-up summary field exists on an object, the object’s master-detail relationship can’t be converted into a lookup relationship.

In this case, if Account has roll-up summary fields based on related Park records, Salesforce blocks the conversion.

A is incorrect because a flow using Account does not normally prevent converting the relationship. B is incorrect because formulas on Park referencing Account are not the primary restriction. C is incorrect because custom objects do not need at least one master-detail relationship for reporting.

===========

The correct answer is A. Roll-up summary field.

Cloud Kicks wants to count how many Subscription records are related to each Shoe record. Because a master-detail relationship already exists between Subscription and Shoe__c , the app builder should create a Roll-Up Summary field on the master object.

Salesforce documentation confirms that roll-up summary fields can count the number of detail records related to a master record. Trailhead also explains that roll-up summaries display values on the master record based on directly related detail records in a master-detail relationship.

B. Lookup field and C. Master-detail field define relationships, but the relationship already exists. D. Sum field is not a Salesforce field type.

===========

The correct answer is B. Add the standard Chatter feed component.

To show Chatter on a custom object Lightning record page, the app builder should use the standard Chatter Feed / Chatter component in Lightning App Builder. Salesforce documentation describes adding Chatter components such as Chatter Feed, Chatter Publisher, and Chatter to Lightning record pages, usually after feed tracking is enabled for the object.

A is incorrect because a related list component does not display the Chatter feed.

C and D are incorrect because a custom component or AppExchange component is not required for standard Chatter feed functionality.

===========

The correct answers are B. Flow Builder and D. Escalation rules.

Escalation rules are the most direct Salesforce Service feature for this requirement. They are designed to automate case escalation when cases are not resolved or not acted on within a defined time period. Salesforce documentation explains that escalation rule entries can use business hours, and escalation actions can send notification emails when the case escalates.

Flow Builder can also be used because record-triggered flows support scheduled paths, allowing automation to run after a defined time from a triggering record event. A flow can check whether the Case is still in New status and then send a notification. For strict business-hour calculation, the app builder must design the flow carefully around the correct time source/business-hour logic.

A is incorrect because validation rules only prevent invalid data from being saved; they do not wait four business hours and send notifications.

C is incorrect for the Platform App Builder context because Scheduled Apex is a programmatic approach, while declarative automation tools are available and preferred for this requirement.

===========