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

The correct answer is B. Feed Tracking.

DreamHouse Realty wants changes to selected fields, such as Asking_Price__c and Real_Estate_Agent__c , to appear prominently in Chatter. This is exactly what Chatter Feed Tracking is used for.

Salesforce documentation states that feed tracking is available for record fields and can be configured for custom objects. Salesforce guidance also says admins can enable feed tracking from Setup, select an object, enable feed tracking, and choose fields to track.

A. Topics is used for categorizing Chatter posts, not automatically tracking field changes.

C. Pin Field is not the Chatter feature for tracking field updates.

D. Publisher Actions are actions users can take from the publisher, not automatic field-change tracking.

===========

The correct answers are A. Unique and D. External ID.

The legacy ID should be marked as an External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce REST API documentation states that records can be inserted or updated using a specified external ID field.

The field should also be marked Unique so that the legacy system ID identifies one Salesforce Account record only. Salesforce documentation explains that an external ID can represent an ID from another external system, and uniqueness helps prevent duplicate matching values.

B is incorrect because encrypted text is not appropriate for a matching/upsert key.

C is incorrect because Required only forces a value; it does not make the field usable for upsert matching or prevent duplicate legacy IDs.

===========

The correct answer is A. A hyperlink to the parent Account of the parent Opportunity.

A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity’s Account.

Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.

B is incorrect because formula field data types do not include Rich Text Area as a formula return type.

C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.

D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

===========

The correct next steps are A. Add the fields to the page layout on the object and C. Create a permission set for access to the object and fields .

This is a two-part access problem in Salesforce: users need both security access and user-interface exposure . Creating a custom object and fields in Schema Builder only creates the metadata. It does not automatically guarantee that end users can see, create, edit, or use those records and fields.

C is required because object permissions define the base-level access users have to records for an object, such as create, read, edit, and delete. Salesforce also uses field permissions / field-level security to control whether users can view or edit individual fields. Permission sets are the correct modern mechanism to grant object and field permissions to selected users without changing their base profile.

A is also required because page layouts control the organization of fields on record detail and edit pages. Even if a user has field-level access, the field must be placed on the relevant page layout for normal record-page visibility and editing in the UI. Salesforce specifically separates field-level security as the access-control layer and page layouts as the UI organization layer.

B is incorrect because “Allow Reports” only makes the object available for report creation; it does not grant users object CRUD access or field-level visibility. D is incorrect because data types are assigned during field creation, not after, and choosing a data type does not grant user access.