Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers | Set: 7

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 answers are C. Use Data Loader to update leads using the CSV file and D. Select Insert Null Values in Settings.

Universal Containers wants to delete values from fields on 5,000 Lead records. The correct method is to use Data Loader Update with the record IDs in the CSV file, leave the target field cells blank, and enable Insert Null Values so Data Loader treats the blank CSV values as null up dates. Salesforce Help explains that to change field values to blank/null with Data Loader, export IDs and fields, clear the values in the CSV, select Insert Null Values, and run an update.

Why others are incorrect:

A is unrelated because record type selection does not delete field values.

B is not the best choice because the Import Wizard is not the proper tool for mass clearing field values using null updates.

Schema Builder can create custom objects, relationship fields, formula fields, and normal fields, but a key limitation is that fields created through Schema Builder are not automatically added to the object’s page layout. The app builder must go to the page layout separately and place the fields where users need to see them. Salesforce Trailhead confirms Schema Builder supports relationship fields, formula fields, and normal fields, so option B is incorrect. Salesforce Help also notes that fields added through Schema Builder are not automatically added to the page layout.

The correct answers are A. Assign app to profiles and B. Build a Custom Tab for the app.

Your option A appears corrupted as “Asking new options,” but the known Salesforce wording for this question is Assign app to profiles.

To make a custom Lightning app available to internal users, users must have access to the app through profile/app assignment. Salesforce documentation explains that assigned app settings specify which apps users can select from the Lightning Platform app menu.

A Custom Tab is also needed when exposing the custom app/component as something users can access from the Salesforce UI. Salesforce documentation states that custom tabs can appear in the app navigation bar and App Launcher.

Adding the app to a Visualforce page is not required, and uploading it to Static Resources is not how Lightning apps are made available to users.

===========

The correct answer is C.

To show Component records as a related list on Product, the app builder should create a relationship field on the child object, Component, pointing to the parent object, Product. Salesforce documentation explains that when a lookup relationship is defined, the lookup field is added on one object and a related list can be shown on the associated object’s page layout.

A is unnecessary unless the requirement is many-to-many. B is incorrect because a roll-up summary does not create a related list. D is incorrect because the relationship field direction is wrong; the field should be on Component, not Product.

===========

The correct answer is A.

UC has three Lead sources: web, trade shows, and partners. Some Lead information is common to all, while other fields are unique to each source. The best configuration is to use Lead record types with separate page layouts so each type of Lead shows the fields relevant to that process. Salesforce documentation states that record types allow different business processes, picklist values, and page layouts for different users or record categories.

B is not ideal because it leaves irrelevant fields visible and relies on users to collapse sections. C unnecessarily creates a different Lead object for the partner community. D is incorrect because separate custom objects would fragment Lead management and prevent standard Lead functionality from being used consistently.

===========

The correct answers are A. Flow Launcher and D. Quick Action.

A flow can be exposed to users through a page-based launcher/component. Salesforce Trailhead explains that users can access a flow by adding it to a Lightning page through Lightning App Builder. The Flow component can be dragged onto the Lightning page so users can run the flow from that page.

A Quick Action can also launch a flow. Salesforce documentation states that quick actions help users launch and navigate through workflows, and Trailhead confirms that custom actions can invoke flows.

Why others are incorrect:

B. Apex can invoke automation programmatically, but it is not the best user-facing access feature in this question.

C. Approval Process routes records for approval; it is not a general method for users to access flows.

===========

The correct answer is C. Developer sandbox.

For small, individual projects where teams need separate environments before moving work into a larger shared testing sandbox, a Developer sandbox should be considered first. It is intended for development and testing of configuration changes in an isolated environment and is the lowest-cost sandbox option compared with Developer Pro, Partial, and Full sandboxes. Salesforce describes sandbox types for different testing and development needs, with Developer and Developer Pro sandboxes copying configuration/metadata rather than full production data.

Developer Pro provides more storage, but the question emphasizes small projects and keeping costs down. Partial and Full sandboxes are better for broader testing with data, but they are not the first choice for many small isolated development efforts.

===========

The correct answers are A. Tabs and B. Related record.

Tabs help create a more condensed Lightning record page by grouping information into separate tabbed sections instead of showing everything in one long page. Salesforce Lightning App Builder allows app builders to add, remove, reorder, and customize components on Lightning record pages.

Related Record is required because service agents want to modify the associated Contact and Account directly from the Case Lightning record page. Salesforce Help states that the Related Record component uses quick action metadata and requires an associated quick action to update records.

Why others are incorrect:

Path is used to guide users through stages or status values, not to edit related Account or Contact records.

Rich Text displays formatted guidance or static text; it does not provide editable related-record functionality.

The validation rule must fire when two things are true:

Job_Accepted__c is already populated

Hire_Date__c is being changed

Salesforce’s ISCHANGED() function returns true when a field’s value changes from its previous value, and formula functions can be used in validation rules.

So this formula prevents users from changing the hire date after the candidate has accepted the offer:

NOT(ISBLANK(Job_Accepted__c)) & & ISCHANGED(Hire_Date__c)

Why others are incorrect:

The other options either use the wrong logical operator or validate the opposite condition. A validation rule must return TRUE only when Salesforce should block the save.

===========