Salesforce Updated Platform-App-Builder Exam Questions and Answers by lennox

The correct answer is B. Create a unique External ID field and use Data Loader.

Cloud Kicks is receiving shipment data from an external shipping system on a regular basis. To prevent duplicate Delivery records and update the correct existing records, the app builder should create a field such as Tracking Number on Delivery__c , mark it as External ID and Unique, then use Data Loader Upsert.

Salesforce documentation states that external IDs can be used when importing custom objects to prevent duplicate records. Salesforce Data Loader documentation also states that upsert combines insert and update: if a matching record exists, it updates it; otherwise, it creates a new record.

A is less appropriate because this is a recurring system migration/update scenario, and Data Loader with External ID is the stronger tool.

C is incomplete because matching only on Salesforce ID requires the external system to already store Salesforce record IDs.

D may help detect duplicates, but duplicate/matching rules do not provide the clean upsert mechanism needed to update the correct existing record.

===========

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

Formula fields can reference fields from related parent records using cross-object formulas, but they cannot directly pull values from multiple child records onto a parent record. Salesforce describes cross-object formulas as formulas that can reference fields from a parent object when the formula is created on the child/detail side of the relationship.

In this case, Account is the parent and Contacts are child records. Since the formula is being created on Account and trying to reference related Contacts, the relationship does not appear in the formula editor.

Correct design alternatives: use a roll-up summary where supported, Flow, Apex, or reporting.

===========

The correct answers are B. Assign the page to a combination of apps and profiles, C. Make the page the default homepage for specific apps, and E. Make the page the org default.

When activating Lightning pages, Salesforce supports assigning a page as an org default, assigning it to specific Lightning apps, and assigning it to combinations such as app and profile. Salesforce Trailhead also confirms that Lightning record page activation supports org default, app default, and app/record type/profile assignments.

A is incorrect because Lightning page activation uses profiles, not permission sets, for this assignment model.

D is incorrect because Lightning pages are not activated by role as a standard activation option.

===========

The correct answer is B. Data is unable to be deployed with change sets.

Change sets deploy metadata/configuration, not business data. Salesforce documentation states that change sets can contain setup modifications, but they cannot be used to upload a list of records such as contacts.

So the report itself can be deployed, but the underlying records needed for the report results are not deployed through the change set. If the Partial Copy sandbox does not contain matching sample data, the report returns no data.

Why others are incorrect:

Data is not deployed just because it is added to a change set.

Reports do not have to be manually recreated if they are deployed properly.

“Salesforce OK” is not a deployment requirement.

===========