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

The correct answer is D. Sum.

Cloud Kicks wants the total value of all won Opportunities displayed on the Account record. In a roll-up summary field, SUM totals the values in a selected numeric/currency field, such as Opportunity Amount. Salesforce documentation identifies SUM as the roll-up summary type used to total values in the selected field.

The app builder would create a roll-up summary field on Account, summarize Opportunities, use SUM on the Amount field, and apply filter criteria for won Opportunities, such as Stage equals Closed Won.

A. Count would only count the number of Opportunities.

B. Total is not the Salesforce roll-up summary type name.

C. Aggregate is not the specific roll-up summary option used here.

===========

To optimize Salesforce Mobile experience:

B. Minimize formula fields and lookup fields improves page load performance on mobile devices.

C. Put key fields in the compact layout ensures important information is visible immediately.

E. Use Global Actions simplifies creating or updating records from mobile quickly.

Salesforce documentation on mobile best practices recommends limiting complex fields, prioritizing compact layouts, and using quick actions for essential functionality. (Salesforce Help)

A is incorrect because default values improve speed and reduce user errors, not eliminate them.

D is unnecessary; Lightning layouts are responsive and do not require separate OS-specific layouts.

===========

Use a Component visibility filter. The issue is not object access or field access. The Contact Lightning record page is shared, but one component should be hidden for users with the Marketing profile. Salesforce Lightning App Builder supports visibility filters on Lightning page components, so the app builder can conditionally show or hide that component based on user/profile criteria.

Why not the others? AppExchange is unrelated. Detail page layouts control field layout, not visibility of a Lightning page component. Field-level security controls field access, not whether a large component appears on a Lightning record page.

===========

The correct answers are B. Set organization-wide default to Private, D. Disable Grant Access Using Hierarchies, and E. Create a criteria-based Sharing Rule for the HR Department.

Set the Review object’s OWD to Private so review records are not visible to all employees by default. Organization-wide defaults define the baseline record access users have to records they do not own.

Disable Grant Access Using Hierarchies because this is a custom object and the requirement says only HR and the submitting employee should see the review. Salesforce allows this setting to be disabled for custom objects so managers higher in the role hierarchy do not automatically inherit access.

Create a criteria-based sharing rule for the HR department so HR can see the Review records even though the default access is private. Salesforce sharing rules are used to grant wider access beyond OWD.

Why others are incorrect:

A is not needed and a Master-Detail relationship to User is not the right access-control design.

C is incorrect because removing Review Read permission from non-HR users would also prevent the submitting employee from viewing their own submitted review.

===========

The correct answers are A. Data loss may occur when changing custom field types and D. Field History Tracking records value changes of 255 characters or less.

A is correct because Salesforce warns that changing the data type of an existing custom field can cause data loss in certain situations. This is a key consideration before converting Text Area (Long) fields to Rich Text Area fields.

D is correct because Salesforce field history tracking has a character limitation. Salesforce tracks changes to fields with more than 255 characters as edited, but it does not record the old and new values. That means long/rich text changes beyond that limit do not provide full before-and-after history values.

Why others are incorrect:

B is not the relevant consideration for this field conversion requirement.

C is incorrect because Salesforce reports do not display rich text field values of all lengths fully; Salesforce documentation notes report display limits for long text and rich text area fields.

===========

The correct answer is B.

Salesforce supports roll-up summary fields for summarizing related records, including scenarios involving Account and related Opportunity values. However, Salesforce documentation states that if Advanced Currency Management is enabled, currency roll-up summary fields are invalid when they are on Accounts and summarize Opportunity values.

Because the VP wants to aggregate Opportunity Amount values on Account, the app builder cannot create that roll-up summary field if Advanced Currency Management is enabled.

Why not others:

A is not the stated Salesforce limitation.

C is wrong because roll-up summary fields are available on Account in supported scenarios.

D is wrong because currency fields can be used in roll-up summaries generally; the issue is specifically Advanced Currency Management with Account-to-Opportunity currency rollups.

The correct answers are C. Text field and D. Number field.

Salesforce allows custom Text, Number, Email, and Auto Number fields to be marked as External ID fields. Since the available choices include Text and Number, those are the two valid answers.

Why others are incorrect:

A. Phone field cannot be marked as an External ID.

B. URL field cannot be marked as an External ID.

===========

The correct answer is D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.

Universal Containers needs to represent separate business entities because separate bills are sent to each customer and each dealer. In Salesforce, business accounts are used to represent companies or organizations, and contacts represent the people who work for those accounts. Salesforce account hierarchies are used to show relationships between related accounts through the Parent Account field.

So the best model is:

Customer = Account

Dealer = Account

Representative at each business = Contact on that Account

Customer/dealer relationship = Account Hierarchy

A is incorrect because Account Teams represent internal Salesforce users working on an account, not external dealer/customer representatives.

B and C are incorrect because they do not correctly represent separate billing entities as separate Accounts.

===========

The correct answer is C.

A Partial Copy sandbox uses a sandbox template to determine which objects and data are copied from production. Salesforce states that sandbox templates let admins select specific objects and data to copy to a Full or Partial Copy sandbox. If the custom object Shipping was not included in the sandbox template, its production records would not be copied into the refreshed partial sandbox.

Why others are incorrect:

A is not the likely issue; refresh timing does not explain one object having no data.

B is less likely as the scenario points to template selection.

D is not the best answer because capacity may limit copied data, but missing all data for a specific object usually indicates the object was not selected in the sandbox template.

===========

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.