Salesforce Platform-App-Builder Online Access

The correct answer is B. Custom action.

The user wants to edit a record’s Status and enter a custom Due Date quickly from the record feed in the Salesforce mobile app. A custom action, specifically an object-specific quick action, can expose selected fields for fast updates on mobile. Salesforce documentation states that object-specific actions let users quickly create or update records in the context of a specific record, and the Salesforce mobile action bar displays actions in mobile places such as feeds and record pages.

Custom button and URL formula field are not the best mobile feed-editing tools. Custom quick access link is not the correct Salesforce feature for this requirement.

===========

The correct answer is C. Create a Partial Copy Sandbox and use a sandbox template.

A Partial Copy Sandbox includes metadata plus selected production data and supports the use of a sandbox template to control which objects and data are copied. This allows the app builder to exclude confidential custom objects. It also meets the weekly refresh requirement because Salesforce allows Partial Copy sandboxes to be refreshed every 5 days.

B. Full Copy Sandbox can use a sandbox template, but it does not meet the weekly refresh requirement.

A and D are incorrect because Developer and Developer Pro sandboxes are not the correct choice when the sandbox must include selected production data records through a sandbox template.

===========

This question is testing the classic Salesforce Process Builder automation best practice , not a generic Flow-only rule. Salesforce’s official process design guidance states that an org should have only one record-change process per object . The reason is simple: every time a record is created or updated, Salesforce evaluates the record-change processes for that object. If an object has multiple record-change processes, the automation becomes harder to predict, harder to troubleshoot, and more likely to hit governor limits. Salesforce specifically explains that consolidating automation into one record-change process gives admins a single view of all criteria and actions for that object, reduces duplicated automation overhead, and allows the app builder to control the order of criteria evaluation.

A is not the best exam answer here. In modern Flow architecture, “one Flow per object” is often discussed as a design pattern, but it is not the exact best-practice wording being tested by this Platform App Builder-style question. Salesforce Flow design is more nuanced today because record-triggered flows can vary by trigger timing and event. B is wrong because validation rules should be separated by validation requirement, not forced into one rule per object. C is wrong because invocable processes are reusable modular processes, not the main record-change automation container.

The correct answer is C. Enhanced List.

Salesforce documentation states that the Enhanced List related list type shows up to 10 fields and allows users to resize columns, sort columns, perform mass actions, and wrap text. This exactly matches the requirement: users need to see ten fields and need the ability to sort and wrap text on related lists.

D. Basic List is incorrect because the Basic List type shows fewer fields and does not provide the enhanced related-list behavior required here. A. List View and B. List Class are not the correct Related List Lightning component type for this requirement.

===========