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

The correct answer is D. Rich text area.

The requirement says users need to write detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields are designed for formatted text and support images and hyperlinks.

Long text area supports longer plain text but not rich formatting with images. URL stores a single web address. Multi-select picklist stores selected values, not detailed formatted descriptions.

===========

The correct answer is A. Page structure will automatically adapt to the device being used to view the record page.

When choosing a Lightning record page template, the app builder should consider how the template displays across supported devices. Salesforce Lightning pages are designed for Lightning Experience and the Salesforce mobile app, and Salesforce documentation states that the chosen template controls how the page displays across devices.

B is incorrect because users do not need “View All Data” just to view a Lightning record page; normal object and record access applies.

C is incorrect because Salesforce supports switching Lightning page templates, subject to template-switching considerations.

D is incorrect because the app builder does not create a separate template for every device type.

===========

The correct answers are A. Create a custom-based sharing rule and B. Update the organization-wide defaults.

Here, “custom-based” is most likely referring to a criteria-based sharing rule. UC wants to move from public sharing to a more restrictive model, so the app builder must first update the Organization-Wide Defaults for Accounts. Salesforce OWDs define the default access users have to records they do not own.

Then, to continue giving the Sales team access to all Account records with the Sales record type, the app builder should create a criteria-based sharing rule based on record criteria, such as Record Type. Salesforce criteria-based sharing rules share records based on field values.

C is incorrect because profiles control object permissions, not record-level sharing by record type.

D is incorrect because owner-based sharing rules share records based on record owner, not record type.

===========

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

Customers and dealers are both separate business entities, and separate bills are sent to each. In Salesforce, business entities are best represented as Accounts, while the single individual at each business should be stored as a Contact under the correct Account. Salesforce account hierarchy is used to show parent-child relationships between related accounts.

Why not D? Account Teams represent internal Salesforce users working on an account, not external customer/dealer representation.

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 answers are A. Tabular format and B. Summary format.

Salesforce reporting snapshots can use custom tabular or summary reports as the source report. Salesforce documentation specifically states that a reporting snapshot source report can be tabular or summary.

Why others are incorrect:

C. Joined format is not supported as a reporting snapshot source report.

D. Matrix format is not supported because matrix reports group by rows and columns, and Salesforce troubleshooting guidance states that matrix reports can’t be used with reporting snapshots.

===========

The correct answers are A. Create an object-specific action on Account and D. Create predefined values for most of the fields.

For this requirement, sales reps need to create a custom Feedback record related to an Account with minimal clicks on mobile. An object-specific quick action is the best solution because it runs in the context of a specific Account record and can create a related child record automatically. Salesforce Trailhead states that object-specific actions let users create records with automatic relationships to other records and provide a streamlined mobile and desktop experience.

Predefined field values reduce manual typing and save mobile users time. Salesforce mobile customization guidance explains that quick actions can include predefined fields, and Trailhead specifically shows predefined values being used to prepopulate fields on action layouts.

B. Create a feedback object as a parent of Account is incorrect because the Feedback record should be related to each Account, normally as a child record or lookup-related record. C. Create a global action on Account is incorrect because global actions create records without record context; Salesforce explains that global actions create records with no relationship to other records, while object-specific actions work in the context of a particular object.

===========

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

In Lightning App Builder, Salesforce provides a standard Chatter component. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed on a record page.

A is incorrect because a custom Chatter feed component is not needed.

C is incorrect because this does not come from the AppExchange/App College.

D is incorrect because Chatter feed is not added by using the standard related list component.

===========

The correct answers are C. The report is in the manager’s Private reports folder and D. The report does not have a chart.

The Report Chart component is used to display a chart from a report on a Lightning page. If the report has no chart, it cannot be used as a Report Chart component source. Salesforce documentation describes the Report Chart component as a way to include a chart from a report in a Lightning page.

The app builder also must have access to the report through report folder sharing. Reports saved in a user’s private report folder are not visible to other users unless moved/shared appropriately. Salesforce explains that reports are saved by default into private reports or dashboards folders unless a public/custom folder is selected.

A is incorrect because a report having no returned data does not stop the report from being selectable. B is incorrect because the app builder does not need to be the report creator; they need access to the report folder and the report must contain a chart.

===========

The correct answers are B. Use a roll-up summary field on the Park record and C. Use a master-detail relationship between the Park and Trail objects.

Northern Trail Outfitters wants the total number of Trails displayed on the Park record without code. In Salesforce, a standard roll-up summary field can count related child records, but it requires a master-detail relationship between the parent and child objects. Salesforce documentation confirms that roll-up summary fields calculate values from related records, and this is the correct declarative feature for this requirement.

A is incorrect because a formula field cannot count child records. D is incorrect because standard roll-up summary fields do not work on ordinary lookup relationships.

===========