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

The correct answer is B. Edit a record page using Lightning App Builder > Drag the component onto the page.

A custom Lightning component installed from AppExchange is configured on a Lightning record page through Lightning App Builder. Salesforce documentation states that Lightning App Builder supports custom Lightning components, including Aura and Lightning web components, and record pages are edited as Lightning pages.

The Page Layout editor is used for fields, buttons, related lists, and layout behavior, not for placing Lightning components on a Lightning record page. App Manager manages apps and utility bars, but the page canvas configuration is done in Lightning App Builder.

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

The correct answer is A. The report type is already based on Opportunities with or without Shipments, so the app builder should not change the report type’s primary object. To expose Account Rating, the app builder should edit the custom report type layout and use Add fields related via lookup from the Opportunity view, because Opportunity has a relationship to Account. Salesforce documentation confirms that custom report types allow fields from objects not directly included in the report type structure by using Add fields related via lookup.

Why others are incorrect:

B is incorrect because the standard Account–Opportunity relationship cannot simply be changed to master-detail.

C is incorrect because changing the primary object to Account would change the report purpose.

D is incorrect because adding a field to a record page does not make it available in a report type.

===========

The correct answer is A. Account Object .

Roll-up summary fields are created on the parent object , because the summary value is displayed on the parent record. Here, the KPI values need to appear for each Account , and they summarize related Opportunity records. Therefore, the app builder should go to the Account object in Object Manager and create roll-up summary fields there.

For this requirement, the app builder would create separate roll-up summary fields on Account, such as:

Count of open Opportunities

Count of won Opportunities

Salesforce documentation describes roll-up summary fields as fields that calculate values from related records, such as records in a related list.

C. Opportunity Object is incorrect because Opportunity is the child/related record being counted.

D. Lightning App Builder is incorrect because Lightning App Builder controls page layout/components, not the creation of roll-up fields.

B. Lightning Object Creator is used to create objects from spreadsheets, not build rollups.

===========

The correct answer is A. Create a lookup relationship on Asset Inventory to Asset. Add the Asset Inventory related list to the Asset page layout.

To show Asset Inventory records as a related list on Asset, the child object must contain the relationship field pointing to the parent object. In this scenario, Asset Inventory is the child/detail-style object, and Asset is the parent record where the related list should appear.

Salesforce relationship fields connect records between objects, and related lists can then be added to the parent object’s page layout. Salesforce documentation for related lists confirms that related lists are managed from the object’s page layout.

Why others are incorrect:

B is incorrect because a roll-up field does not create the relationship or related list.

C is incorrect because the relationship direction is wrong; the relationship field should be created on Asset Inventory, not on Asset.

D is incorrect because a junction object is only needed for many-to-many relationships. Here, Asset Inventory records simply need to relate to Asset records.

===========

Limitations when changing custom field data types include:

A. It is not possible to change the data type of a formula field – formula fields cannot be converted to other field types because they are calculated dynamically.

D. It is not possible to change a Text Area (Long) field to Text – Salesforce prevents reducing the field length because data loss could occur.

Salesforce documentation highlights these restrictions: (Salesforce Help)

B is partially true; changing fields referenced in Apex requires careful handling, but Apex references can sometimes be updated automatically.

C is allowed with some limitations if the External ID type is compatible.

===========

The correct answers are A. Roll-up summaries are limited to master-detail relationships and C. An object can have 25 roll-up summaries.

Roll-up summary fields summarize data from related child records onto the parent record, but standard Salesforce roll-up summaries are available only when the child records are directly related through a master-detail relationship. In this scenario, only one of the three custom objects has a master-detail relationship to Account, so native roll-up summaries cannot be used for the other two lookup/non-master-detail objects.

Salesforce also lists 25 roll-up summary fields per object as the standard allocation, so summarizing 15 fields from three objects would require 45 summaries, which exceeds the normal Account object limit.

B is incorrect because native roll-up summary calculations support COUNT, SUM, MIN, and MAX, not AVG.

D is incorrect because “20 object references” is not the key roll-up summary consideration in this proposal.

The correct answer is A. Flow.

The requirement says the Opportunity should store the Account Billing State value, but the value must remain static after the Opportunity is created. A record-triggered Flow is the recommended declarative automation because it can run when an Opportunity is created and populate a custom field with the related Account’s Billing State. Salesforce Trailhead describes record-triggered flows as automation that can run when a record is created or updated, and can update the triggering record or related records depending on configuration.

D. Formula field is incorrect because formula fields are automatically calculated and read-only. A formula would continue to reflect the current Account Billing State, so it would not preserve the original value after creation.

B. Apex is not the recommended first choice because Flow handles this requirement declaratively.

C. Roll-up summary field is incorrect because roll-ups aggregate child records; they do not copy a parent Account field value onto an Opportunity.

The correct answer is C. Approval process.

The key requirement is that the manager’s sign-off on free parts must be processed. Salesforce approval processes are designed to automate record approval, define approval steps, assign approvers, and perform actions when records are approved or rejected. Salesforce Trailhead gives a similar discount-management example where discount percentage is tracked and manager approval is requested through an approval process.

Why others are incorrect:

A. High Velocity Sales is for sales engagement/cadences, not approval sign-off.

B. Quotes may help with pricing, but it does not by itself process manager approval.

D. Checkbox can store a value but cannot route approval.

===========

The correct answer is B.

When customer invitations are enabled for Chatter groups, invited customers get limited collaboration access. Salesforce documentation states that customers can see only the groups they’re invited to and can interact only with members of those groups.

A is incorrect because invited customers do not automatically get broad group-invitation rights. C is incorrect because Chatter customer access does not grant access to Account records. D is incorrect because customers are invited to specific groups; they do not receive general public-group request access.

===========

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

Cloud Kicks wants to count how many Subscription records are related to each Shoe record. Because a master-detail relationship already exists between Subscription and Shoe__c , the app builder should create a Roll-Up Summary field on the master object.

Salesforce documentation confirms that roll-up summary fields can count the number of detail records related to a master record. Trailhead also explains that roll-up summaries display values on the master record based on directly related detail records in a master-detail relationship.

B. Lookup field and C. Master-detail field define relationships, but the relationship already exists. D. Sum field is not a Salesforce field type.

===========