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

The correct answer is B. Geolocation.

Salesforce geolocation fields are used to identify locations using latitude and longitude and can support distance calculations.

Because Universal Containers delivers containers to remote construction sites and customers provide crossroads or location markers, the app builder should use a Geolocation field to capture location-based information rather than a number, reference, or external lookup field.

Why others are incorrect:

A. Number stores numeric values only.

C. Reference is not the correct field type for capturing physical location.

D. External Lookup is used to relate Salesforce records to external object records, not to store site location details.

===========

The correct answer is A. Highlights panel.

In Lightning Experience, record actions such as New Task appear in the Highlights Panel area of the Lightning record page. Salesforce documentation explains that the actions in the highlights panel come from the object’s page layout, specifically the Salesforce Mobile and Lightning Experience Actions section, unless dynamic actions are enabled.

Since the custom action was already added to the Mobile & Lightning Actions section on the page layouts, the app builder must add the Highlights Panel component to display those actions on the Lightning record page.

Activities shows activity timeline/composer-related functionality, but it is not where page-layout actions are generally displayed. Related Lists and Related Record do not display the main action bar.

===========

The lookup field is created on the custom object Box and points to Account. That makes Account the parent-side object and Box the related child object. Salesforce automatically creates a standard relationship report type in the format Parent Object with Child Object, so the report type is Accounts with Boxes. Salesforce Help confirms that standard report types can be generated automatically when reportable custom objects have lookup relationships.

Why others are incorrect:

A. Boxes with Accounts starts from the child object perspective.

C and D include “with or without,” which is normally configured through custom report type relationship options, not the automatically created standard relationship report type.

===========

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

Formula fields can reference fields on related parent records through cross-object formulas. For example, a formula field on Contact can reference Account fields because Account is the parent of Contact. Salesforce Trailhead shows this pattern by inserting Contact | Account | Account Number in a formula on Contact.

However, the reverse direction is not supported in a normal formula field. An Account formula cannot directly reference values from multiple related Contact child records. Since Contacts are child records of Account, the Contact relationship does not appear in the Account formula editor.

A is incorrect because the issue described is about relationship direction, not the number of formula fields.

C is incorrect because Contact and Account do not need a master-detail relationship for this limitation to apply.

D is incorrect because Salesforce formula character limits are separate from this parent-to-child reference limitation. Salesforce documents formula character limits separately.

===========

The correct formula is:

IF(

NOT(ISBLANK(Nickname__c)),

Nickname__c,

FirstName

)

Salesforce recommends ISBLANK() to check whether a field has no value, including text fields. Since Nickname__c is optional, the formula first checks whether it is not blank. If it has a value, Salesforce uses the nickname. If it is blank, Salesforce uses FirstName .

A is incorrect because BLANKVALUE() is not used this way inside NOT() .

B is incorrect because the logic is reversed and ISNULL() is not preferred for text fields.

D is incorrect because TEXT() is not needed for a text field and does not perform a blank check.

===========

The correct answer is B. Flow.

The requirement is to show the number of open Cases for both the Account and the Parent Account. This is not a simple native roll-up summary scenario because standard roll-up summary fields are mainly for master-detail relationships, while lookup relationships do not support standard roll-up summary fields.

Salesforce specifically documents Flow examples where a flow looks up the parent account, checks how many open cases it has, and evaluates that count. Salesforce also has guidance for creating roll-up-style summaries using Flow, including a use case to count Cases related to an Account.

Why others are incorrect:

A. Approval Process is for approvals, not counting open Cases.

C. Custom object is unnecessary.

D. Roll-up summary is not the best fit for counting Cases across Account and Parent Account relationships.

===========

The correct answer is B. Data Import Wizard.

The list contains only approximately 800 leads, which is well within the Salesforce Data Import Wizard limit. Salesforce documentation states that Data Import Wizard can import leads and supports up to 50,000 records at a time. It is also the best standard tool here because the requirement includes preventing duplicate lead records during import.

Data Loader is better for large-volume or scheduled technical loads, but it does not provide the same simple duplicate-prevention import experience for this small daily lead list. Manual entry is inefficient, and DataLoader.io is not the standard Platform App Builder exam answer.

===========

The correct answers are B. Cross-object field updates between Training and Student records are not supported and C. On Training record, the Student Lookup field can be made optional.

This question is about creating a Student lookup field on the Training object. A lookup relationship is a looser relationship than master-detail. Salesforce documentation explains that lookup relationships do not support roll-up summary fields, unlike master-detail relationships.

Because this is a lookup relationship, the Student lookup field on Training can be optional unless the app builder marks it required. Cross-object field updates are also not supported in this lookup relationship scenario; Salesforce documents that cross-object field updates work for master-detail relationship scenarios, not normal lookup relationships.

A is incorrect because roll-up summary fields require a master-detail relationship.

D is incorrect because deleting Student records is controlled by object permissions and relationship delete behavior, not simply by access from the Training record.

===========

The correct answer is C. App Manager.

To add components to the Utility Bar of an existing Lightning app, the app builder edits the app from Setup → App Manager, then uses the app’s Utility Items configuration. Salesforce Help specifically states that to edit or add a utility bar to an existing app, use App Manager and click Edit for the app.

Why others are incorrect:

A is close, but the entry point for editing an existing app’s utility bar is App Manager, not directly Lightning App Builder.

B is wrong because a Lightning Record Page is for record page layout/components, not app-level utility bar configuration.

D is wrong because App Menu is for launching apps, not configuring them.

===========

The correct answer is A because the rule must fire only when Sales Organization = Canada and Pricing Tier is blank.

ISPICKVAL() checks whether a picklist equals a specific text value, and TEXT() converts a picklist value into text so ISBLANK() can evaluate whether it is empty. Salesforce documents ISPICKVAL() for comparing picklist values and TEXT() for converting picklist values in formulas.

Why others are incorrect:

B has invalid formula structure.

C uses incorrect picklist blank logic.

D uses OR , which would require Pricing Tier even when Sales Organization is not Canada.

===========