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

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 Automation Lightning App ' s Monitor tab is Salesforce ' s centralized interface for examining failed and paused flow interviews. Salesforce states that the Monitor tab displays failed interviews, their error information, and details needed to determine why execution failed. From the failed interview details, an administrator can open the run in debug mode and inspect the execution information without requiring the user to reproduce the issue. This directly satisfies the requirement to troubleshoot intermittent production failures from historical flow runs. Option A focuses primarily on paused interviews and is not the current comprehensive monitoring experience. Apex Replay Debugger is intended for Apex debugging rather than declarative Flow execution. Running the flow manually as another user creates a new test execution rather than analyzing the specific production failures that already occurred.

The correct answers are A. Roll-up summaries are limited to master-detail relationships and C. An object can have 25 roll-up summaries.

Roll-up summary fields summarize data from related child records onto the parent record, but standard Salesforce roll-up summaries are available only when the child records are directly related through a master-detail relationship. In this scenario, only one of the three custom objects has a master-detail relationship to Account, so native roll-up summaries cannot be used for the other two lookup/non-master-detail objects.

Salesforce also lists 25 roll-up summary fields per object as the standard allocation, so summarizing 15 fields from three objects would require 45 summaries, which exceeds the normal Account object limit.

B is incorrect because native roll-up summary calculations support COUNT, SUM, MIN, and MAX, not AVG.

D is incorrect because “20 object references” is not the key roll-up summary consideration in this proposal.

The correct answer is B.

When customer invitations are enabled for Chatter groups, invited customers get limited collaboration access. Salesforce documentation states that customers can see only the groups they’re invited to and can interact only with members of those groups.

A is incorrect because invited customers do not automatically get broad group-invitation rights. C is incorrect because Chatter customer access does not grant access to Account records. D is incorrect because customers are invited to specific groups; they do not receive general public-group request access.

===========

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 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.

===========

The correct answer is B. Validation Rule.

DreamHouse Realty wants to prevent an Opportunity from entering the Qualified stage unless Expected_Close_Date__c is populated. A validation rule is the correct tool because Salesforce validation rules check whether record data meets specified criteria before the user can save the record.

A validation rule could check:

Stage = Qualified

AND

Expected_Close_Date__c is blank

If both are true, Salesforce blocks the save and displays an error message.

A. Page Layout can make a field visible or required on a layout, but it cannot conditionally require the field only when Stage equals Qualified.

C. Activity History is unrelated.

D. Record Type controls business processes and layouts but does not enforce this condition by itself.

===========

The correct answer is D. Universal Containers wants the real-time value of the Account’s Support Level picklist to appear on related Case records. The best declarative solution is a cross-object formula field on Case that references the related Account field.

Because Support Level is a picklist, the formula should use the TEXT() function to return the picklist value as text. Salesforce documentation states that cross-object formulas can reference fields from related objects, and Salesforce’s TEXT function supports picklist values in formulas.

Example formula concept:

TEXT(Account.Support_Level__c)

Why others are incorrect:

A is incorrect because the formula must be on Case, not Account.

B is incorrect because Case already relates to Account; a new lookup alone does not display the value.

C is incorrect because roll-up summary fields summarize child records; they do not copy/display a parent picklist value on child Case records.

===========

Dynamic Forms Field and Field Section components historically required special mobile handling. Salesforce now provides the Dynamic Forms and Dynamic Highlights Panel on Mobile setting in Salesforce Mobile App Setup so mobile users can receive the Dynamic Forms experience used on desktop record pages. Salesforce specifically states that when users cannot receive Dynamic Forms Field and Field Section behavior on mobile, administrators should enable this setting from Setup → Salesforce Mobile App. Adding more Field Sections does not solve the underlying mobile-support setting. Visibility rules control when already-supported components appear, but they do not substitute for enabling Dynamic Forms on Mobile. Reverting mobile users to traditional page layouts is also unnecessary when Salesforce provides native Dynamic Forms mobile support. Therefore, C addresses the underlying configuration issue directly. Salesforce

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

The correct answers are A. Review the Contact record and ensure it is linked to an Account, C. Verify the users with the issue have access to the Contact object, and E. Confirm whether Default Organization-Wide Sharing Settings provide access to the Account.

A Contact that is not linked to an Account is treated as a private contact. Salesforce states that contacts without an account are private regardless of the sharing model, so checking whether the Contact is associated with an Account is a valid troubleshooting step.

Users also need object-level access to the Contact object. Object permissions control whether users have base-level access such as read, create, edit, and delete for an object.

Finally, Contact visibility is often affected by Account access, especially when Contact sharing is controlled by the parent Account. Organization-Wide Defaults define the default record access users have for records they do not own, so checking the Account OWD is also correct.

B is incorrect because creating a new Contact does not troubleshoot the actual sharing/security issue.

D is incorrect because creating a broad Account Sharing Rule for all records is not the first troubleshooting step and may overexpose data.

===========