Free Practice Questions for Salesforce Platform-App-Builder Exam

The correct answers are A. Use a master-detail relationship between the Park and Trail objects and C. Use a roll-up summary field on the Park record to show the total number of trails .

To show the total number of child Trail records on the parent Park record without code, the app builder should use a roll-up summary field . Salesforce documentation states that roll-up summary fields display values on a master record based on related detail records.

That means Park should be the master object and Trail should be the detail object. Then a roll-up summary field on Park can count the related Trail records.

B is incorrect because standard lookup relationships do not support roll-up summary fields.

D is incorrect because a formula field cannot count multiple child records.

===========

The correct answer is C. Record Detail.

The Record Detail component on a Lightning Record Page displays the fields and sections from the object’s assigned page layout. After using Lightning Object Creator to create the object, fields, and data, the app builder must add the Record Detail component if users need to see the fields from the page layout on the Lightning Record Page. Salesforce documentation states that the Record Detail component displays fields and sections from the page layout associated with the object.

Why the other options are incorrect:

Highlights Panel shows key record actions and compact-layout information.

Recommendations displays recommendation records.

Path shows guided stage/status progression, not all page-layout fields.

===========

The correct sandbox type is Partial Copy.

A Partial Copy sandbox is built for testing with a subset of production data. Salesforce lists Partial Copy sandboxes with 5 GB data storage and a 5-day refresh interval, which supports the requirement to refresh it every weekend.

Why the other options are wrong:

Developer and Developer Pro sandboxes are mainly for development and do not copy a produc tion data subset in the same way. A Full sandbox can copy all production data, but its refresh interval is longer and it is unnecessary for a subset under 5 GB.

===========

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 C. A record-triggered flow can run automatically when an Opportunity is updated to Closed Won, create a renewal Opportunity, and notify the contracts team. Salesforce Trailhead explains that record-triggered flows are built around trigger, criteria, and action; for example, when an Opportunity is created or updated and meets criteria, the flow can create another record.

Salesforce Flow can also create records and send emails, which fits both requirements: create the renewal Opportunity and notify an external contracts team.

Why others are incorrect:

A Approval Process is for review/approval routing.

B Outbound Message may notify an external system, but it does not handle the full renewal Opportunity creation requirement by itself.

D Validation Rule only prevents bad data; it does not create records or send notifications.

===========

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 answers are A. The NOW() function in the formula field and D. A cross-object field referenced in the formula field.

Salesforce allows roll-up summary fields to summarize formula fields only when the formula does not contain unsupported dynamic or cross-object references. Salesforce documentation states that roll-up summaries can calculate formula fields only if the formula does not contain cross-object field references or functions that derive values dynamically, such as NOW() or TODAY().

A is correct because NOW() changes dynamically based on current date/time.

D is correct because cross-object field references prevent the formula from being used in the roll-up summary.

C is incorrect because CASE() itself is allowed.

B is incorrect because the issue is not simply a field update; the restriction is specifically cross-object references or dynamic formula functions inside the formula being summarized.

===========

omprehensive and Detailed Explanation with all Platform App Builder documents: =

The correct answer is A. Sandbox cloning.

Cloud Kicks needs many parallel sandboxes that start from the same base configuration and data. Sandbox cloning is designed for this because Salesforce copies the source sandbox’s data and metadata into a new sandbox. Salesforce documentation states that cloning a sandbox copies its data and metadata into the new sandbox.

Partial copy and full copy are sandbox types, not the best mechanism for repeatedly creating many sandboxes from the same prepared baseline. Sandbox refreshes update existing sandboxes; they do not create at least 20 parallel environments from the same baseline.

===========

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.

===========

The correct answers are A. Create owner-based sharing rules that give Read access to the master objects and C. Set Sharing Settings to Read Only on both Master-Detail relationship fields.

A junction object is normally created with two master-detail relationships to represent a many-to-many relationship. Salesforce documentation states that sharing access to a junction object record is determined by the user’s access to both associated master records and the Sharing Setting option on the master-detail relationship fields.

Because the master objects, Seminars and Attendees, have private organization-wide defaults, selected users need record access to those master records. Owner-based sharing rules can grant the selected group Read access to the master object records. Salesforce also documents that organization-wide defaults define baseline record access, and sharing rules are used to extend access when defaults are private or restricted.

The Read Only sharing setting on the master-detail relationship allows users with at least read access to the master records to work with related detail records, assuming they also have the required object permissions on the junction object.

B is incorrect because lookup filters restrict selectable related records; they do not grant record access.

D is incorrect because junction object records in master-detail relationships inherit sharing from the master records. Sharing is not handled directly through an owner-based sharing rule on the junction object.

==========