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

The correct answer is B. Create a new roll-up summary field called First Order Date, using type MIN on the Opportunity Close Date with a filter where IsWon = TRUE.

Cloud Kicks wants to track the first purchase date for each customer. The first purchase is the earliest won Opportunity Close Date. A roll-up summary field can calculate values from related records and supports summary types such as COUNT, SUM, MIN, and MAX. Salesforce Trailhead states that MIN displays the lowest value from the selected field and supports date/date-time fields.

So the app builder should create a roll-up summary field on the Account, summarize related Opportunities, choose MIN on CloseDate , and filter to only include won Opportunities, such as IsWon = TRUE .

A and C are incorrect because the field should be a roll-up summary field itself, not a regular date field updated by a roll-up.

D is incorrect because SUM is for number, currency, and percent fields, not date fields. Salesforce documentation confirms that MIN/MAX support date fields, while SUM is for numeric-style fields.

===========

The correct answer is D. Partial Copy sandbox.

A Partial Copy sandbox is designed for testing and UAT when users need a subset of production data. Salesforce states that Partial Copy sandboxes include metadata plus a subset of production data via sandbox template, support 5 GB data storage, and have a 5-day refresh interval, which satisfies a weekly refresh requirement.

A. Full sandbox is incorrect because it copies all production data and has a longer refresh interval.

B/C. Developer or Developer Pro are incorrect because they do not copy production data through a template in the same way required for this UAT scenario.

========

The correct answer is D. Deselect auto add to custom report type.

When creating a new custom field, Salesforce provides an Auto Add option that can automatically add the new field to applicable existing custom report types. If the app builder does not want the new field to appear on pre-existing custom report types, they should deselect the Auto add to custom report type option during field creation. Salesforce release documentation confirms that Auto Add automatically adds custom fields to custom report types based on that object.

Why the other options are incorrect:

Removing the field from page layouts only affects record-page visibility, not report type availability.

Changing profile visibility or read-only access affects field security, not whether the field is added to the custom report type layout.

===========

The correct answer is B. Queue.

The approval request must go to department members who can approve overnight shipments. In Salesforce approval processes, routing an approval to a queue is appropriate when a group of users can own or act on the approval request and any one of the queue members can handle it. Salesforce approval documentation describes approval processes as automation that specifies each approval step, including who receives the approval request.

A queue is better than a role or hierarchy field when the request needs to be handled by a department group rather than a single manager or a specific user from a hierarchy field.

A. Role is less appropriate because roles are for hierarchy-based access and routing.

C. Hierarchy field is used when routing to a user identified through a manager-style field.

D. Public group is used for sharing and grouping users, but approval queues are the standard routing choice for a group of approvers in this scenario.

===========

The correct answer is B. Cross-object formula.

Opportunity has a standard relationship to Account, so an app builder can create a formula field on Opportunity that references the parent Account field. Salesforce defines a cross-object formula as a formula that spans related objects and references fields on those related objects.

Because Account_Region__c is a picklist on Account, the Opportunity formula would commonly be a text formula like:

TEXT(Account.Account_Region__c)

Field history tracking only tracks changes, a lookup field would create a relationship rather than display the Account field value, and field-level security controls visibility but does not copy or display the parent field on Opportunity.

===========

The correct answer is D.

Validation rules are the right declarative tool to enforce data compliance before a record is saved. They can prevent a Case from moving backward to an earlier Status and can require specific fields when Case criteria are met. Salesforce formula functions such as ISCHANGED() compare whether a field value changed, and validation rules can use formula logic to stop invalid saves.

Why others are incorrect:

Approval Process is for routing records for approval.

Dependent picklists control picklist value availability, not status regression.

Case Flow can automate case processes, but validation rules are the best tool for enforcing save-time compliance.

===========

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 A. Sharing Hierarchy.

Sales reps want to see who has access to an Account record and why/how they have that access. Salesforce provides this through Sharing Hierarchy. Salesforce documentation states that users can click Sharing Hierarchy from the record action menu to display users who have access to the record. Salesforce release documentation also explains that selecting Sharing Hierarchy lets users view record access and the reason for that access.

C. Sharing is not the best answer because the Sharing button is mainly used to manually grant access, not to view the full access hierarchy and access reasons. B. New Task and D. Edit do not relate to record access visibility.

===========

The correct answers are A. Navigation Menu and C. In-App Notification.

Salesforce documentation states that users can receive and act on approval requests in the Salesforce mobile app by tapping the notification or by going to Approval Requests in the navigation menu. Salesforce also describes the Approval Requests navigation item as showing pending approvals where users can approve or reject items from within Salesforce.

Why others are incorrect:

B. Home Screen is not the documented approval-response delivery method in this context.

D. Record Detail is not the best answer here because the documented mobile approval response paths are the notification and the Approval Requests navigation item.

===========

Use a Roll-Up Summary field on Account to count the related Opportunity records. Salesforce roll-up summary fields can calculate values from related records, and the COUNT summary type totals the number of related records. Trailhead also gives the Account and Opportunity example for roll-up summaries.

A formula field cannot count child records by itself. A lookup field only creates a relationship. AppExchange is unnecessary for this standard use case.

===========