App Builder Platform-App-Builder Release Date

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 answers are A. Data loss may occur when changing custom field types and D. Field History Tracking records value changes of 255 characters or less.

A is correct because Salesforce warns that changing the data type of an existing custom field can cause data loss in certain situations. This is a key consideration before converting Text Area (Long) fields to Rich Text Area fields.

D is correct because Salesforce field history tracking has a character limitation. Salesforce tracks changes to fields with more than 255 characters as edited, but it does not record the old and new values. That means long/rich text changes beyond that limit do not provide full before-and-after history values.

Why others are incorrect:

B is not the relevant consideration for this field conversion requirement.

C is incorrect because Salesforce reports do not display rich text field values of all lengths fully; Salesforce documentation notes report display limits for long text and rich text area fields.

===========

The correct answer is B. Quick action.

Sales reps need to create Opportunity records directly from an Account, with several fields prepopulated. This is an object-specific Quick Action use case. Salesforce states that object-specific actions let users create or update records in the context of a particular object. Salesforce also supports predefined field values for quick actions, which can prepopulate fields and make record creation faster.

Default action is not the correct feature name for this requirement. Custom button and custom link are older navigation-style tools and are not the best Lightning/mobile-friendly option for creating related records with predefined values.

===========

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.

===========