Free Practice Questions for Salesforce Platform-App-Builder Exam

The correct answers are A. Public Groups, D. Roles and Subordinates, and E. Users.

For a custom object with Private sharing, manual sharing is used to open access to selected records on a case-by-case basis. Salesforce manual sharing allows individual records to be shared with users, public groups, and roles. Salesforce Classic manual sharing also lets the user select the type of group, user, role, or territory to add.

B. Private Groups is not the standard Platform App Builder answer here.

C. Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.

Page layouts are metadata components. When an updated layout is included in a deployment, the target organization receives the source version of that layout rather than merging independent layout customizations field by field. Consequently, if three fields existed only on the production version but were absent from the sandbox version being deployed, those field placements can disappear when the source layout configuration replaces the target configuration. Salesforce ' s deployment documentation emphasizes that metadata deployments apply the layout configuration supplied in the deployment payload and warns that page-layout metadata and assignments require complete deployment planning. Option A cannot be correct because a failed deployment is rolled back. Missing field permissions affect visibility, but the scenario specifically identifies fields disappearing from the deployed layout configuration. Therefore, B best explains the behavior.

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

The correct answer is C. Unable to reference the child records.

A formula field on Account cannot directly pull data from multiple related Contact records because Contacts are child records of Account. Cross-object formulas work by referencing fields through supported parent relationships, not by traversing from a parent record down to multiple child records. Salesforce documentation describes cross-object formulas as formulas that reference fields on related objects, especially parent records through relationships.

Because an Account can have many Contacts, Salesforce does not expose that child relationship in the formula editor as a single field reference. For summarized child data, the app builder would normally use a roll-up-style solution where supported, or automation such as Flow.

A is unrelated unless the formula has already exceeded character limits.

B is misleading because the core issue is not simply that Account and Contact lack master-detail; it is that formulas cannot directly reference child records.

D is not supported by the scenario.

===========

The correct answer is B. Actions & Recommendations component.

The Actions & Recommendations component is used to give agents a guided to-do list/checklist on a record page. Salesforce documentation describes it as a component that can show flows, quick actions, and recommendations so agents can complete required steps consistently. This matches the requirement to provide service agents with checklist items when servicing a Case.

Why others are incorrect:

A “Business component” is not the standard Salesforce feature for this.

Activity Timeline shows activities, not a required checklist.

Highlights Panel shows key fields and actions, not guided service steps.

===========

Users need Read access to both master objects.

Request Inventory is a junction object with two master-detail relationships: Inventory and Order. For junction objects, access is based on the associated master records and the sharing behavior of the master-detail relationships. Salesforce documentation for object relationship considerations explains that sharing access to a junction object record is determined by access to both associated master records.

Why not the others? Sharing rules are not created directly on a master-detail detail object in the same way, because it is controlled by parent. Apex-based sharing is not needed. Read access to only the first master object is not enough because the junction record connects two master records.

===========

The correct answer is C. Two master-detail relationships on a new custom object.

This requirement is a many-to-many relationship: one Contact can relate to many Solar Projects, and one Solar Project can relate to many Contacts. Salesforce models this with a junction object, which is a custom object with two master-detail relationships.

A simple lookup on one object would not properly support the many-to-many data model.

===========

Grouping is the correct reporting capability because the requirement is to compare Case counts across two categorical dimensions: Status and Priority. Salesforce reports support grouping records by rows and columns. The app builder can group Cases by Status and then by Priority, or configure a matrix-style report using one field for row grouping and another for column grouping. The resulting subtotals and grand totals make the comparison immediately visible. Filters determine which records are included but do not organize the resulting records into comparison categories. Bucket columns are useful for creating temporary categories without adding Salesforce fields, but Status and Priority already provide the required categories. A custom report type controls which related objects and fields are available, not how existing Case records are grouped.

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