Salesforce Platform-App-Builder Online Access

The correct answer is A. The requirement is to combine four custom text fields into one formula field and display the result on two lines.

The formula works as follows:

Street__c displays the street on the first line.

BR() inserts a line break. Salesforce documents the BR formula function as inserting a line break in a text string.

City__c & " , " & Planet__c & " " & Galaxy__c displays the remaining location information on the second line. The & operator connects two or more strings in Salesforce formulas.

Why others are incorrect:

Options using field names without __c are not correct for custom fields. Options using __r are relationship references, not direct custom field references. Options without BR() do not satisfy the two-line requirement.

===========

The correct answers are B. AppExchange and D. Lightning Components.

Salesforce Trailhead states that custom Lightning components can be created with Lightning Web Components or Aura, and existing Lightning components can also be installed from the AppExchange. Custom components configured for Lightning App Builder appear in the Lightning Components pane and can be added to Lightning pages.

Why others are incorrect:

A. Import Wizard is a data import tool, not a source of UI components.

C. Apex Code provides server-side logic, but Apex itself is not a Lightning page component resource.

===========

The correct answer is C. Add the standard Chatter feed component.

To add Chatter feed functionality to a custom object Lightning record page, the app builder should use the standard Chatter component in Lightning App Builder. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed combination on a record page.

A is incorrect because no custom Chatter feed component is required. B is incorrect because related lists do not add the Chatter feed. D is incorrect because the standard Chatter component is already available; an AppExchange component is unnecessary.

===========

Flow Trigger Explorer is specifically designed to manage the execution sequence of record-triggered flows for the same object and trigger category. Salesforce documents that changing a flow ' s order in Flow Trigger Explorer changes its Trigger Order value, and that this value determines the sequence in which applicable flows execute. Therefore, the discount calculation flow should receive the earlier/lower trigger order and the notification flow the later order. This preserves separate flows while guaranteeing deterministic sequencing. An asynchronous path does not provide the same explicit ordering contract. A zero-minute scheduled path unnecessarily changes transaction timing. Combining both flows violates the stated ownership requirement and is not necessary because Salesforce provides native trigger-order controls. The correct Platform App Builder solution is therefore Flow Trigger Explorer.

================