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

A record-triggered flow is the preferred declarative automation. Salesforce supports record-triggered automation when records are created, updated, or deleted, and its current Flow architecture includes after-delete processing for actions that must occur because a record was removed. The flow can trigger from Task deletion, use information from the triggering Task to identify the related Case, obtain the Case owner, and execute the email notification action. Assignment rules are designed primarily for assigning records such as Cases or Leads and do not respond to Task deletion. Escalation rules manage Case escalation timing, not deletion events. An Apex trigger could technically implement the requirement, but Platform App Builder principles favor native declarative automation when Flow supports the event and required action.

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

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 answers are C. My Domain must be deployed and D. The component is tagged for record pages instead of home pages.

Salesforce custom Lightning components must be properly configured before they appear in Lightning App Builder. Salesforce Trailhead explains that custom components configured for Lightning App Builder appear in the Lightning Components pane, and the component bundle must be compatible with Lightning App Builder and Lightning pages.

C is correct because Salesforce requires My Domain for adding custom Lightning components in Lightning Experience/App Builder scenarios. Salesforce Help notes that users cannot add a custom Lightning component without enabling and deploying My Domain.

D is correct because Lightning components must be exposed for the correct page type. A component exposed only for record pages will not appear for a Lightning Home page. Salesforce Developer documentation states that lightning__HomePage enables a component to be used on a Home page, while record-page-only configuration is separate.

Why others are incorrect:

A is incorrect because a custom tab is not required to add components to a Lightning Home page.

B is incorrect because “developer permission” is not the normal reason a downloaded component cannot be added to a Lightning Home page.

===========

The requirement specifies detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields support:

Multiple lines of text

Inline images

Hyperlinks

Formatting (bold, italic, lists)

Salesforce documentation confirms that Rich Text Area fields are the standard choice when storing formatted content on a record. (Salesforce Help)

D. Long Text Area supports only plain text, not images or links.

C. URL is for a single web address only.

B. Lightning Web Component is for custom UI elements, not a field type.

===========

The correct answer is D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.

Universal Containers needs to represent separate business entities because separate bills are sent to each customer and each dealer. In Salesforce, business accounts are used to represent companies or organizations, and contacts represent the people who work for those accounts. Salesforce account hierarchies are used to show relationships between related accounts through the Parent Account field.

So the best model is:

Customer = Account

Dealer = Account

Representative at each business = Contact on that Account

Customer/dealer relationship = Account Hierarchy

A is incorrect because Account Teams represent internal Salesforce users working on an account, not external dealer/customer representatives.

B and C are incorrect because they do not correctly represent separate billing entities as separate Accounts.

===========

The correct answers are A. Use a master-detail relationship between the Park and Trail objects and C. Use a roll-up summary field on the Park record to show the total number of trails .

To show the total number of child Trail records on the parent Park record without code, the app builder should use a roll-up summary field . Salesforce documentation states that roll-up summary fields display values on a master record based on related detail records.

That means Park should be the master object and Trail should be the detail object. Then a roll-up summary field on Park can count the related Trail records.

B is incorrect because standard lookup relationships do not support roll-up summary fields.

D is incorrect because a formula field cannot count multiple child records.

===========

The correct answer is A. AppExchange.

For a Salesforce Classic-to-Lightning Experience migration, the app builder should look for prebuilt apps, components, adoption tools, and consultant solutions on AppExchange. Salesforce now refers to this marketplace as AgentExchange in newer Trailhead content, but the exam option “AppExchange” is still the intended answer. Salesforce describes it as the marketplace for Salesforce solutions, including apps, agents, components, and more, and specifically notes that admins can look there instead of building everything from scratch.

Flow Builder is for automation, Lightning Object Creator is for creating objects from spreadsheets, and Import Wizard is for importing data. They are not marketplaces for prebuilt adoption or migration resources.

===========

The correct answer is D. Choose an unmanaged package from AppExchange that closely meets the requirements of the project and allows programmatic development.

The requirement has two key parts: the app builder has very little time, and the solution must be fully customizable. Salesforce documentation describes unmanaged packages as suitable for one-time drops of applications that require customization after installation. That fits this scenario better than building everything from scratch.

C is incorrect because managed packages are better for distributed, upgradeable AppExchange apps, but they can restrict subscriber changes to packaged components. The question specifically says the solution still needs full customization, which points to an unmanaged package.

The correct answers are A and B .

The requirement is to display a visual flag image based on Case Priority. Salesforce’s own sample image formula for Case Priority uses the IMAGE() function with CASE() to display green, yellow, or red flag images.

Both formulas are valid because:

A uses IMAGE() with nested IF() and ISPICKVAL() checks.

B uses IMAGE() with CASE() to return the correct image URL.

C and D are incorrect because they return only the image URL text, not the actual image. The formula must use IMAGE() to display a visual flag.

===========

The correct answer is D. The Owner field on the Master record.

In a master-detail relationship, the detail record does not have independent ownership. Salesforce documentation states that the Owner field on the detail object isn’t available and is automatically set to the owner of the related master record.

Sharing is also controlled by the parent/master record. Salesforce Help explains that when a custom object is on the detail side of a master-detail relationship, its organization-wide default is set to Controlled by Parent.

A and C are incorrect because the detail record does not maintain independent ownership in a master-detail relationship. B is incorrect because ownership is not determined by a default owner setting on the parent object; it comes from the actual Owner field on the master record.

===========