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

Feed Tracking is the correct feature because Salesforce can automatically generate feed updates when a tracked field changes on a record. Salesforce Help explains that feed tracking detects changes to tracked record fields and posts updates to the feed. It can also be configured for custom objects.

For this scenario, the app builder would track the travel request approval/status field. When the request becomes Approved, Salesforce posts that tracked change automatically on the record feed.

Why others are incorrect:

Auto-response rule sends automatic email responses, mainly for Lead/Case scenarios.

Approval process manages record approval routing, but the feature that creates automatic feed posts for field changes is Feed Tracking.

Feed quick action is manual, not automatic.

===========

The correct answers are A. Tabs and B. Related record.

Tabs help create a more condensed Lightning record page by grouping information into separate tabbed sections instead of showing everything in one long page. Salesforce Lightning App Builder allows app builders to add, remove, reorder, and customize components on Lightning record pages.

Related Record is required because service agents want to modify the associated Contact and Account directly from the Case Lightning record page. Salesforce Help states that the Related Record component uses quick action metadata and requires an associated quick action to update records.

Why others are incorrect:

Path is used to guide users through stages or status values, not to edit related Account or Contact records.

Rich Text displays formatted guidance or static text; it does not provide editable related-record functionality.

The correct answer is C. Salesforce Schema Builder can create fields, including relationship fields, formula fields, and normal fields, and it also helps visualize existing object relationships. However, a field created in Schema Builder is not automatically added to the object’s page layout. Salesforce documentation states that after using Schema Builder, the field must be added through the Page Layout Editor.

Why others are incorrect:

A is incorrect because Schema Builder can create formula fields.

B is incorrect because Schema Builder can create relationship fields.

D is incorrect because Schema Builder is specifically used to view and understand object relationships.

===========

The correct answer is C. A delegated approver is the recommended Salesforce feature when the assigned approver is unavailable, such as during vacation. Salesforce documentation confirms that users can identify a delegate in approval settings, and delegated approvers can approve or reject approval requests.

This ensures the closed-won Opportunity can still be reviewed before the leaderboard is updated, even though the owner’s manager is away.

Why others are incorrect:

A is not the best recommended setup because relying on an assistant to reassign requests is manual and reactive.

B is incorrect because forwarding approval requests is not the standard solution for planned approver absence.

D is incorrect because assignment rules do not assign delegated approvers for approval processes.

===========

The correct answer is C. Internal profiles.

When an app builder creates a custom field using Schema Builder, Salesforce sets field-level security for custom fields to visible and editable for internal profiles by default.

That is why B. All profiles is not the best answer. Salesforce’s documented default is specifically internal profiles, not every possible profile type.

===========

The correct answer is D.

Salesforce allows converting a master-detail relationship to a lookup relationship only when there are no roll-up summary fields on the master object that summarize the detail records. Salesforce documentation states that after a roll-up summary field exists on an object, the object’s master-detail relationship can’t be converted into a lookup relationship.

In this case, if Account has roll-up summary fields based on related Park records, Salesforce blocks the conversion.

A is incorrect because a flow using Account does not normally prevent converting the relationship. B is incorrect because formulas on Park referencing Account are not the primary restriction. C is incorrect because custom objects do not need at least one master-detail relationship for reporting.

===========

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

The legacy ID should be stored in a custom field marked as an External ID because Salesforce uses External ID fields to identify records from an outside system and to support update/upsert operations during future data loads. The field should also be marked Unique so each legacy system ID maps to only one Salesforce Account record and avoids duplicate-match problems during upsert. Salesforce documentation defines External ID fields as fields that contain record identifiers from outside Salesforce and can be used to update or upsert records.

A. Required is not necessary for the upsert-matching requirement.

B. Encrypted/Text encrypted is not appropriate because encrypted fields are not used for this legacy-ID matching purpose.

===========

The correct answer is C. Record-triggered flow.

To track the number of times a Case is reopened, the app builder can create a record-triggered flow on the Case object that runs when the Case is updated. The flow can check when the Status changes from Closed to an open/reopened status and increment a custom number field such as Number_of_Reopens__c . Salesforce Trailhead explains that record-triggered flows run when records are created, updated, created or updated, or deleted.

Why not Apex Trigger? Apex could work, but the Platform App Builder best answer is the declarative option: Flow before code.

To embed a chart on the Account detail page showing related Opportunities by Stage, the report must summarize Opportunities, not just list them. Salesforce documentation specifies that summary reports allow grouping by fields (e.g., Stage) and can be used in Report Chart components. (Salesforce Help)

Tabular reports cannot be grouped and therefore cannot provide the aggregated chart needed.

The report must be built on the Opportunity object because the records being summarized are Opportunities, not Accounts.

===========

The correct answer is B. Lookup.

This is a one-to-many mentorship relationship: one experienced Realtor can mentor many new Realtors, but each new Realtor works with only one experienced Realtor. A lookup relationship is appropriate for connecting one record to another in this type of flexible parent-child model. Salesforce relationship documentation confirms that lookup relationships are used to relate objects without the strict ownership, sharing, and deletion behavior of master-detail relationships.

Master-detail is too restrictive because the new Realtor record should not necessarily inherit ownership and deletion behavior from the mentor. Many-to-many is incorrect because each new Realtor has only one mentor. Indirect lookup is used for external objects, not this internal Salesforce relationship.

===========