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

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

In Lightning App Builder, Salesforce provides a standard Chatter component for record pages. 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 related list component does not add the Chatter feed.

B is incorrect because the standard Chatter component is available in Lightning App Builder; it does not need to come from AppExchange.

D is incorrect because a custom component is unnecessary when Salesforce provides the standard Chatter component.

===========

The correct answer is A. Two Master-detail relationships on a new custom object.

This is a classic many-to-many relationship requirement: one Contact can relate to many Solar Projects, and one Solar Project can relate to many Contacts. Salesforce recommends using a junction object for many-to-many relationships. A junction object is a custom object with two master-detail relationships.

The new custom junction object would sit between Contact and Solar Project, with one master-detail relationship to Contact and one master-detail relationship to Solar Project.

C could technically connect records using lookups, but the standard Salesforce data-modeling answer for a true many-to-many relationship is a junction object with two master-detail relationships.

===========

When deploying from a sandbox on a newer Salesforce version to production on a current version, any components that rely on features not yet available in production will fail.

Change sets do not automatically upgrade production.

All features must be supported in the target org at deployment time.

Salesforce documentation notes that compatibility issues may occur if components use version-specific features, and deployments must be tested against the target org’s current version. (Salesforce Help)

A is incorrect because deployments do not automatically wait for production upgrades.

B is partially true, but deployments are possible if features are supported.

C is incorrect; components are not automatically upgraded.

===========

The correct answer is C. Schema Builder.

Schema Builder is designed to help app builders visualize the Salesforce data model, including standard objects, custom objects, fields, and relationships. Salesforce Trailhead states that Schema Builder lets users visualize and edit the data model and is useful for understanding complex data models.

Object Manager and Fields & Relationships are used to configure individual objects and fields, but they do not provide the same visual relationship map. Lightning App Builder is for page layout and UI configuration, not data-model visualization.

The correct answer is C. Checkbox.

Universal Containers needs to track whether a contract was sent or not sent before an Opportunity is marked Closed Won. This is a simple Yes/No reporting requirement, so a Checkbox field is the best field type. Salesforce checkbox fields are represented as True/False values and can be used in reports and list view filters.

Picklist is unnecessary for a two-state value. Text and Text Area would create inconsistent reporting because users could type different values.

A Lightning Component tab is the native mechanism for exposing a standalone Lightning component as a navigation item. Salesforce instructs administrators to create a custom Lightning Component tab for the component and then add that tab to the desired Lightning app through App Manager ' s Navigation Items configuration. Salesforce also identifies Lightning component tabs as supported navigation-bar items. The Utility Bar is designed for persistent productivity utilities displayed while users remain on another page, not for a component that must function as a primary navigation destination. A dashboard adds unnecessary indirection, and a Web Tab is designed for external web content rather than directly surfacing a Salesforce Lightning component. Therefore, creating a Lightning Component tab and adding it to the Sales Operations application ' s navigation menu is the correct solution.

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

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

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 updates. 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.

The correct answer is D. Roll-up summary field.

Cloud Kicks wants to display a count of related Opportunities on the Account record where the Opportunities are Closed Won and have a Close Date within the last year. A roll-up summary field is the correct declarative feature because it calculates values from related records, including counts, sums, minimums, and maximums. Salesforce documentation confirms that roll-up summary fields calculate values from related records and can display values on the parent record.

The app builder can create a roll-up summary field on Account with filter criteria such as:

Stage = Closed Won

Close Date = Last 365 Days / Last Year

Why others are incorrect:

Activity timeline displays activities, not Opportunity counts.

Formula field cannot count multiple child Opportunity records.

Validation rule blocks invalid saves; it does not calculate related record totals.

===========

The correct action is to validate the inbound change set in Production before the deployment window. Salesforce states that an inbound change set can be validated without deploying changes, and validation shows the same success or failure messages that would occur during an actual deployment.

This helps the app builder confirm whether Apex tests, dependencies, and deployment requirements will pass while the developer is away.

Why not others:

A is wrong because removing Apex classes would remove required code.

B is wrong because deployment validation is done from the inbound change set in the target org.

C is not the standard change-set validation process.